• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 3324 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.

XDS110 Problem with IAR EW ARM7.40.2

SATTAR MALOKANI
Intellectual 555 points
Other Parts Discussed in Thread: ENERGYTRACE

Hi There,

I order MSP432 launchpad and CC2650 Sensor tag and debug pack from TI recently. I am using IAR EW ARM 7.40.2 i am experiencing the XDS110 debugger problem with both boards when using IAR EW. But when I use CCS V6.1 every thing goes fine. Since I am more familiar with IAR EW so I want to use this.

With MSP432 launchpad flashing very simple code BlinkLED takes couple of minutes with IAR EW work bench. When I clicked the run on the IAR EW progm halt and  LED do not blink. And With CC2650 sensor tag simple BLE prephiral program downloads quickly to flash but after running the code I can not put the break point. Console shows message debugger busy. 

Even though I tried on new windows 7. and installed all the driver package but it did not work. Please give some solution. 

thanks

Abdul Sattar

  • 0
    TI__Guru**** 217527 points
    Hello Abdul,

    I'm going to delete your previous post since it is a duplicate of this one, just fyi...

    To interface with the XDS-110ET debugger in IAR & Keil you can try selecting the CMSIS-DAP debugger interface from the drop down menu. CMSIS-DAP is the standardized debugger interface defined by ARM, the XDS110-ET is fully CMSIS-DAP compliant and therefore does not require any driver installation when using any IDEs that support CMSIS-DAP. Otherwise you might want to try contacting IAR themselves for further driver support with their product.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Intellectual 555 points

    Hi Ryan,

    thanks for your reply. Yes I tried CMSIS-DAP it takes too long to download the code to MSP432, i am using very simple example BlinkLED. After long time downloading completes and then i press run on debug,  it responses very slow. and even on break point it hit after some delay in while(1) loop.

    When using the XDS110 download is fast, but when i want to set break point during running it says device is busy. I tried different ways on IAR EW but did not success. 

    Please have a look and suggest solution thanks.

    Abdul

  • 0 in reply to Ryan Brown1
    Intellectual 555 points
    Hi Ryan

    i feel that there is something wrong with my board on debug side. The chip on the debug side marked as IC101 and IC105 are get hot. Would you please suggest why they are getting hot. even though they getting hot but debugger is working fine with ccs v6.1, and debugger is not working with IAR EWARM 7.40.2

    thanks

    Abdul
  • 0 in reply to Ryan Brown1
    Intellectual 555 points

    hi Ryan,

    yes you may delete my previous post, they both are same. I am sorry i posted again because from previous i did not get response.  I have looked at some hardware connection the red marked in above picture are getting hot. please look at my above post and reply me thanks. 

    Abdul

  • 0 in reply to SATTAR MALOKANI
    TI__Guru**** 217527 points
    Abdul,

    Can you describe how hot these devices are getting such as mildly warm, noticeably warm, too hot to touch comfortably, or hot enough to cause a burn? Do they only get hot while debugging in IAR or does the same thing happen in CCS as well? Have you followed all of the instructions listed in SLAU574? www.ti.com/.../slau574.pdf

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Intellectual 555 points

    Hi Ryan ,
    Thanks for your reply. They are getting too hot too touch. The out of box program went very well. Once i started burning simple LED program with iar then debug problem happened it took long time to download. Once i connect usb to MSP432 launchpad board then these two parts getting started hot and even they make the surrounding area of PCB hot. Even though they are hot enough but burning the program with CCS V6.1 goes fine and even debugging.  And I followed all instruction in slau574.pdf. I do not know what went wrong with board. Thanks.


    Abdul sattar

  • 0 in reply to SATTAR MALOKANI
    TI__Expert 7125 points

    Abdul,

    Are these devices only hot when running blink LED? Or hot for any program including the TI provided out of box code?

    Did you make any physical modifications to the PCB? Is anything else connected to the PCB?

    Not sure if you are able- but do you have a way to measure current to the board? The current through the 3V3 jumper in the Isolation Jumper block between the MSP432 and the XDS110 would be helpful to know.

    Are you using EnergyTrace when this occurs? Are the devices hot when using the EnergyTrace functionality?

  • 0 in reply to MikeS
    Intellectual 555 points
    Hi Mike,

    thanks for your reply. These parts are getting hot for any program even out of box. I did not change anything on the PCB. After playing with out of box program. I just burn the BlinkLED program with IAREW, even first time of burning program from IAR it took long time. I tried different time but program did not success so i changed to CCS V6.1 with CSS burning program and debugging went fine. I also connected Kentec QVGA booster pack and program with CCS V6.1, with CCS every thing is ok but these two components are getting hot. For cuurent measurement i will let you know tomorrow. Right now i do not have access to lab. I also ordered sample components they will be delivered tomorrow. So I will let you know details tomorrow.

    Thanks.

**Attention** This is a public forum