• Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 575 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.

CCS 6.2.0 w/launchpad 432 won't run debug under linux, weird state

robert schaefer
Expert 2050 points

 I load the program w/ debug, but on completion see the debug state toggling between running and reset very quickly and doesn't stop.

 I can't get any further. What would cause this?

 This same project loads/debugs ok under Windows, but causes the resume button to remain greyed out on the mac - as previously noted in my entry titled: NO 'Run' options are eabled in CCS 6 debugger (resume, suspend, terminate, step-into .... etcetera).

thanks,

bob s.

  • TI__Guru**** 476091 points
    Hello Bob,
    Could you provide the executable you are loading? And which 432 launchpad are you using? The red one or black one?

    Thanks
    ki
  • in reply to Ki
    Expert 2050 points

    Hi,

    I've got two black 432's. I sometimes see warning messages in CCS saying they are out-of-date but still supported.

    Can I attach a tar.gz?RapidEnergyUnit.tar.gz

  • in reply to robert schaefer
    Expert 2050 points
    Additional notes:
    The file charge_control.c is in process (not all hardware is there yet), it can be part of the build or excluded from the build as it is not yet called.
    I will be ported this code to a bespoke card w/the 432 processor, once I figure out how to get the jtag emulator XDS 200 to work.
    bob s.
  • TI__Guru**** 476091 points

    Thanks,

    I can reproduce this issue.

    A few observations.

    robert schaefer said:
     This same project loads/debugs ok under Windows,

    This is NOT the case for me. The same exact behavior occurs with CCS 6.2.0 on my Windows 7-64 PC

    Also - once I load and run that program to my black MSP432 LaunchPad, it puts it in a bad state where subsequent attempts to connect to the CPU fail with a "Device ID not recognized" error. Likely the program overwrote some area of flash it should not have been. I had to factory reset the LaunchPad to get it working again. Did you have to do this also?

    Thanks

    ki