• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 1657 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Error connecting to TMS570 HDK using BH560v2

bert lenaerts
Prodigy 60 points
Other Parts Discussed in Thread: TMS320F28335

I try to connect our new blackhawk xds560v2 STM emulator to TI's TMS570 development board. I connected to this board before using the on-board xds100 emulator. With the new configuration however, I get the following error message:

Error connecting to the target: (Error -234 @ 0x0) The instruction scan-path cannot circulate bits, it may be broken. An attempt to scan the JTAG instruction registers has failed. The target's JTAG instruction path appears to be broken with a stuck-at-ones or stuck-at-zero fault. (Emulation package 5.0.791.0)

With the emulator, some config and diagnostic tools are supplied. If I try a JTAG path scan with the "BH560v2 config utility", it always works the first time after powercycling the development board. All the times after that, the same test will fail. I browsed through several threads here on the forum, and I already tried following suggestions:

- update the emulator firmware

- update the emulator drivers (through code composer)

- reduce the JTAG clock (down to 0.5 MHz)

- set the acces port designator to 0x02000100

None of this seems to work. I am a bit out of ideas now, and I would like to ask if any of you would have some further suggestions?

thanks already,

Bert

  • 0
    Prodigy 60 points

    In the meanwhile I performed some more tests, as suggested by the support desk of blackhawk, with following results:

    - In CCS, setting the option "TCLK looped-back with user specified limit" has a positive effect, but still produces following error message:  

    Error connecting to the target:
    (Error -2062 @ 0x0)
    Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 5.0.791.0)

    - Our newly developed board, also containing a TM570LS3137, behaves exactly the same under these tests. Actually, it is for testing this board that we bought the emulator for.

    - I tried the same setup (PC, emulator, software) on another target, a TMS320F28335 from the C2000 series, and this works well. The tests in Blackhawk's config utility succeed time after time.

    I am getting the impression here that the new TMS570 series are not yet fully supported by either driver software or programmer firmware. Does anybody else had a similar issue? Or is there somebody who successfully connected an external emulator to the TMS570 HDK, and if so, which programmer was it?


  • 0 in reply to bert lenaerts
    TI__Expert 6985 points

    Bert,

    I connected several external emulators to the HDK and they all worked: SD XDS510, SD XDS560v2 STM, BH XDS560M

    Unfortunately I don't have a BH XDS560v2. I guess you found and followed this post: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/161988/597503.aspx#597503

    The only issue I know so far is that 12MHz TCLK is not working, TCLK has to be limited to 6MHz.

    Best Regards,

    Christian

  • 0 in reply to Christian Herget
    Prodigy 60 points

    Hi Christian,

    thanks for your reply. I indeed found and followed former post.

    There is one important detail that I did not mention in my previous posts: the "test connection" in CCS has always been successful (within certain TCLK limits), as opposed to what one might expect from similar tests in the blackhawk config utility. 

    When you say that SD XDS510, SD XDS560v2 STM and BH XDS560M all worked, do you mean then that you actually tried to start a debug session, or did you only push the "test connection" button?

    Which version of CCS are you using? I run CCS5.2.0, with updated Blackhawk drivers.

    Unfortunately, I do not have any other emulator to try with, but according to Blackhawk, and also to the integrity tests in CCS, this one should be working fine.

    regards,

    Bert

     

     

  • 0 in reply to bert lenaerts
    TI__Expert 6985 points

    I currently using SD XDS510 USB Plus and SD XDS560v2 STM with CCS 5.2.1 and currently I don't have any Blackhawk drivers installed.

    For my tests with the BH XDS560M I used CCS 5.1.

    Can you please try to connect to the IcePick and DAP:

    • View the Target Configurations files in CCS: View --> Target Configurations
    • Than navigate to your current Target Configuration right-click it and choose: "Launch Selected Configuration"
    • The CCS Debug view should appear.
    • Perform a right-click in the upper left Debug window and choose: "View all cores"
    • Now you should see IcePick, DAP and Cortex-R4F
    • By right-clicking the IcePick you can choose "Connect Target" for just this debug module.
    • If this worked you can perform the same for the DAP and your JTAG connection should be fine.

    There is also this demo video how to use the IcePick, but this is for CCS 4.x and the handling is a little bit different.

    Best Regards,

    Christian

  • 0 in reply to Christian Herget
    Prodigy 60 points

    We have a breakthrough: the programmer + target are working correctly on my collegue's computer. Since he runs the latest CCS5.2.1, I updated my version as well. Unfortunately, this doesn't seem to do the trick for me. The problem persists.

    Christian, when repeating the procedure you explain above, I end up with the familiar error (scan path cannot circulate bits) when trying to connect with IcePick.

    Bert

  • 0 in reply to bert lenaerts
    Prodigy 60 points

    Ok, one final update: starting a new project in my newly installed CCS and then trying to debug, fails the first time, but works after a retry. A slower TCK doesn't seem to remedy the occasional failures, but still I'm happy that at least I can start working on our new board now.

    Setting the core's "acces port designator" to 0x02000100 remains a necessary measure by the way. 

  • 0 in reply to bert lenaerts
    TI__Expert 6985 points

    Good to hear, that this now works for you.

    Best Regards,
    Christian