• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 415 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.

Questions about using a Blackhawk XDS560v2

Don Carlson2
Intellectual 410 points

We are using a BH XDS560V2 with the ARM-20-pin JTAG connector with a RM46. In order for it to work, I had to setup the "Access Port Designator" to 0x02000100. I was only able to figure this out by searching on the TI forum. I am curious, what exactly does this address represent, and is it documented in the BH or TI manuals anywhere? I would like to add a reference for our documentation.

Also, when terminating a debug session, unlike the XDS220 that would release the JTAG and allow the CPU to run, when I terminate a debug session with the BH XDS560V2, the CPU does not appear to start running... it hangs and I must cycle power or reset to get it working. Is there a configuration for the BH XDS560V2 to release the JTAG / reset the CPU when the debug session is terminated and disconnected?

Thanks,
Don ...

  • 0
    TI__Expert 4580 points

    Hello:

    We have received your post and will get back to you soon.

    Regards.

  • 0
    TI__Mastermind 22375 points

    Don,

    Basically the access port designator is just a way for the driver to know what AP number is used for the AHB and the APB. Usually these are just AP numbers 0 and 1 (respectively), but the access port designator allows for different APs to be used. 

    There is no documentation anywhere and the only place to find this is in our code.

    As for the second issue, this part is held in common code so both the xds220 and the xds560 should run the core once a session is terminated.

    If necessary, we can attempt to reproduce this locally with a spectrum digital xds560v2.

  • 0 in reply to Jean-Marc Mifsud
    TI__Guru 68920 points

    Don,

    I had a problem similar to the 'it hangs' when trying to download and run a program using debug server scripting.

    When I saw the hang it really wasn't hung just stopped at a breakpoint and not running...

    I found that I needed to change an option in order to make the target run freely after a disconnect.

    See http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/231249.aspx?pi73866=1

    This option may (or may not, I'm not sure... ) be the same as the GUI option:

    So you might try flipping that option and / or playing with some of the others.

    Anyway that's one idea.