This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Boot Loader Question

Hi, I've got some code running on a Logic PD board that uses the ARM and DSP in the L138.  I'm trying to move to my target custom board, but am having some strange issues.  Primarily, it appears that some of the peripheral devices, like the UPP port, don't work.

Going back and forth between my custom board and the Logic PD board I see that the boot loader seems to make the difference.  The 1.65 bootloader on the Logic PD board, allows the UPP port and possibly other peripherals to work with my code. Newer boot loaders cause the issue with the UPP port not working on the Logic PD board too.

Unfortunately, this doesn't help me with my custom board.  I've had no luck using Code Composer Studio and an XDS 510 pod to burn the 1.65 boot loader into serial FLASH on either my custom board or the logic PD board.  I get the same errors:

"No magic number

SPI Memory Boot Failed

Aborting ..."

I can use the serial flash utility with the Logic PD board, and 1.65 works if I do that.  But, using JTAG and Code composer makes even the Logic PD board fail to boot.

I can't use the serial boot utilty with my custom board because the boot pins are set up to boot from the SPI memory only.  I could do some surgery on my custom board and make it boot from the UART.

What's wrong with the newer boot loaders that I can actually burn with Code Composer?

Thanks,

John