• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 2264 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Trying to debug MCBTMS570 Eval board with Blackhawk USB100v2 debugger

Florian Rees
Prodigy 80 points

Hy,

I am trying to develop with the MCBTMS570 eval board from Keil. Debugging via the direct USB debugger on board is possible but very slow.
So now I am trying to get the Blackhawk USBv100v2 to work.

I followed this quick start guide: http://www.blackhawk-dsp.com/downloads/docs/guides/USB100v2-QS-01.pdf
Datasheet and quickstart guide for this and similar products can be found on: http://www.blackhawk-dsp.com/support/Docs.aspx#BH-USB-100

As the product I got was delivered with the quick start guide for USB100v2 (and 'not' model D)  I suppose I have this one.
But it doesn't really matter as the quick start guide is quite the same.

I am trying to get a debug conntection and this fails completely. So I think the problem is probably in the target device configuration. Which is all in Step 4 of the quick start guide.

Drivers:
I installed CCS4 and I am 100% sure I did it before I connecte the debugger as it is suggested in the manual.
I think the emulation driver from FTDI are installed successfully, as I get the device twice in the windows device manager as TI XDS100 Channel A and B.

Hardware installation:
I am 100% sure I attached the connectors in the corredt order since the first timer of connecting.

Any tipps how to configure this different to get a debug connenction?

 

Thanks

Florain

  • 0
    TI__Mastermind 30845 points

    Florian,

    Just to be clear, you are trying to connect using CCS4 and not Keil uVision, correct? And the onboard XDS100v2 on the MDK works fine?

    >>I am trying to get a debug conntection and this fails completely. So I think the problem is probably in the target device configuration. Which is all in Step 4 of the quick start guide.

    What kind of a failure are you seeing?

    Regards,

    Abhishek

  • 0
    TI__Guru 68830 points

    Hi Florian,

    The USB emulator on the Keil MCBTMS570 is an XDS100v2,  it's just embedded onto the board.

    So:

      - you should be able to use the same driver and configuration for the on-board XDS100v2 as for the standalone XDS100v2.

      - unfortunately, you'll get the same performance.

    There are a few things you can try in the configuration of CCS to speed up the XDS100v2.   You might try:

       1) choosing adaptive clocking and setting a max clock more like 3MHz for TCK (vs. default 1MHz)

       2) change your CCS option under Tools->On Chip Flash,  Erase Flash,  From "Entire Flash" to "Necessary Sectors Only".

           if you're just doing small programming examples then this will speed things up when you reprogram.   The TMS570 has a very large on chip flash (2MBytes) so it can take a long time if you always erase the whole flash but only needed to erase a few 100K bytes.

    But, the xds100v2 is really an evaluation tool - you should probably step up to a more powerful and faster emulator for serious work.

    Best Regards,

    Anthony

  • 0 in reply to A Arora
    Prodigy 80 points

    Hello Abhishek,

    I am using CCS4 but including the automated updates. I did hope, that the Debugger would speed up debugging, but as the next post answers it won`t(I will answer this extra).  At the momemt I am not definitely  which error code I am getting, but it's about that I am not getting any connection.
    Thanks so far!
    Florian

  • 0 in reply to Anthony F. Seely
    Prodigy 80 points

    Hello Anthony,

    I thought something like that as it is working with the target device XDS100v2. Anyway I didn't order this debugger I just have no other tool at the moment. One question to
    '-unfortunately, you'll get the same performance':

    If there is the same harware on the Keil board as the XDS100v2. Means that this includes the same FTDI IC? Depending on IC I suggest this mainly slowes the speed of the connection, so the fast JTAG connection would be quite useless here.
    Am I right?

    But I think its still strange why the external Blackhawk is not getting a connection. Or is there something with the MCBTMS570 JTAG connection I missed?

    Anyway I thank you for the good tipps for debugging.


    But I couldn't follow the two of your following steps:

      1) choosing adaptive clocking and setting a max clock more like 3MHz for TCK (vs. default 1MHz)

       2) change your CCS option under Tools->On Chip Flash,  Erase Flash,  From "Entire Flash" to "Necessary Sectors Only".

    If it matters I have CCS  4.1.3.00038.
    If I am just blind please just write out your steps more precisely.

    Thanks!
    Florian

  • 0 in reply to Florian Rees
    Prodigy 80 points

    Another question Anthony,

    maybe there is a possibility that I get another Debugger. Can you recommend some. I think I read a list of debuggers in this forum some time ago.

    But I would like to know of someone who is working successful with it. So I have a feedback.

    Thanks

    Florian

  • 0 in reply to Florian Rees
    TI__Mastermind 30845 points

    Florian,

    you can find some information here and here.

    I know more 3rd parties support our devices than listed above and we are working on updating our product/wiki pages with that information.

    Regards,

    Abhishek