Hi,
I have a custom board with two 5509A processors on a single jtag chain. This board has been used for some time and was originally developed using CCSv2 with the XDS510PP emulator which had no problems with the two processors on the JTAG chain.
Ive been porting this to CCSv5 using a blackhawk XDS560v2 emulator. I had to do some work to make sure all the CSL configuration that used to be done in the CCSv2 configuration was transferred to the initial code in my main function and I think I have done that correctly. The first dsp in the chain is configured with EMIF and the second is with HPI. I load the code on each processor and step through the beginning of main on each until the CSL initialization is done. Then, I try checking the memory of the second processor from the first by looking at memory location 0x2002c0 since the second processor is connected to CE1. Unfortunately, I get the following error:
dsp0: Trouble Reading Memory Block at 0x2002c0 on Page 1 of Length 0x5a: (Error -1144 @ 0x2002C0) Device core is hung. The debugger attempted to recover debug control, but was unsuccessful. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.791.0)
After this, I lose control of the processor and have to exit debug and reboot the board.
Interestingly, when I look at the EBSR memory location, I get an error there as well:
dsp0: Trouble Reading Memory Block at 0x6c00 on Page 2 of Length 0x5a: (Error -1069 @ 0xD878) Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.791.0)
However, it doesn't hang the processor and I can still step through the code. Also, the EBSR value seems to be displayed correctly although all the data after looks bad.
Any ideas what is wrong here? Getting quite frustrated.
I tried slowing down the emulator to 2MHz and it didn't change anything. I also did a test of the target configuration and everything was fine up to the highest frequency.