OMAPBootrom¶
Generic documentation¶
TODO: Read the various TRM and push the info to wikidata:
- check the various SOCs the sram size limit in the TRM.
- check the load address / memory mapping of MLO in case of USB boot or boot from eMMC in the TRM.
- Check mmc1 booting constraint (card size, look if < 4GiB works) in the TRM
Also:
- Read the TRM sections about SYS_BOOT and booting and document that, ideally write a tool for it, or upstream the code in some other tool.
Documentation¶
The droiddevelopers website has some information on trying to use bugs run free software on several Motorola devices.
That website has many information:
- It has documentation on the structure of signed MLOs
TODO:
- Read droiddevelopers more to understand restricted boot better.
- Also the OMAP wiki might have some information on OMAP restricted boot.
- Also look if there is substancial information in the Technical Reference Manual (TRM) about fuses but that's unlikely.
Code¶
- As march 2020, there are no fuses driver or code for any OMAP in either u-boot, Barebox, Linux, or crucible.
- U-boot documentation mention TI tools that have to be obtained after signing an NDA
- TODO: check if chipsec has infos on OMAP fuses
Possible attacks¶
- Even if it's unlikely, once we understand the OMAP restricted boot better, we could check if some devices are signed but not in enforcing mode.
Other ideas¶
- On IRC there was some interest in replacing the SOC by simply unsoldering it and resoldering a GP OMAP.
- TODO: check if the stock bootloader still work with that or how to make sure that the device is working after the SOC has been replaced for the first time ever. Example: run the stock bootloader on a single board computer with UART.
- TODO: Write code that init the display
- Find how to handle the amount of work combined with the insecurity of the supply chain for the OMAPs
Links¶