• State TI Thinks Resolved
  • Locked Locked
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 3061 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP432: MDK-ARM Debug with using MSP432 LaunchPad

Kaka
Guru 24520 points
Other Parts Discussed in Thread: SEGGER

Hi TI Expert,

We have met the issue in case of using the MDK-ARM with MSP432 LaunchPad.

[Issue]

The behavior of MDK-ARM is too slow for debug. When my customer run the "step into" on MDK-ARM, the response too late. 

So, my customer checked the USB protocol. And it used the Interrupt Transfer for USB.

 It is set the 0x10 value for bInterval.  So, it seems that this is the cause of this issue.

Do you have any solution to resolve this issue?

And can customer debug the multi MSP432 LPs at the same time?

If you have any question, please let me know.

Best regards.

Kaka

  • 0
    TI__Mastermind 25045 points

    Hi Kaka,

    Kaka said:
    The behavior of MDK-ARM is too slow for debug. When my customer run the "step into" on MDK-ARM, the response too late. 

    How slow?? Just trying to get a feeling on how long does it takes to jump into the function...

    Which µVision IDE version is your customer using?? I'm not experiencing this slow - behavior and it may be related to the target dll. I'm using v5.16.0.0

    Kaka said:
    And can customer debug the multi MSP432 LPs at the same time?

    Yes they can. They will need to have different serial number on each of their launchpads, This will allow them to have more than one XDS110 connected to their system and let the host locate a specific one to connect to.

    They will need to run the following two commands:

    xdsdfu -m
    xdsdfu -s xxxxxxxx -r

    where xxxxxxxx is a serial number, any combination of letters and numbers, from 1 to 8 characters in length.

    You can find the xdsdfu utility in your ccs installation - C:\ti\ccs_base\common\uscif\xds110 and then in your project you can select which debugger to use:

    Regards,

      David

  • 0 in reply to DavidL
    TI__Mastermind 25045 points
    Hi Kaka,

    In order to change the serial number, please make sure that you only have one XDS110 class debug probe plugged in. If not, the xdsdfu program will attempt to flash the first XDS110 debug probe it finds.

    Regards,

    David
  • 0 in reply to DavidL
    Guru 24520 points
    Hi David,

    Thank you for your feedback.
    I will confirm the Keil revision which they have used. And I answered your question as below.

    It took a few seconds(1s ~2s) to run the step in IDE. And when they have used the competitor's debugger(NXP), the time dealy to run was very few time. In addition to this, the flash writing time is so slow against to competitor. So, they think that they can not use this debugger on MSP432 LP for debugging without any stress. They requested to resolve this phenomenon.


    Regarding to the multi debugging of MSP432 LP, I tried to flash the serial number. As a result, we could write the number. But there was not the folder of "XDS110" which you pointed out on your previous post. I find this on following location.
    C:\ti\ccsv6\ccs_base\common\uscif\xds110

    In case of using ARM-MDK, would you please show us the "xds110" directory?
    **It seems that customer should also install the CCS because this directory is in CCS.

    Best regards.
    Kaka
  • 0 in reply to Kaka
    Guru 24520 points

    Hi David,

    I got feedback from my customer. Please see the attached file as below.

    And I got feedback about Debugger. The competitor's debugger is LPC-Link2(NXP) in my previous post.
    If you have any addition questions, please let me know.
    Best regards.
    Kaka

  • 0 in reply to Kaka
    Guru 24520 points
    Hi David,

    Would you please check my response?

    Best regards.
    Kaka
  • 0 in reply to Kaka
    TI__Mastermind 25045 points

    Hi Kaka,

    Kaka said:
    In case of using ARM-MDK, would you please show us the "xds110" directory?
    **It seems that customer should also install the CCS because this directory is in CCS.

    Yes, that is the recommended option. But I zipped that folder from my CCS v6.1.1.00022, please take a look at the readme.txt file. Also, please try to update the XDS110 firmware (instructions are also in the readme.txt file), I would like to see if with this updated firmware, they still get the same ~2s delay.

    Also, it would be interesting if they could run the same test on CCS, just want to make sure that this delay only happens with Keil.

      Thanks,

       David

  • 0 in reply to DavidL
    TI__Mastermind 25045 points

    Hi Kaka,

     After discussing internally, Keil MDK download/debugging speed using XDS110 in CMSIS-DAP mode is a known limitation, so were working with Keil to get this fix, I'm sure that this will improved in the following releases but it is not clear when.

    In the meantime your customer could use one of these external debuggers: SEGGER J-Link or Keil uLink2

      Best regards,

        David

     

  • 0 in reply to DavidL
    Guru 24520 points
    Hi David,

    Thank you for your confirming and response.
    I will inform them to my customer. Could you please inform to me when this issue improve?

    Best regards.
    Kaka
  • 0 in reply to Kaka
    TI__Mastermind 25045 points
    Hi Kaka,

    This post has been closed but will be updated when this fix becomes available. Thank you for your patience.

    Best regards,

    David
  • 0 in reply to DavidL
    Guru 24520 points
    Hi David

    Any update on this?

    Best regards.
    Kaka
  • 0 in reply to Kaka
    Guru 24520 points
    Hi David

    Any update on this?

    Best regards.
    Kaka
  • 0 in reply to Kaka
    TI__Mastermind 25045 points

    Hi Kaka,

    Unfortunately no and it does not seem like this got updated in the MDK-ARM Version 5.18. I'll see if I can get some more information from the Tools team.

    Thanks for your patience.

    Best regards,

    David

  • 0 in reply to DavidL
    Guru 24520 points
    Hi David,

    Thank you for your response.
    I am waiting for your updates.

    Best regards.
    Kaka
  • 0 in reply to Kaka
    TI__Mastermind 25045 points

    Hi Kaka,

      We are planning to release a new XDS110 firmware version that should improve the CMSIS-DAP. I'm trying to get more information on when this version will become available.

       Thanks,

         David

  • 0 in reply to DavidL
    Guru 24520 points
    Hi David,

    Thank you for your confirmation. I understand your situation.
    If you get more information for this topics, please let me know.

    Best regards.
    Kaka
  • 0 in reply to Kaka
    Guru 24520 points
    Hi David,

    Do you have any updates for this topics?
    Can we get the improved the CMSIS-DAP now?

    Best regards.
    Kaka
  • 0 in reply to Kaka
    TI__Mastermind 25045 points
    Hi Kaka,

    It seems like that was the case on V5.20. At the same time the XDS110 debug probe that is used on the TI MPS432 Launchpad is also supported.

    Regards,

    David
  • 0 in reply to DavidL
    Guru 24520 points
    Hi David,
    I checked the behavior of MDK-ARM but it it seemed that it was too slow for debug. Did you resolve this issue?
    I used the XDS110-ET debug probe on MSP432LP.

    Best regards.
    Kaka

**Attention** This is a public forum