• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 78 subscribers
  • Views 789 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/MSP432P401R: Error initialising emulator ? MSP430_RegisterMessageCallback ? Help required

Sean Howson
Prodigy 180 points

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hi

I'm using an MSP432P401R on a prototype board we've just had made, the board uses a JTAG connection with the same interface design used on the red launchpad I had been using for development. 

PROBLEM:

I am struggling to get the brand new, latest, MSP-FET to enter a debug session. I will program the board just fine through UNIFLASH, but fails to enter a debug session (in the latest CCS).

it produces the following error: 

"

Error initializing emulator:
Unable to locate entry point for MSP430_RegisterMessageCallback

"

In fact, it produces this error, EVEN with the usb cable to the debugger unplugged! Implying it's not even got as far as communicating with the MSP-FET yet? 

Similar threads have advices updating the DLL, i've been looking into the this and downloaded what i believe is the most up to date DLL, but to be honest i'm not entirely sure what this does and how to install/build the DLL?

any clues or help would be greatly appreciated. I'm getting fed up of debugging using the 3 LED's on the board and it's not really a viable long term solution!

Cheers,

Sean :)

  • 0
    TI__Guru 59141 points

    Sean,

       I will reach out to the tools team.  I am concerned that it says MSP430 and not MSP432.  Can you confirm that you are using the MSP-FET Adapter,  ?

    Also, that you have selected the correct connection within CCS?

      

    Thanks,

    Chris

  • 0 in reply to Chris Sterzik
    Prodigy 180 points
    Hi Chris

    Thank you for your reply, I'm actually not using the adapter as we are not using an ARM standard JTAG connector. We have our own small adapter (just a bunch of connectors, no active circuitry) that converts the connector on the MSP-FET debugger to the connector on the board. I have made a bid to move to the ARM standard connectors in the past but it hasn't always been well received! :)

    What bugs me is that it will program just fine using UNIFLASH, yet on CCS, this error persists even without the debugger plugged in at all!

    i HAD adjusted the settings for the probe in the CCXML file, but I had NOT made the adjustments in the project menu you showed in the screenshot. Unfortunately making this adjustment made no difference :(
    any ideas?
  • 0 in reply to Sean Howson
    TI__Guru 59141 points
    Since the UNIFLASH is working, a good assumption is that the tool chain and hardware are working. I would recommend uninstalling and then re-installing CCS.

    Chris
  • 0 in reply to Chris Sterzik
    Prodigy 180 points
    Ok Chris, I'm happy to give that a go, could you perhaps first tell me:

    Do you know of any packages or add-on/plugins etc that i should definitely install when re-installing CCS?

    What does the error actually mean? I'd like to understand what is actually happening? I found references to the emulation .gel script in the config for the XML file, is it presumably linked to this perhaps?

    Thanks,
    Sean
  • 0 in reply to Sean Howson
    TI__Guru 59141 points
    Sean,
    It has been a while since I have done an install, but I believe that you only need to select the ARM (MSP432) device package. As far as the error, I do not know.

    Chris
  • 0 in reply to Chris Sterzik
    Prodigy 180 points
    Chris
    Ok seems like we're getting somewhere... Fresh install, now we have the error
    Cannot find a driver for Cpu CORTEX_M4_0
    I'm presuming when configuring the debugger CCS goes through some load of steps/verifications etc and the register call back issue i previously had either came before or after the driver issue i'm now having... hopefully before and now the emulation issue is fine, perhaps? :/
    Cheers,
    Sean
  • 0 in reply to Sean Howson
    Prodigy 180 points
    Edit: getting somewhere, updated debugger firmware, now onto some generic "unknown device" error, when connecting to target... getting really close, had a few errors like this one on uniflash before, probably the way the device is powered interfering a bit, standby
  • 0 in reply to Sean Howson
    Prodigy 180 points
    Sorted! thanks Chris, huge thing ticked of the list of things to do. Couple of updates etc and we're working. Thank you very much :)

**Attention** This is a public forum