• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 312 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.

TMS320F280049C: Code Composer Studio crashing during life debug

Lennart Gardian2
Intellectual 270 points

Part Number: TMS320F280049C
Other Parts Discussed in Thread: TMS320F2806

Hi there,

I'm facing the issue that my Code Composer Studio is constantly throughing the error "Trouble Reading Memory Block" when I try to debug my ADCs.

In detail I place a brakepoint that I set to "Refresh All Windows" and add the ADCRESULT variable to the watch expressions so that I can look at life updates of the ADCRESULT register or even plot the data into a graph. So far everything works fine. The problem occurs when I stop the debug session and restart it. It loads the program and than throughs the above error. Or to be more precise:

C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8 
IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0xc8

Despite of the error the debug sessions seams to work fine but I had a bunch of cases where it seemed to me that it didn't and problems like "the ISR is being called anymore" occured or could it be that I thinks it's not being called because CCS can't find the breakpoints anymore?


So I wonder whether the above is a known issue, whether there are some guidelines how to avoid it and whether the error really can effect my debug session or whether it can be ignored?!

Thanks a lot!

  • 0
    TI__Genius 15385 points

    Hi,

    Can you give more details on how you stopped the debug session and restarted?

    Did you hit the Stop button on the CCS? 

    What happens if you power down and reconnect the debugger and reload the program?

    Best Regards,

    Nirav

  • 0 in reply to Nirav Ginwala
    Intellectual 270 points

    Hi Nirav,

    I first just restarted the debug session which than pops up a promt telling me that I need to stop the debug session what it automatically does then. Then I saw the issues and started to use the stop button but it didn't change anything.
    If I reconnect the launchpad board without restarting the CCS the issue remeains. If I just restart CCS without reconnecting the eval board the issue is gone.

    I'm facing a farely similar problem with an old TMS320F2806 project and a custom board which I connect to with an XDS200 debugger. I regularly need to reconnect the debugger to be able to set breakpoints.

  • 0 in reply to Lennart Gardian2
    TI__Genius 15385 points

    It looks like your code is stuck in some loop when you are trying to do restart, and then when you hit stop it somehow corrupts JTAG scan. Can you put a break point in your code, and once it reaches the breakpoint you can hit restart.

    Also to make sure you are using the latest CCS version?

    Best Regards,

    Nirav

  • 0
    Intellectual 270 points

    Hi Nirav,

    I just double checked on it and yes the issue occurs even though the program hits a breakpoint, I press the stop button and restart the debug command again. On the restart I get the above errors. During the last week or so I couldn't realise the issue anymore that the initial breakpoint on main entry couldn't be found anymore. In fact I couldn't realise any issue except of the error message.
    During the last week I was only working with the 280049C launchpad and not with the TMS320F2806 custom board.

    The CCS version is 10.2.0.00009

  • 0 in reply to Lennart Gardian2
    TI__Genius 15385 points

    Hi Lennart,

    When you hit "Stop" button it disconnects the debugger, and you will have to load the board configuration file again. Also the device is powered up while you hit Stop. Rather you should hit restart instead of "Stop".

    Best Regards,

    Nirav