| Alessandro Rubini | d5254f1 | 2009-01-24 18:10:37 +0100 | [diff] [blame] | 1 | |
| 2 | The Nomadik 8815 CPU has a "secure" boot mode where no external access |
| 3 | (not even JTAG) is allowed. The "remap" bits in the evaluation board |
| 4 | are configured in order to boot from the internal ROM memory (in |
| 5 | secure mode). |
| 6 | |
| 7 | The boot process as defined by the manufacturer executes external code |
| 8 | (loaded from NAND or OneNAND) that that disables such "security" in |
| 9 | order to run u-boot and later the kernel without constraints. Such |
| 10 | code is a proprietary initial boot loader, called "X-Loader" (in case |
| 11 | anyone wonders, it has no relations with other loaders with the same |
| 12 | name and there is no GPL code inside the ST X-Loader). |
| 13 | |
| 14 | SDRAM configuration, PLL setup and initial loading from NAND is |
| 15 | implemented in the X-Loader, so U-Boot is already running in SDRAM |
| 16 | when control is handed over to it. |
| 17 | |
| 18 | |
| 19 | On www.st.com/nomadik and on www.stnwireless.com there are documents, |
| 20 | summary data and white papers on Nomadik. The full datasheet for |
| 21 | STn8815 is not currently available on line but under specific request |
| 22 | to the local ST sales offices. |