Part Number:PROCESSOR-SDK-OMAPL138
I have been trying to load the various boot components into NAND from a u-boot terminal to allow booting from NAND. At the moment I'm manually punching in commands to the u-boot terminal, but my expectation is that I will be able to prepare a minicom script (much like what is done at setup stage) that will allow this to be carried out as a semi-automated step.
If possible, I would not like to rely on the windows tool provided as I don't have access to a windows development PC.
I have a bootable SD card, which I have added the following to its boot partition:
- u-boot.ais (output of make u-boot)
- u-boot.bin (output of make u-boot)
- zImage (output of make linux)
To keep things simple, Im not looking at TFTP for now...
These are the steps Im carrying out so far:
- boot the board using the SD card, and bring up u-boot terminal (using U-Boot 2017.01-g9fd60700db)
- Copy the AIS bootloader from the SD to the start of NAND
nand device 0 nand erase.spread 0 0x20000 fatload mmc 0 0x81600000 u-boot.ais nand write 0x81600000 0 0x20000
- Copy the u-boot binary from the SD card to NAND
nand erase.spread 0x80000 0x40000 fatload mmc 0 0x81600000 u-boot.bin nand write 0x81600000 0x80000 0x40000
- Copy the kernel image from SD card to NAND
nand erase.spread 0x280000 0x300000 fatload mmc 0 0x81600000 zImage nand write 0x81600000 0x280000 0x300000
At this stage I would have thought that the required components have been copied to NAND, meaning the board will load u-boot successfully. I could then go off an configure the way u-boot loads the kernel... but I'm not seeing this at all. I'm not seeing any activity at all. Besides the Ethernet lights slowly blinking at me - 1Hz or slower)
This is making me think I'm writing incorrect files... However, I see the same result when trying to write the pre-built images... Where am I going wrong? Invalid addresses perhaps?