I have build a secondary bootloader that a host loads via the HPI. This secodary bootloader executes (via the jump address and 0x60/60 address ) and this loads my application in internal and external memory via the HPI and a shared internal memory region. If I load the bootloader using the jtag initially, I can then download the application and all is good. After that, I can reset the DSP, and then download the secondary bootloader, then the application as many times as I want. All works good.
The problem is the very first time after I power up the hardware and do not use the JTAG. If I download the secondary bootloader and hit the 5502 entry address, the bootload starts up fine. It configures the external SDRAM, performs a mem test on the SDRAM, configs the HPI, then sets the HINT indicating ready for download. The host then copies the entire DSP application, in blocks, to the local memory share, and the bootloader copies this to internal and external memory. on completion, the entry address is given to the secondary bootloader, and this initiates the DSP app. The app starts to run but gets stuck when trying to access external serial ports, like the spi, or UART. If I connect with the jtag and hault, then run, all the sudden everything is happening. The app is already executing in external memory and going along fine untill it hits a read from the SPI or a CSL write to the uart.
I believe that there is some configuration I am missing that the debugger is supplying. The only thing I find in the sd5502emu.gel is the config of SDRAM, which I have already verified is working.
Any Ideas?
Robert
