Problem with sd560v2u on Concerto

More information:

I ran the Reset, PathLength, and Integrity tests with the following results:

@BEGIN-1

CMD:dbgjtag.exe -d sd560v2u -p 0 -r

CMD:dbgjtag.exe -d sd560v2u -p 0 -S pathlength

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-233' (0xffffff17).

The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:

The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.

An attempt to scan the JTAG scan-path has failed.

The target's JTAG scan-path appears to be broken

with a stuck-at-ones or stuck-at-zero fault.

CMD:dbgjtag.exe -d sd560v2u -p 0 -S integrity

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-233' (0xffffff17).

The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:

The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.

An attempt to scan the JTAG scan-path has failed.

The target's JTAG scan-path appears to be broken

with a stuck-at-ones or stuck-at-zero fault.

@END-1

Here is my pinout:

I transferred the circuitry direct from the Concerto eval board and made these connections . .

Hi Pat,

I'm a little fuzzy on some details so please confirm if I have this straight:

1) You are using CCSv4.2 (which 4.2 version are you using?)

2) You have a custom F28M35H52C1 board with a 10-pin JTAG header

3) You can connect to it using an XDS100v2 emulator

4) You cannot connect to it using an SD XDS560v2 USB based emulator

Is the above correct?

Thanks

ki

Thanks Ki for the response.

I am using CCSv4.2.5.00005. Yes to all questions. I can connect and debug using XDS100v2 fine. I just started using the XDS560v2 STM for CCS v4.x, but cannot get it to connect to the target. I connected the JTAG connector functions to the same points as the USB was previously connected. The schematic is the same as for the Concerto eval board, the F28M35xx ISO Control Card. I connected the JTAG connector pins to the DEBUG3V3 side of the isolators, same as the USB FT2232 while disconnecting the connections to the USB.

Pat

Was the XDS100v2 that was working also using the same JTAG header as the XDS560v2?

Ki,

I am using the same board circuitry as the eval board. On that board, the USB FT2232 device connects to the jtag interface pins 83-89 on the F28M35H52C1 MCU, thru the isolation buffers. With the 14-pin JTAG connector, I connect the same - to the MCU via the isolators. Is there some additional setup that I need to do? I followed the directions provided with the SD module. Obviously, I'm missing something here.

Thanks,

Pat

Ki,

I have reviewed the setup reguirements and verified the wiring again, to be sure. I also moved the emulator from my Win7 machine to my more reliable XP maqchine with the same result. I cannot even launch the debugger without getting the error "Error initializing emulator". I only get the top line in the debug window that says "Spectrum Digital SXD560V2 STM Emulator_0 [Non-Project Debug Session].

There is a major disconnect here in the setup OR I may have a bad emulator, even tho it is brand new and the first time used. I didn't see any switches on the module. I have a red State-3 and a yellow State-2 light on constantly, State-1 is always off, indicating that the emulator is not connected??? All the connections are tight and I have seperate power to the module. The USB connection is also powered seperately from the computer.

I would appreciate any and all help here.

Thanks,

Pat

.

When I switch to the CM3 side and try to run the emulator, I get this error:

Error connecting to the target: (Error -233 @ 0x0) The JTAG IR and DR scan-paths cannot circulate bits, they may be broken. An attempt to scan the JTAG scan-path has failed. The target's JTAG scan-path appears to be broken with a stuck-at-ones or stuck-at-zero fault. (Release 5.0.429.0)

Any idea why I would get this message?

Thanks,

Pat

Pat,

This is a bit out of my expertise. Hence I've forwarded this thread to the emulation experts so they can reply.

Thanks

ki

Okay, Thanks Ki.

Here's some more data:
When I try to connect (and get the error message), the signals on the JTAG pins are:
TCK = 500 kHz squarewave, TMS = low, TDI = high, TRSTn = high (tried a 2.2k ohm pull down - no effect), TDO = low, EMU0 = high, EMU1 = high (NOTE: EMU0 and EMU 1 appear to be inverted from the Concerto output - this was done on the eval board - is this correct for the 560v2 as well?

THanks,

Pat

Pat,

I noticed in the JTAG pinout you have “RTCK – Test Clock?”. For this device TCK should be looped back to RTCK on your board. If not, when you setup the  XDS560v2 in CCS there is a “JTAG Clock Selection” parameter that has a loopback option. You can give that a try.

Regards,

Doug

Doug,

Thanks for your reply. I do have TCK and RTCK tied together on my board at the JTAG connector, if that is what you mean.

Pat

1) Is this a Blackhawk or a Spectrum Digital 560v2?  In the first post, it was described as a Blackhawk, but the configuration and tools indicate it's being configured as a Spectrum Digital.  These aren't 100% compatible.  If it is a Blackhawk, then make sure you're only using Blackhawk's tools and configuration.

2) The error message "Error initializing emulator" means that the emulation software in CCS cannot communicate with and download code into the emulator.  It has nothing to do with the connection of the JTAG pins. It could be that the configuration is incorrect, the emulator is hung, the Windows driver hasn't enumerated the emulator, corrupted install of the emupack, the emulator is broken, etc.  

3) The error message in dbgjtag "SC_ERR_PATH_BROKEN" means that there's no data coming out of the target device on the TDO pin.  The target is either not getting into the proper scan state, or the TDO pin is not connected or possibly held high/low.  This is not the same as a missing RTCK connection, it would be a different error message.  So RTCK isn't the issue here.

If possible, try the emulator with another board known to be working.  And/or try using another emulator with this particular installation.  See if you can pin down what combination works or doesn't work to isolate where the problem is.