Part Number: TMS320C5515
Tool/software:
Hi,
On the TMS320C5515 there is a ROM boot-loader. As I understand that boot-loader - based on Using the TMS320C5515-14-05-04 Bootloader (sprabd7d) document - the boot-loader searches for and then transfers an application boot image to RAM and then initiates execution. The boot image may found on a number of storage options. The storage options are searched in a specific order. For example, an image on SPI EEPROM would be used in preference to the same image stored on a connected SD card, since the EEPROM has precedence in the boot-loader search.
At application run-time, I would like to report the storage location that was selected by the boot-loader. For example, I don't mind the image being loaded from an SD card as a backstop where the SPI EEPROM image is unavailable or corrupt but I'd like to inform the user that the code isn't running from our choice of preferred location. Is there an application run-time method to query the boot-loader to determine the storage location from which the code was copied?
I've also consulted the device datasheet (SPRUFX5E) and CPU reference (SWPU073E) but found nothing relevant.
I'm not hopeful that such a mechanism exists, but it seemed prudent to get a definitive confirmation. I further appreciate that another option is to generate different code images for the different storage locations, and I might adopt that method if the boot-loader information is not available at application run-time.
Regards,
BJC
