TS201-JTAG. Multiprocessor configuration. Processor not going in emulator session
Thread Summary
The user encountered JTAG connection issues with a custom board using 3 TS201s in a JTAG chain after loading a file into EPROM. The solution was to change the boot mode by setting the /BMS pin high during reset, allowing the processor to wait for an external boot. This workaround resolved the JTAG connection and debug session issues.AI Generated Content
Hello,
I have been using a custom board where 3 TS201s are connected in a JTAG chain. I am using ADZS-USB-ICE emulator.
Initially, when there was nothing in EPROM of the processor, JTAG was successfully going in the emulator session. After I dumped a loader file in it, I have been getting the error with error code 0x80004005 and JTAG is not going in emulator session.
I have tried using all the three different initial connections - Halt then reset, Halt and Do not Disturb. Former two are giving the error code. In Do not Disturb mode, it is going in emulator session but when I try to load driver for erasing flash, VisualDSP++ hangs by giving error "JTAG scan failed..." and "Emulator HW couldnt scan EMUCTL or EMUPC register". There is no issue with driver file as it was working fine initially.
Can anyone please suggest me the way in which I can enter the Debug session in any way?
I am using VisualDSP++ 5.1.
Hello.. Can someone please help me out with this. Thanks in advance.
Hi Nirav,
Can you try changing the boot mode and see if that helps ? /BMS pin is a strap pin and its value during reset decides the boot mode. Making the /BMS pin high during reset will make the processor wait for an external device to boot DSP through the external port or a link port.
Regards,
Mahesh
Thank you for your reply Sir. Changing the BMS pin worked. .. But I did not understand why the former case didn't work. If I have anything in EPROM and I want to go in debug session, I cannot go, without changing the BMS pin. Can you please give your comments on that.
Thanks and regards,
Nirav
Hi Nirav,
The problem may be with the loader file or the programming of EPROM. But if there is a proper code sitting in EPROM, them should not be any issues in connecting to the debug session.
Regards,
Mahesh
Please log in to reply.