We are presently upgrading our application from SYS/BIOS IND SDK 1.1.0.6 to 2.1.1.2. The application itself has been ported fine, but now we are running into issues with the bootloader(s).
When we were using the 1.x series of the SDK, we noticed that the SPI flash bootloader would also boot an 'app' file on the SD card if it was present, then would fall back to the SPI flash if the file was removed. Is this no longer a supported feature? Would we need to edit the bootloader source code to 'get it back'?
A second problem is we are unable to get our board to boot from an SD Card bootloader at all; the above 'feature' was the only way we were able to boot from SD card previously. I followed the below process:
- Copied C:\ti\sysbios_ind_sdk_2.1.1.2\sdk\starterware\binary\bootloader\bin\am335x-evm\gcc\bootloader_boot_mmcsd_a8host_debug_ti.bin to SD card and renamed to MLO
- Copied application binary (_ti.bin) to SD card and renamed to APP
- Erased the SPI flash bootloader by running C:\ti\sysbios_ind_sdk_2.1.1.2\sdk\tools\flasher\spi_flasher\isdk_spi_flasher.out, selecting erase, and erasing 0x0 with size 64 kbytes.
When starting up the board in this configuration, no text is observed for the bootloader on the USB serial connection, and the application software does not start.
We tried placing the SYSBOOT jumper in both positions (pins 1-2 OR pins 2-3) with no success. Note that we have previously erased the NOR bootloader to prevent interference.
We also noticed that we could still use the SDK 1.x bootloader to launch SDK 2.x application from the SD card if using the .bin file without the TI prefix, which is a temporary solution to allow SD booting. However, the old bootloader will not run SDK 2.x application from SPI flash at all.
Any suggestions for
- Having a dual-mode bootloader (preferred), or
- Fixing the SD card boot
Would be appreciated.