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.

Debugger dies in CCS 4.1.1 on Windoows7

Other Parts Discussed in Thread: MSP430F5438

Hi,

t worked in previous version of v4.1.0 on Windows 7, but now the debugger died in 20 steps through. Any idea?

 

Thanks.

  • Can you provide some more info?

    Win7 32 or 64?

    What emulator?

    What device?

     

    What is meant by dying?  Are you stepping through code and something happens after stepping 20 times?

     

    John

  • Thanks John. Customer is using Windows 7 64-bit mode. They are using FET430UIF, and targeting MSP430F5438. They have another question:

    They told me the CCS v4 cannot generate hex file after the compile is completed. I think this is related to settings issue, but they said they have gone through everything in IDE, but they did not find a solution. The option is grayed out.

     

    Thanks!

  • For the question about generating hex file, this is set up under Project Build Properties->Build Steps->Post-build step. There are some pre-defined steps which create TI-TXT or Intel hex images which they can select, or create a command of their own. I've used this with CCS 4.1.1 and it works.

  • I have been playing with a F5438 on my Win7 64b laptop this morning and I can't get it to lock up.  

    A couple of thoughts:

    • The program could be doing something that triggers CCS to lose the connection.  If you could send me the program I could try loading it on my board to reproduce.
    • Maybe one of the views (watch, registers, memory) is viewing something that causes a problem with CCS when reads memory to refresh them.  If you could get a screen shot of what their CCS looks like I could set mine up the same.

    John