• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 67 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.

MSPM0L1106: XDS110 vs J-link initialization behavior

Munan Xu
Expert 4430 points
Part Number: MSPM0L1106

Tool/software:

Hello,


I had a customer who's using both the XDS110 and J-Link debuggers to develop their application. One thing they've noticed is that the same code which works on J-Link doesn't work with the XDS110. Neither application when programmed and running standalone after a hard reset worked as expected. We isolated this down to an initialization sequencing issue where the customer was writing to timer registers before PWREN was asserted. So obviously changing the order of operations here solved that problem. 

However, this leads to a more interesting question of why does the J-Link code work while debugging? Does J-Link initialize and enable all the peripherals on the device which is what this behavior implies? Any insights into the initialization differences between XDS110 and J-Link?

Munan

  • 0
    TI__Expert 4430 points

    Oh also if it makes any difference and I'm fairly sure it might, customer is using IAR 9.50

    Munan

  • 0
    TI__Prodigy 680 points

    Hey Munan,

    JLink should function the same as the XDS110 where both will just be the bridge between the device and PC. In terms of peripheral initialization there is no dependency on the debugging tool used.

    My theory as to why there is a difference would be the flashloader implementation. Their implementation might have done some padding maybe that could have affected the image?

    Henry