• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 2160 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.

CC430F5137 Debugging Problem: Could not read Enhanced Emulation Module register

Ismail Uluturk
Prodigy 20 points
Other Parts Discussed in Thread: CC430F5137

    Hi all,

    I have a custom designed board with a CC430F5137 and i am trying to debug it from Spy-Bi-Wire with no joy. Chip is successfully recognized as CC40F5137 and code is downloaded to device without any problems( at least it seems like that, i don't have my leds populated because there was a mix with my parts order so i can't really check but it appears fine). But after the download when i try to run/step my program i get these errors:

MSP430: Program loaded. Code Size - Text: 146 bytes Data: 4 bytes
MSP430: Can't Run Target CPU: Could not read Enhanced Emulation Module register
MSP430: Can't Single Step Target Program: Could not read Enhanced Emulation Module register
MSP430: Failed Software Reset: Could not read Enhanced Emulation Module register

   The code I am trying to debug is an example from TI and same problem appears with test codes i have written so I don't think thats the case. Code Composer Studio version I am using is Version: 4.2.4.00033 .

   Debugger I am using is eZ430-RF USB debugging interface(The one that comes with the chronos watch). I can debug my chronos with it so I don't think the problem is caused  by that as well.  Board is powered from debugger while being programmed/debugged.

 I searched this error but failed to find anything. I wonder what are the possible causes for such an error.

Thanks for your help.

 

 

 

  • 0
    Guru 227245 points

    The EEM is a hardware register that is accessible through (and only through) the JTAG connector. It is configured by the debugger to halt the CPU when a certain operation is performed by the CPU. (breakpoint).
    It has nothing to do with your program.

    That the EEM register cannot be accessed is basically a hardware error. Eithe rthere is a problem with your FET firmware or with the connection between FET and target MSP or with the target MSP itself (low supply voltage, whatever)

    usually you'll get a 'cannot find device or device not supported' error in this case, but i tseems that the physical constellation is stable enough to establish a JTAG connection and identify the MSP.
    The interesting part is that you seem to be able to download the program to the MSP. But when the debugger tries to set its default breakpoints (start of main etc.) it fails. No idea why. Wrong target device selected? (normally, it should complain then)

  • 0 in reply to Jens-Michael Gross
    Prodigy 20 points

    I have solved the problem, The cause was a  a mix-up in the soldering stage, there was a capacitor where the pull-up on the reset line should be, and a 47k Ohm resistor where the capacitor should be. Swapping them solved the problem, I can download and debug code without any problems now.  Thanks for your help.

  • 0 in reply to Ismail Uluturk
    Guru 227245 points

    Ah, so the MSP started and did run long enough to establish the JTAG connection and identify the chip, but then got into reset again due to the pulldown. Or something like that.
    Interesting.

    Glad you found he offending hardware :)

**Attention** This is a public forum