• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 531 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.

CCSv4 continual crashes (MSP430 target)

Tom Rocks
Prodigy 80 points

Other Parts Discussed in Thread: MSP430F5528

Hi,

I've been working on an MSP430 project (MSP430F5528 target) with CCSv4.2.3.00004. As of today I am unable to debug my project as CCS crashes during the loading process of the debugger. The following describes the problem:

This morning when I first attempted to connect and debug the project I got the following error:

MSP430: Trouble Reading Memory Block at 0x4400 on Page 0 of Length 0x10c: Could not communicate with FET
MSP430: File Loader: Data verification failed at address 0x00004400 Please verify target memory and memory map.
Error found during data verification.
Ensure the linker command file matches the memory map.

On attempting to debug again, CCS crashed with the exit code -1073741819 and the following error message:

This same crash recurs whenever I attempt to debug my project.

I have tried renaming the ctools.dll file (as recommended in http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/36438/127741.aspx?PageIndex=1), and I have tried witha  clean workspace, (as recommended in http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/72329/262723.aspx#262723).

Attached are a couple of log files taken using DebugView

5861.CCS debug error log.1.log

3755.CCS debug error log.2.log

If you could help solve this problem I would be very appreciative.

 

 

PC: Windows XP SP3, Lenovo Thinkpad X60s.

Debugger: Olimex MSP430-JTAG-ISO

Target: MSP430F5528

CCS: 4.2.3.00004, "C:\program files\texas instruments\ccsv4\"

There is no ccxml file in the "<user name>\user\CCSTargetConfigurations" directory.

  • 0
    Prodigy 80 points

    I have tried uninstalling CCS and reinstalling the latest version (1.2.4.00033). Now I am able to connect to the debugger, but clicking Terminate All causes CCS to crash in the same way.

  • 0 in reply to Tom Rocks
    TI__Guru**** 173310 points

    Have you tried to rename the ctools.dll with 4.2.4 to see if it helps with the crash during "Terminate All"?

  • 0 in reply to AartiG
    Prodigy 80 points

    I have tried renaming ctools.dll with the 4.2.3.0004 release, however currently I can't even get the debugger running - CCS crashes with the popup error (screenshot above) whilst trying to start the debugger.

    Previously I had enjoyed using CCS, but it's turning into a nightmare. I'm spending more time solving problems with CCS (see two other posts of mine on e2e in the past week) than I am doing any work.