Part Number:TMS320C6748
We are operating a C674x DSP on a number of different custom cards with our only non-volatile memory being a large SPI flash. At address 0 of this SPI flash we have our own custom boot loader which among other things provides a means of transferring AIS files (code and data) via different communications links, programming the AIS to the SPI flash at a specific location, and then loading that code and data to the DSP RAM and transferring control.
This all works very nicely. We build our images (both boot loader and main code) using your AIS generation tool. We program the custom boot loader (with UART boot mode) using your UartHost.exe program. It is really a very nice set of tools, thank you, but there is one fly in the ointment which perhaps can be fixed/improved.
At the moment, the custom boot loader must contain code that reads AIS from the SPI flash, parses the AIS, and then executes the various AIS functions (primarily loading code to RAM of course, but also some of the other AIS functions). However, it seems a shame to do it this way, since the ROM loader already has all the code for this purpose, fully debugged, performing all AIS functions,
My question: Is there a way that after my custom boot loader has done what it needs to do, it can pass an SPI flash address to the ROM loader and transfer control to the ROM loader, and it would do all the parsing of the AIS and all the AIS functions? I would think that this would be helpful for a lot of users, and perhaps it is available, but I have read through an awful lot of reference material and cannot find a documented way to do this.
Even if this is not a planned-for and documented mode of operation, perhaps someone with access to the source code of the ROM loader could tell us a register to place the SPI address and a location to jump to that could provide this functionality.
Thanks.