Part Number: TMS320F28388D
Hello everyone,
in our current project we want to chain multiple TMS320F28388D Devices via the SPI-Bus.
One controller from another vendor will serve as master and all TMS320F28388D are setup as slaves.
After selling the finished device, the customers only have access to an interface of the master-controller (other vendor).
We still want to make infield softwareupdates of the TMS320F28388D possible.
Since all TMS320 are chained on one SPI we can't use the SPI-Bootloader, becuase we can't simulate an EEPROM.
We then thought, to integrate a seperate standalone firmware-update-application on every TMS320 when shipping.
The idea is to let the master-controller control a boot-pin of all TMS320 and then issue a software reset on all of them.
All TMS320 will then boot from a different FLASH-Bank and load the firmware-update-application.
I understand how to change the bootmode to change the boot-flash-bank of CPU1 and CPU2.
What I don't know, is how the main-application can start from one main-function, while the firmware-update-application starts from a different main-function.
Furthermore I would like to know if it's better to implement both firmwares in one CCS-Projekt (1 for each CPU) or to setup two different projects for each firmware (2 for each CPU) and then combine the generated hex files later?
Thanks and Regards,
Marcel Kummer.
