Tool/software: Linux
Hello,
I m unable to boot RT-Linux by using the Windows & Linux procedure. I follow this step:
1) Erase bootloader stored in the flash by using "isdk_spi_flasher.out" from code composer: Erase, offset 0x0, size 64
-> Result: The origin starterware app doesn't run anymore on the serial console, + the LCD message in the display disappear
2A) I create SD card by using this
-> Result: I have the MLO +U-boot.img in the boot part, and the rootfs in the other.
2B) I use the create-sd.sh in the Linux SDK and i reach exactly a the same point.
3) I turn-on the board with the sysboot jumper in the good position (2&3) and nothing happen in the serial console.
So at the beginning i have the follow booting sequence:
ROM Booltoader --> Starterware bootloader at 0x00000000 in the flash -> Starterware app in the flash at 0x20000000
After the procedure i get:
ROM Bootloader-> MLO for U-BOOT-> Nothing. I m sure the MLO is executing from the SD card because after sereral try i replace the MLO that have to boot U-boot by the MLO that boot a starterware app found here:
Note for the moment i just put the MLO (StarterWareBootloader) without the app (StarterWareApp) and i get this:
That prove the boot sequence pass really by the SD-CARD when i put the example-utils app find here:
the MLO seems to copy the starterware in the I-RAM but it don't execute it
My conclusion, based in the code below, is that the code seems to be copied but never executed from the for in SD card booting context , and that for the Starware app booting and the Linux booting. Did you yet had the same issues? What a your recommandations to debug this?
Thanks you.