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.

IAR Embedded Workbench - TI Plugin

Other Parts Discussed in Thread: CC2640

Hello,

I'm posting here since there's not another forum to post.

IAR Embedded Workbench uses TI provided plugins and tools when debugging devices such as CC2640. In this case, the TI tools are extremely slow when starting a debug session and downloading code. What you can see in the screen is that the debugger loads many workspace screens. The main screen shows a dialog with a progress bar that says "Restoring Desktop" and then it scrolls through a list of supposed windows (I don't have all those RTOS windows open, display is basics Worspace, files disassembly, debug log and build tabs).

Anyone using IAR EW would see this when debugging devices, and sometimes is slows down the process of working significantly.

Having spoken to IAR, they've informed me it is TI that needs to address this.

  • Hi Gustavo,

    I'm assigning this to an expert to comment.

  • Hi Gustavo,

    Thanks for your feedback, will check why this happens and get back to you.

    How long does it take you from pressing the "download and debug" button until you can start debugging? 

    Thanks, 
    Elin

  • Hi,

    Sometimes it will take around 15 seconds, but others it's around 30-45 seconds.

    There's a lot of variability.

  • Hi Gustavo, 

    Thanks for the feedback. 

    I'm currently waiting to hear back from the team, I will let you know as soon as I have an update.

    Thanks, 
    Elin

  • Hi Gustavo,

    The reason why it takes so long to start a debug session is, as you said because EW opens all windows before deciding which are really visible and the TI plugin has a large number of windows. This is actually done to improve the performance later during the session but is, of course, perceived as ineffective when you aren't using all the windows.

    Can you check which version of the plugin you are using? 

    Thanks, 
    Elin