• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 52 subscribers
  • Views 3118 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.

DSS - FET Communication Issues

Joshua Lawes
Intellectual 650 points
Other Parts Discussed in Thread: MSP430F249, CCSTUDIO

I am receiving various errors (much more frequently since updating to Code Composer 4.2.3 from 4.0.1) when attempting to connect/load SW to my MSP430F249 target via an MSP-FET430UIF using DSS (javascript).  One example is below.  I would like to know how to avoid these errors completely so that I can test/qualify my software...

SEVERE: MSP430: Trouble Writing Memory Block at 0x2100 on Page 0 of Length 0x29e2: Could not communicate with FET

SEVERE: File: R:\Projects\TPM\Software\Calibration\Debug\Calibration.out: Load failed.
SEVERE: Error loading "R:/Projects/TPM/Software/Calibration/Debug/Calibration.out": File: R:\Projects\TPM\Software\Calibration\Debug\Calibration.out: Load failed.

I follow the proceeding steps when attempting to :

// Import Java & DSS Packages into namespace
importPackage(Packages.com.ti.debug.engine.scripting)
importPackage(Packages.com.ti.ccstudio.scripting.environment)
importPackage(Packages.java.lang)

// Obtain singleton instance of the scripting environment, factory for creating servers and sessions
env = ScriptingEnvironment.instance();   
       
// Set timeout (ms) for all calls to the debug script server
env.setScriptTimeout(myScriptTimeoutValue);
   
// Start debug scripting server
debugServer = env.getServer("DebugServer.1");
debugServer.setConfig(myMSP430F249configFile);
debugSession = debugServer.openSession(".*");

// Connect to target
debugSession.target.connect();

// Load the primary software to target
debugSession.memory.loadProgram(myPrimaryExecutable);

Any help would be greatly appreciated!!

Thanks,

--

Joshua

 

  • 0
    Intellectual 650 points

    Note also that if the board is feeling particularly friendly and decides to allow me to connect and load SW, then I am finding the following error when attempting to run the target post halt.

    SEVERE: Timed out after 100000ms
    SEVERE: com.ti.debug.engine.scripting.Target.run(): Timed out after 100000ms

  • 0 in reply to Joshua Lawes
    TI__Guru**** 450031 points

    Hi Joshua,

    Do you only see errors when running from DSS or do you see it when using the CCS IDE?

    ki

  • 0 in reply to Ki
    Intellectual 650 points

    Hi Ki,

    Thanks for the response.  I do occasionally see the memory block reading error in the CCS IDE when debugging the active project.  Once it occurs, the only solution seems to be to disconnect/reconnect the FET and/or restart CCS.

    Cheers,

    --

    Josh

  • 0 in reply to Joshua Lawes
    TI__Guru**** 450031 points

    Joshua Lawes said:
    Once it occurs, the only solution seems to be to disconnect/reconnect the FET

    You mean physically disconnect the FET from the PC or just disconnect CCS from the target (CCS target disconnect)?

  • 0 in reply to Ki
    Intellectual 650 points

    Sorry for the ambiguity, yes just CCS target disconnect.

  • 0 in reply to Joshua Lawes
    TI__Guru**** 450031 points

    Joshua - can you turn on Debug Server Logging and then reproduce the issue and then send the log to us? If the log is huge, send me a private message and I'll send you a place when you can mail it to.

    For more details on how to enable Debug Server Logging, see:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 650 points

    Hi Ki,

    Just as an update, I've been doing a lot of manual testing of my software this past week and haven't seen the FET problem mentioned (in the original post) for quite some time.  As a result I reviewed my test scripts and realised that if ever there is an error, I'm not disconnecting correctly from the FET.  So now I've added a try/catch clause so that the FET will always be disconnected (rookie error)...

    The issue described in the following quote is still present however as it is more intermittent, I'll send you a log when I can.

    Joshua Lawes said:

    Note also that if the board is feeling particularly friendly and decides to allow me to connect and load SW, then I am finding the following error when attempting to run the target post halt.

    SEVERE: Timed out after 100000ms
    SEVERE: com.ti.debug.engine.scripting.Target.run(): Timed out after 100000ms

     

  • 0 in reply to Joshua Lawes
    Intellectual 650 points

    Hello,

    To further increase stability of the FET when switching between multiple projects/builds within the same DSS session, I found it helped to also create a single configuration file in a shared location and link to it from each project, rather than creating a separate configuration file for each project.

    Cheers,

    --

    Joshua