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.

  • Resolved

MSP430F5438A: DSLite version 7.2.0.2096 error: MSP430: Error connecting to the target: Unknown device

Part Number: MSP430F5438A

I am trying to make a simple system to program boards from the command line so UniFlash is not needed. I am running version 4.2.0.1490 of UniFlash. I create a "Standalone Command Line" package from within UniFlash. I take the uniflash_windows_64.zip and unzip it into a folder, run "one_time_setup.bat" then "dslite.bat", and DSLite (version 7.2.0.2096) always gives me the following error:

        Executing Startup Scripts: MSP430
Connecting...
error: MSP430: Error connecting to the target: Unknown device
Failed: Operation was aborted

I turned on logging in the dslite.bat batch file (-g blinker.log) and found the following in blinker.log:

0x000017EC 1201 3 MSP430 MSP C: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 )
0x000017EC 6084 3 MSP430 MSP R: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 ) = -1
0x000017EC 6084 3 MSP430 MSP C: MSP430_Error_Number()
0x000017EC 6084 3 MSP430 MSP R: MSP430_Error_Number() = 5
0x000017EC 6084 3 MSP430 MSP C: MSP430_Error_String( 5 )
0x000017EC 6084 3 MSP430 MSP R: MSP430_Error_String( 5 ) = Unknown device
0x000017EC 6084 3 MSP430 GTI R: GTI_CONNECT( 0x02666268 ) = 0xFFFFFFFF
0x000017EC 6084 3  PERF I: GTI_CONNECT finished:  4.884457s wall, 0.000000s user + 0.000000s system = 0.000000s CPU (n/a%)

I can get the device to program from UniFlash itself, but I want to use the command line tool for production. From UniFlash, I get the following in the log (from ds.log):

0x000016A4 344603 3 MSP430 MSP C: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 )
0x000016A4 345270 3 MSP430 MSP R: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 ) = 0

Why is DSLite failing and UniFlash succeeding? Is there a way to get the internal function "MSP430_OpenDevice()" to succeed from the command line through the DSLite tool? Please let me know.

Thank you,

Mike

  • In reply to Mike Ostrego:

    Thanks for confirming. I've passed your feedback along.

    Regards,

    James

    MSP Customer Applications

  • In reply to Mike Ostrego:

    Hello Mike,

    I'm sorry about the delay. The software team is still working to resolve this issue. Could you please try configuring the CLI package to use SLOW JTAG mode? I've attached a target configuration file (.ccxml) for the MSP430F5438A already configured for that mode (configured it using CCS). Using the cloud-based UniFlash tool, select the "Create Session From Existing Target Configuration File" option, choose this .ccxml file, click "Start", and then generate the CLI package.

    Let me know if this works when you can, and thank you again for your patience.

    Regards,

    James

    MSP Customer Applications

  • In reply to James Evans:

    I see that I didn't attach the .ccxml file. Here it is.

    MSP430F5438A.ccxml

    Regards,

    James

    MSP Customer Applications

  • In reply to James Evans:

    James,

    I have been away from this project for a while. Thanks for the update. I will be able to test the configuration file next week.

    Regards,
    Mike
  • In reply to Mike Ostrego:

    Absolutely! No rush, and thanks for letting me know.

    Regards,

    James

    MSP Customer Applications

  • In reply to James Evans:

    James,

    Still no luck with the new configuration file. I'm attaching the terminal log and the executable log I generated by adding the -g option to the dslite.bat file.

    Mike

    terminal.log

    test.log

  • In reply to Mike Ostrego:

    Hello Mike,

    Thanks so much for trying this. I'll relay the log files to our software team and let you know if they find anything.

    Regards,

    James

    MSP Customer Applications

  • In reply to Mike Ostrego:

    Hello Mike,

    Me again. Our software team has created a custom DLL for this case, which I've attached. When convenient for you (no rush), could you please try switching out the DLL used by the MSP430-FLASHER tool with this one, program the device using the MSP430-FLASHER tool, and share the log files? Thanks again for your help and patience. We really appreciate it.

    MSP430.dll

    Regards,

    James

    MSP Customer Applications

  • In reply to James Evans:

    James,

    I tried the new DLL file. New firmware was loaded on my MSP-FET when I ran the dslite batch file.  After the new firmware was installed, it printed out that it was successful in loading the image to the microcontroller.

    Here are the log files:

    new_dll_test.log

    command_prompt.log

    Mike

  • In reply to Mike Ostrego:

    Hello James,

    I tried the MSP-FET with the test firmware back on CSS to see if it would stop the retries I need on the debugger, but CSS loaded the old firmware back on the MSP-FET.

    I wasn't sure if the success with loading the software with the test DLL was a fluke, so I tried the command line again. This time it failed the first time. I tried multiple times with some successes and some failures. The fact that I am getting successes means that I think you are on the right track towards a fix.

    Here are the new log files:

    new_dll_test2_command_prompt.log

    new_dll_test2.log

    Regards,

    Mike

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.