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.

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

Part Number: MSP430F5438A
Other Parts Discussed in Thread: UNIFLASH, , MSP430F6736, MSP-FET, MSP430F5438, MSP430-FLASHER, MSP-FLASHER, TEST2

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

  • Hello Mike,

    Thank you for your detailed post.

    My first suggestion would be to try updating to the latest offline version of UniFlash, which is version 4.2.1.1562. Perhaps this issue has been fixed.

    If that doesn't work, can you try using our online version of UniFlash and see if this issue still exists? I did this for our MSP430F6736 device, and the Standalone Command Tool worked fine. According to the output in the terminal, I was using DSLite version 7.2.0.2152.

    Here's the link to our cloud-based UniFlash: https://dev.ti.com/uniflash/

    Here are the instructions for generating the Standalone Command Tool: processors.wiki.ti.com/.../UniFlash_v4_Quick_Guide

    When running the two .bat files, you may need Administrator privileges. In the meantime, I'll loop in our Tools team to make them aware of this issue.

    Regards,

    James

    MSP Customer Applications
  • Hello James,

    I downloaded and tried the new UniFlash (version 4.2.1.1562). This contains DSLite version 7.4.0.1095. I still received the "unknown device" error. Then I tried the online UniFlash version 4.2.0.1490, which contains DSLite version 7.2.0.2152, and I still am getting the "unknown device" error. I ran the Windows command prompt in Administrator mode in both cases (I am running this on Windows 7). I have been trying this out with the MSP-EXP430F5438 development board and the CCS v7 Blinker test code compiled to a .hex file.

    Can you try this out on your end with an actual MSP430F5438A part and see if it works for you? Maybe you could use the MSP-EXP430F5438 dev board if you have one.

    Here's what I've been seeing from the MSP-FET device itself. When the MSP-FET first tries to program, the red Mode LED blinks and the green Power LED stays off. It fails to program and the green power LED turns on. At this point, UniFlash gives me the option to retry, but DSLite just aborts. On the retry from UniFlash, the green power LED stays on while the red mode LED keeps blinking and the part actually gets programmed. Can you put this retry feature in the DSLite program, or could you just fix the code so that it retries on its own?

    I guess let me know if you can get this to work on a MSP430F5438A part on your end. I am running out of ideas on my end.

    Thanks,
    Mike
  • James,

    I am going to try to attach the log from my trial with DSLite version 7.4.0.1095 and UniFlash Version: 4.2.1.1562.

    Mike

    0602.blinker.log

  • Hello Mike,

    Thanks for the additional details and for the log file. I tried to duplicate your issue on my side with a target socket board, MSP-FET, and MSP430F5438, but everything worked as expected using the cloud-based UniFlash CLI and the msp430x54x_fet_1.c.out file generated in CCS v7.2.0. My PC is Windows 7 64-bit as well.

    Did you purchase your MSP-FET recently? Also, can you tell me which version of CCS v7 you have?

    Regards,

    James

    MSP Customer Applications
  • Hello Jason,

    My MSP-FET and MSP-EXP430F5438 experimenter board were purchased in May of this year. The sticker on the MSP-FET box shows "SEAL DT 10/25/16".

    I am currently using CCS v7.2.0.00013, but I have installed several updates since the initial install of CCS 7.2.
    From the Installation History tab in CCS:
    8/3/17, 12:26:24 PM CDT Installed Code Composer Studio 7.2.0.00013.
    8/3/17, 12:41:49 PM CDT Installed org.eclipse.rtsc.xdctools:3.32.2.25, org.eclipse.rtsc.xdctools:3.50.2.20
    8/15/17, 10:01:44 AM CDT Updates include: com.ti.cgt.msp430.16.win32,com.ti.msp.debug_probe,com.ti.msp430.ccs_header_files,com.ti.msp430.gcc_header_files,com.ti.msp430.support_files
    9/20/17, 10:25:24 AM CDT Updates include: com.ti.gcc.msp430.win32
    10/10/17, 9:39:47 AM CDT Updates include: com.ti.dsflash.win32

    As a test, I tried using the .out instead of the .hex file (since you said you had tested with msp430x54x_fet_1.c.out). I'm still receiving the "Unknown device" error with the .out file when running the dslite.bat file.

    Do you think there is an issue with the MSP-FET firmware? Is there a way for me to tell what version of firmware is running on the MSP-FET?

    Regards,
    Mike
  • Hello Mike,

    Thank you for the additional information. I'm sure this will help our Tools team figure out what's going on. I've looped them in and am waiting for their feedback.

    While we try to figure out the issue with the CLI package, another command line tool that we offer is MSP430-FLASHER. I used the following command to check the MSP-FET's firmware version using the command "MSP430Flasher.exe -i DETECT" executed in a terminal window while inside the MSPFlasher folder (for me it's C:\ti\MSPFlasher_1.3.15). If the firmware is too old, then MSP430-FLASHER may not show it. When executing the command above when the MSP-FET has an older firmware version, it will probably ask you to update the firmware.

    You could try installing and using the latest MSP430-FLASHER to upgrade your MSP-FET's firmware and then try programming the MSP430F5438A. I've included the MSP Flasher's User's Guide below for your reference. Section 3 contains the available Triggers and Arguments, and Section 4 contains Exit Specifications. Section 7 includes several example commands for loading and executing code from a .txt file.

    If you have any questions about the MSP430-FLASHER or encounter any issues, please let me know. Hopefully, this helps you move forward in your development.

    Regards,

    James

    MSP Customer Applications

  • Hello James,

    I tried the MSP Flasher v1.3.15 software with the -i DETECT option. It said that the FET firmware was up to date.
    The rest of the information I pasted below:
    * Arguments : -i DETECT
    * -----------------------------------
    * Driver : loaded
    * Dll Version : 31001000
    * FwVersion : 31000003
    * Interface : DETECT
    * HwVersion : U 3.0
    * JTAG Mode : AUTO
    * Device : MSP430F5438A
    * EEM : Level 7, ClockCntrl 2
    * VCC OFF

    I decided to try to use the Flasher software to program the MSP430 from the command line. With the .hex file as-is from the CCS software, the Flasher came back with "ERROR: File type could not be identified." I then changed the first character of each line of the .hex file from "%" to ":". The Flasher software then came back with "ERROR: Error within Intel Hex file. I tried with both Unix and DOS EOLs, same error in both cases.

    As a final shot at this, I set out to find how to make TI text files in the compiler. In Project -> Properties -> CCS Build -> MSP430 Hex Utility, I clicked on "Edit Flags..." and added "--ti-txt". I then tried the MSPFlasher with the TI text file produced by the Hex Utility. It works. I now have a way to program the TI MSP430 parts from the command line.

    In conclusion, don't get rid of the MSPFlasher program. I saw in several places it is deprecated, but it seems that right now, it is the only way for some chips to be programmed from the command line.

    Regards,
    Mike
  • Hello Mike,

    Thanks for the update. I'm glad to hear that the MSP430-FLASHER works well for you with the TI text file. Even though certain flags/features are deprecated, I don't expect that the MSP430-FLASHER will go away any time soon.

    I haven't heard back yet from our Tools team about the CLI issue, so just continue using the MSP430-Flasher moving forward. If you have any more issues, please let me know.

    Regards,

    James

    MSP Customer Applications
  • Hello James,

    Thanks, I will continue to use the MSP Flasher software for now. If the Tools team solves the CLI issue, please respond on this thread so I will know to update my UniFlash installation.

    Regards,
    Mike
  • I'll do that. If you have any other issues, don't hesitate to let us know.

    Regards,

    James

    MSP Customer Applications

  • Hello Mike,

    Quick update - the software team is trying to replicate your issue but haven't been able to yet. They had a few follow-up questions.

    • Which device revision of the MSP430F5438A are you using?
    • Which JTAG interface (2-wire SBW or 4-wire JTAG) are you using?

    I know that the MSP430-FLASHER can automatically detect which JTAG interface to use (based on your hardware configuration), but I'm not sure that the CLI can do that. Perhaps, it's using the wrong interface which could be causing this error message.

    Regards,

    James

    MSP Customer Applications

  • Hello James,

    Thanks for the update. As far as the device revision of the MSP430F5438A, I don't know. It looks like I have to write some code to query the TLV registers, and send you the results. I am using the 4-wire JTAG interface. Our schematic for the JTAG is consistent with the signal connections shown in Figure 2-1 of SLAU278Y.

    Regards,
    Mike
  • Hello Mike,

    Thanks for the information and for following the recommended connections in Figure 2-1 (this is very important for proper JTAG operation). You may be able to identify the revision by looking at the top of the package. Typically, "REV x" is shown where x is the specific revision code.

    Regards,

    James

    MSP Customer Applications
  • Mike,

    In your original post, you mentioned that you are able to program your device using the GUI, is this consistently working? And consistently failing using CLI (DSLite)?

    If so, can you also provide the Debug Sever Logging for the GUI run? I think you already provided the log for the failing CLI run, so I want to try comparing the 2 log files to see what the difference is.

    Thanks,
    Ricky
  • I checked the package. I am using a rev. F part.
  • Hi Ricky,

    I am able to program with the GUI, but the first attempt always fails. So, yes, it is consistent in that regard. Yes, I have never been able to program the part with the standalone command line tool.

    I will get you a log of the GUI programmer soon.

    Regards,
    Mike
  • Mike,

    Interesting; so it always fails the first time in the GUI? Maybe that explains the difference between the GUI and CLI flow, since you will not be able to make a 'second' attempt at programming it without closing down everything and restarting in CLI.

    Hopefully the GUI logs will provide some useful information on what the cause of this behaviour is.

    Thanks,
    Ricky
  • Ricky,

    I am attaching the log file from the UniFlash programming run. Here's the brief output from the UniFlash console:

    [11/15/2017, 4:53:58 PM] [ERROR] MSP430: Error connecting to the target: Unknown device

    [11/15/2017, 4:54:05 PM] [INFO] MSP430: Flash/FRAM usage is 2552 bytes. RAM usage is 215 bytes.

    [11/15/2017, 4:54:05 PM] [SUCCESS] Program Load completed successfully.

    Mike

    ds.log

  • Hello Mike,

    Thanks for providing the device revision. Are you using an external power supply to power the device when you're programming it with the MSP-FET or are you using the MSP-FET to power the device?

    Thank you for your patience and feedback here as we try to narrow down the issue.

    Regards,

    James

    MSP Customer Applications
  • Hi James,

    I am using an external power supply to power the MSP430.

    Regards,
    Mike
  • Thanks for confirming. I've passed your feedback along.

    Regards,

    James

    MSP Customer Applications
  • 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

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

    MSP430F5438A.ccxml

    Regards,

    James

    MSP Customer Applications

  • 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
  • Absolutely! No rush, and thanks for letting me know.

    Regards,

    James

    MSP Customer Applications
  • 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
    C:\test>dslite.bat
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_f
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Parsing connections/TIMSP430-USB.xml
            Parsing drivers/msp430_emu.xml
            Parsing devices/MSP430F5438A.xml
            Parsing ../options/MSP430F5438A_TI.xml
            Parsing ../options/MSP430F5438A_GNU.xml
            Parsing ../cpus/MSP430Xv2.xml
            Parsing ../Modules/msp430/ADC12_2.xml
            Parsing ../Modules/msp430/CRC16_2.xml
            Parsing ../Modules/msp430/DMA_6.xml
            Parsing ../Modules/msp430/Flash_6.xml
            Parsing ../Modules/msp430/MPY_16__Multiplier__16_Bit_Mode_1.xml
            Parsing ../Modules/msp430/MPY_32__Multiplier__32_Bit_Mode_1.xml
            Parsing ../Modules/msp430/Port_A_1.xml
            Parsing ../Modules/msp430/Port_1_2_5.xml
            Parsing ../Modules/msp430/Port_B_1.xml
            Parsing ../Modules/msp430/Port_3_4_4.xml
            Parsing ../Modules/msp430/Port_C_1.xml
            Parsing ../Modules/msp430/Port_5_6_3.xml
            Parsing ../Modules/msp430/Port_D_1.xml
            Parsing ../Modules/msp430/Port_7_8_3.xml
            Parsing ../Modules/msp430/Port_E_1.xml
            Parsing ../Modules/msp430/Port_9_10_3.xml
            Parsing ../Modules/msp430/Port_F_1.xml
            Parsing ../Modules/msp430/Port_11_1.xml
            Parsing ../Modules/msp430/Port_J_1.xml
            Parsing ../Modules/msp430/PMM__Power_Management_System_2.xml
            Parsing ../Modules/msp430/RC__RAM_Control_Module_1.xml
            Parsing ../Modules/msp430/Shared_Reference_1.xml
            Parsing ../Modules/msp430/RTC__Real_Time_Clock_1.xml
            Parsing ../Modules/msp430/SFR__Special_Function_Registers_1.xml
            Parsing ../Modules/msp430/SYS__System_Module_2.xml
            Parsing ../Modules/msp430/Timer0_A5_1.xml
            Parsing ../Modules/msp430/Timer1_A3_1.xml
            Parsing ../Modules/msp430/Timer0_B7_1.xml
            Parsing ../Modules/msp430/UCS__Unified_System_Clock_1.xml
            Parsing ../Modules/msp430/USCI_A0__UART_Mode_2.xml
            Parsing ../Modules/msp430/USCI_A0__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B0__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B0__I2C_Mode_3.xml
            Parsing ../Modules/msp430/USCI_A1__UART_Mode_2.xml
            Parsing ../Modules/msp430/USCI_A1__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B1__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B1__I2C_Mode_2.xml
            Parsing ../Modules/msp430/USCI_A2__UART_Mode_1.xml
            Parsing ../Modules/msp430/USCI_A2__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B2__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B2__I2C_Mode_1.xml
            Parsing ../Modules/msp430/USCI_A3__UART_Mode_1.xml
            Parsing ../Modules/msp430/USCI_A3__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B3__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B3__I2C_Mode_1.xml
            Parsing ../Modules/msp430/Watchdog_Timer_2.xml
            Parsing ../Modules/msp430/MSP430Xv2_NotVisible.xml
            Initializing Register Database...
            Parsing C:\Users\xxxxx\AppData\Local\TEXASI~1\CCS\C_drive\2\0
            Initializing: MSP430
            Mapping registers: MSP430 - Core Registers
            Mapping registers: MSP430 - ADC12
            Mapping registers: MSP430 - CRC16
            Mapping registers: MSP430 - DMA
            Mapping registers: MSP430 - Flash
            Mapping registers: MSP430 - MPY_16__Multiplier__16_Bit_Mode
            Mapping registers: MSP430 - MPY_32__Multiplier__32_Bit_Mode
            Mapping registers: MSP430 - Port_A
            Mapping registers: MSP430 - Port_1_2
            Mapping registers: MSP430 - Port_B
            Mapping registers: MSP430 - Port_3_4
            Mapping registers: MSP430 - Port_C
            Mapping registers: MSP430 - Port_5_6
            Mapping registers: MSP430 - Port_D
            Mapping registers: MSP430 - Port_7_8
            Mapping registers: MSP430 - Port_E
            Mapping registers: MSP430 - Port_9_10
            Mapping registers: MSP430 - Port_F
            Mapping registers: MSP430 - Port_11
            Mapping registers: MSP430 - Port_J
            Mapping registers: MSP430 - PMM__Power_Management_System
            Mapping registers: MSP430 - RC__RAM_Control_Module
            Mapping registers: MSP430 - Shared_Reference
            Mapping registers: MSP430 - RTC__Real_Time_Clock
            Mapping registers: MSP430 - SFR__Special_Function_Registers
            Mapping registers: MSP430 - SYS__System_Module
            Mapping registers: MSP430 - Timer0_A5
            Mapping registers: MSP430 - Timer1_A3
            Mapping registers: MSP430 - Timer0_B7
            Mapping registers: MSP430 - UCS__Unified_System_Clock
            Mapping registers: MSP430 - USCI_A0__UART_Mode
            Mapping registers: MSP430 - USCI_A0__SPI_Mode
            Mapping registers: MSP430 - USCI_B0__SPI_Mode
            Mapping registers: MSP430 - USCI_B0__I2C_Mode
            Mapping registers: MSP430 - USCI_A1__UART_Mode
            Mapping registers: MSP430 - USCI_A1__SPI_Mode
            Mapping registers: MSP430 - USCI_B1__SPI_Mode
            Mapping registers: MSP430 - USCI_B1__I2C_Mode
            Mapping registers: MSP430 - USCI_A2__UART_Mode
            Mapping registers: MSP430 - USCI_A2__SPI_Mode
            Mapping registers: MSP430 - USCI_B2__SPI_Mode
            Mapping registers: MSP430 - USCI_B2__I2C_Mode
            Mapping registers: MSP430 - USCI_A3__UART_Mode
            Mapping registers: MSP430 - USCI_A3__SPI_Mode
            Mapping registers: MSP430 - USCI_B3__SPI_Mode
            Mapping registers: MSP430 - USCI_B3__I2C_Mode
            Mapping registers: MSP430 - Watchdog_Timer
            Mapping registers: MSP430 - Hidden
            Building search data: MSP430
            Executing Startup Scripts: MSP430
    Connecting...
    error: MSP430: Error connecting to the target: Unknown device
    Failed: Operation was aborted
    
    C:\test>

    test.log

  • 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
  • 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

  • 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
    C:\test>dslite
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_files/set
    tings/generated.ufsettings -e -f -v -g test.log user_files/images/dev_test.out
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Parsing connections/TIMSP430-USB.xml
            Parsing drivers/msp430_emu.xml
            Parsing devices/MSP430F5438A.xml
            Parsing ../options/MSP430F5438A_TI.xml
            Parsing ../options/MSP430F5438A_GNU.xml
            Parsing ../cpus/MSP430Xv2.xml
            Parsing ../Modules/msp430/ADC12_2.xml
            Parsing ../Modules/msp430/CRC16_2.xml
            Parsing ../Modules/msp430/DMA_6.xml
            Parsing ../Modules/msp430/Flash_6.xml
            Parsing ../Modules/msp430/MPY_16__Multiplier__16_Bit_Mode_1.xml
            Parsing ../Modules/msp430/MPY_32__Multiplier__32_Bit_Mode_1.xml
            Parsing ../Modules/msp430/Port_A_1.xml
            Parsing ../Modules/msp430/Port_1_2_5.xml
            Parsing ../Modules/msp430/Port_B_1.xml
            Parsing ../Modules/msp430/Port_3_4_4.xml
            Parsing ../Modules/msp430/Port_C_1.xml
            Parsing ../Modules/msp430/Port_5_6_3.xml
            Parsing ../Modules/msp430/Port_D_1.xml
            Parsing ../Modules/msp430/Port_7_8_3.xml
            Parsing ../Modules/msp430/Port_E_1.xml
            Parsing ../Modules/msp430/Port_9_10_3.xml
            Parsing ../Modules/msp430/Port_F_1.xml
            Parsing ../Modules/msp430/Port_11_1.xml
            Parsing ../Modules/msp430/Port_J_1.xml
            Parsing ../Modules/msp430/PMM__Power_Management_System_2.xml
            Parsing ../Modules/msp430/RC__RAM_Control_Module_1.xml
            Parsing ../Modules/msp430/Shared_Reference_1.xml
            Parsing ../Modules/msp430/RTC__Real_Time_Clock_1.xml
            Parsing ../Modules/msp430/SFR__Special_Function_Registers_1.xml
            Parsing ../Modules/msp430/SYS__System_Module_2.xml
            Parsing ../Modules/msp430/Timer0_A5_1.xml
            Parsing ../Modules/msp430/Timer1_A3_1.xml
            Parsing ../Modules/msp430/Timer0_B7_1.xml
            Parsing ../Modules/msp430/UCS__Unified_System_Clock_1.xml
            Parsing ../Modules/msp430/USCI_A0__UART_Mode_2.xml
            Parsing ../Modules/msp430/USCI_A0__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B0__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B0__I2C_Mode_3.xml
            Parsing ../Modules/msp430/USCI_A1__UART_Mode_2.xml
            Parsing ../Modules/msp430/USCI_A1__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B1__SPI_Mode_2.xml
            Parsing ../Modules/msp430/USCI_B1__I2C_Mode_2.xml
            Parsing ../Modules/msp430/USCI_A2__UART_Mode_1.xml
            Parsing ../Modules/msp430/USCI_A2__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B2__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B2__I2C_Mode_1.xml
            Parsing ../Modules/msp430/USCI_A3__UART_Mode_1.xml
            Parsing ../Modules/msp430/USCI_A3__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B3__SPI_Mode_1.xml
            Parsing ../Modules/msp430/USCI_B3__I2C_Mode_1.xml
            Parsing ../Modules/msp430/Watchdog_Timer_2.xml
            Parsing ../Modules/msp430/MSP430Xv2_NotVisible.xml
            Initializing Register Database...
            Parsing C:\Users\mostrego\AppData\Local\TEXASI~1\CCS\C_drive\2\0\7352552
    24.cache
            Initializing: MSP430
    error: MSP430: Error initializing emulator: A firmware update is required for th
    e MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update"
    button to update the firmware and launch your debug session (this may require se
    veral update steps).  DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
    Updating Firmware
            Initializing Bootloader...
            Programming New Firmware...
            Programming New Firmware...: 16%
            Programming New Firmware...: 33%
            Programming New Firmware...: 50%
            Programming New Firmware...: 66%
            Programming New Firmware...: 83%
            Programming New Firmware...: 100%
            Initializing Bootloader...: 100%
            Programming New Firmware...: 100%
            Programming New Firmware...: 13%
            Programming New Firmware...: 16%
            Programming New Firmware...: 19%
            Programming New Firmware...: 22%
            Programming New Firmware...: 25%
            Programming New Firmware...: 28%
            Programming New Firmware...: 31%
            Programming New Firmware...: 34%
            Programming New Firmware...: 37%
            Programming New Firmware...: 40%
            Programming New Firmware...: 43%
            Programming New Firmware...: 55%
            Programming New Firmware...: 58%
            Programming New Firmware...: 61%
            Programming New Firmware...: 64%
            Programming New Firmware...: 67%
            Programming New Firmware...: 70%
            Programming New Firmware...: 73%
            Programming New Firmware...: 76%
            Programming New Firmware...: 79%
            Programming New Firmware...: 82%
            Programming New Firmware...: 85%
            Programming New Firmware...: 88%
            Programming New Firmware...: 91%
            Programming New Firmware...: 94%
            Programming New Firmware...: 97%
            Programming New Firmware...: 100%
            Finishing...: 100%
            Mapping registers: MSP430 - Core Registers
            Mapping registers: MSP430 - ADC12
            Mapping registers: MSP430 - CRC16
            Mapping registers: MSP430 - DMA
            Mapping registers: MSP430 - Flash
            Mapping registers: MSP430 - MPY_16__Multiplier__16_Bit_Mode
            Mapping registers: MSP430 - MPY_32__Multiplier__32_Bit_Mode
            Mapping registers: MSP430 - Port_A
            Mapping registers: MSP430 - Port_1_2
            Mapping registers: MSP430 - Port_B
            Mapping registers: MSP430 - Port_3_4
            Mapping registers: MSP430 - Port_C
            Mapping registers: MSP430 - Port_5_6
            Mapping registers: MSP430 - Port_D
            Mapping registers: MSP430 - Port_7_8
            Mapping registers: MSP430 - Port_E
            Mapping registers: MSP430 - Port_9_10
            Mapping registers: MSP430 - Port_F
            Mapping registers: MSP430 - Port_11
            Mapping registers: MSP430 - Port_J
            Mapping registers: MSP430 - PMM__Power_Management_System
            Mapping registers: MSP430 - RC__RAM_Control_Module
            Mapping registers: MSP430 - Shared_Reference
            Mapping registers: MSP430 - RTC__Real_Time_Clock
            Mapping registers: MSP430 - SFR__Special_Function_Registers
            Mapping registers: MSP430 - SYS__System_Module
            Mapping registers: MSP430 - Timer0_A5
            Mapping registers: MSP430 - Timer1_A3
            Mapping registers: MSP430 - Timer0_B7
            Mapping registers: MSP430 - UCS__Unified_System_Clock
            Mapping registers: MSP430 - USCI_A0__UART_Mode
            Mapping registers: MSP430 - USCI_A0__SPI_Mode
            Mapping registers: MSP430 - USCI_B0__SPI_Mode
            Mapping registers: MSP430 - USCI_B0__I2C_Mode
            Mapping registers: MSP430 - USCI_A1__UART_Mode
            Mapping registers: MSP430 - USCI_A1__SPI_Mode
            Mapping registers: MSP430 - USCI_B1__SPI_Mode
            Mapping registers: MSP430 - USCI_B1__I2C_Mode
            Mapping registers: MSP430 - USCI_A2__UART_Mode
            Mapping registers: MSP430 - USCI_A2__SPI_Mode
            Mapping registers: MSP430 - USCI_B2__SPI_Mode
            Mapping registers: MSP430 - USCI_B2__I2C_Mode
            Mapping registers: MSP430 - USCI_A3__UART_Mode
            Mapping registers: MSP430 - USCI_A3__SPI_Mode
            Mapping registers: MSP430 - USCI_B3__SPI_Mode
            Mapping registers: MSP430 - USCI_B3__I2C_Mode
            Mapping registers: MSP430 - Watchdog_Timer
            Mapping registers: MSP430 - Hidden
            Building search data: MSP430
            Executing Startup Scripts: MSP430
    Connecting...
    
    OpenDevice MSP430F5438A
    Loading Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
            .text: 0 of 1072 at 0xffd2: 11%
            Finished: 11%
            Setting PC to entry point.: 11%
    info: MSP430:  Flash/FRAM usage is 1234 bytes. RAM usage is 164 bytes.
    Verifying Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
            .text: 0 of 1072 at 0xffd2: 11%
            Finished: 11%
    info: MSP430: Program verification successful for user_files/images/dev_test.out
    
    Running...
    Success
    
    C:\test>
    

    Mike

  • 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
    C:\test>dslite
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_files/set
    tings/generated.ufsettings -e -f -v -g test.log user_files/images/dev_test.out
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Initializing Register Database...
            Initializing: MSP430
    error: MSP430: Error initializing emulator: A firmware update is required for th
    e MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update"
    button to update the firmware and launch your debug session (this may require se
    veral update steps).  DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
    Updating Firmware
            Initializing Bootloader...
            Programming New Firmware...
            Programming New Firmware...: 16%
            Programming New Firmware...: 33%
            Programming New Firmware...: 50%
            Programming New Firmware...: 66%
            Programming New Firmware...: 83%
            Programming New Firmware...: 100%
            Initializing Bootloader...: 100%
            Programming New Firmware...: 100%
            Programming New Firmware...: 13%
            Programming New Firmware...: 16%
            Programming New Firmware...: 19%
            Programming New Firmware...: 22%
            Programming New Firmware...: 25%
            Programming New Firmware...: 28%
            Programming New Firmware...: 31%
            Programming New Firmware...: 34%
            Programming New Firmware...: 37%
            Programming New Firmware...: 40%
            Programming New Firmware...: 43%
            Programming New Firmware...: 55%
            Programming New Firmware...: 58%
            Programming New Firmware...: 61%
            Programming New Firmware...: 64%
            Programming New Firmware...: 67%
            Programming New Firmware...: 70%
            Programming New Firmware...: 73%
            Programming New Firmware...: 76%
            Programming New Firmware...: 79%
            Programming New Firmware...: 82%
            Programming New Firmware...: 85%
            Programming New Firmware...: 88%
            Programming New Firmware...: 91%
            Programming New Firmware...: 94%
            Programming New Firmware...: 97%
            Programming New Firmware...: 100%
            Finishing...: 100%
            Executing Startup Scripts: MSP430
    Connecting...
    
    OpenDevice MSP430F5438A
    Loading Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
    error: MSP430: Trouble Writing Memory Block at 0x5c00 on Page 0 of Length 0xa2:
    Could not write device memory
    error: MSP430: File Loader: Verification failed: Target failed to write 0x05C00
            Finished
    Failed: File: user_files/images/dev_test.out: Load failed.
    
    C:\test>dslite
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_files/set
    tings/generated.ufsettings -e -f -v -g test.log user_files/images/dev_test.out
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Initializing Register Database...
            Initializing: MSP430
            Executing Startup Scripts: MSP430
    Connecting...
    
    OpenDevice MSP430F5438A
    Loading Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
            .text: 0 of 1072 at 0xffd2: 11%
            Finished: 11%
            Setting PC to entry point.: 11%
    info: MSP430:  Flash/FRAM usage is 1234 bytes. RAM usage is 164 bytes.
    Verifying Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
            .text: 0 of 1072 at 0xffd2: 11%
            Finished: 11%
    info: MSP430: Program verification successful for user_files/images/dev_test.out
    
    Running...
    Success
    
    C:\test>dslite
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_files/set
    tings/generated.ufsettings -e -f -v -g test.log user_files/images/dev_test.out
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Initializing Register Database...
            Initializing: MSP430
            Executing Startup Scripts: MSP430
    Connecting...
    
    OpenDevice MSP430F5438A
    Loading Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
    error: MSP430: Trouble Writing Memory Block at 0x5c00 on Page 0 of Length 0xa2:
    Could not write device memory
    error: MSP430: File Loader: Verification failed: Target failed to write 0x05C00
            Finished
    Failed: File: user_files/images/dev_test.out: Load failed.
    
    C:\test>dslite
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_files/set
    tings/generated.ufsettings -e -f -v -g test.log user_files/images/dev_test.out
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Initializing Register Database...
            Initializing: MSP430
            Executing Startup Scripts: MSP430
    Connecting...
    
    OpenDevice MSP430F5438A
    Loading Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
            .text: 0 of 1072 at 0xffd2: 11%
            Finished: 11%
            Setting PC to entry point.: 11%
    info: MSP430:  Flash/FRAM usage is 1234 bytes. RAM usage is 164 bytes.
    Verifying Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
            .text: 0 of 1072 at 0xffd2: 11%
            Finished: 11%
    info: MSP430: Program verification successful for user_files/images/dev_test.out
    
    Running...
    Success
    
    C:\test>dslite
    Executing default command:
    > dslite --mode flash -c user_files/configs/MSP430F5438A.ccxml -l user_files/set
    tings/generated.ufsettings -e -f -v -g test.log user_files/images/dev_test.out
    
    DSLite version 7.4.0.1095
    Configuring Debugger (may take a few minutes on first launch)...
            Initializing Register Database...
            Initializing: MSP430
            Executing Startup Scripts: MSP430
    Connecting...
    
    OpenDevice MSP430F5438A
    Loading Program: user_files/images/dev_test.out
            Preparing ...
            .text: 0 of 162 at 0x5c00
    error: MSP430: Trouble Writing Memory Block at 0x5c00 on Page 0 of Length 0xa2:
    Could not write device memory
    error: MSP430: File Loader: Verification failed: Target failed to write 0x05C00
            Finished
    Failed: File: user_files/images/dev_test.out: Load failed.
    
    C:\test>
    

    new_dll_test2.log

    Regards,

    Mike

  • Hello Mike,

    Outstanding! Thanks so much for sharing these details and log files. I will pass them along to our software team and keep you posted.

    Regards,

    James

    MSP Customer Applications
  • Hello Mike,

    Mike Ostrego said:

    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:

    (Please visit the site to view this file)

    (Please visit the site to view this file)

    To confirm, the MSP-FET's firmware was updated with the original DLL after using it with CCS, and it failed several times when used with the CLI. Using the test DLL, you didn't see any failures with the CLI. Is this correct?

    The second test log shows a success on the first attempt and a different error behavior (verification error instead of connection error). If and when possible, could you share the MSP-Flasher console output?

    Thanks again.

    Regards,

    James

    MSP Customer Applications

  • Hello James,

    When I re-ran the DSLite command line tool, the experimental DLL, MSP430.dll, reprogrammed the MSP-FET, with what I assume is the same MSP-FET firmware load, as the first experimental test. The reason why I did this is that I couldn't trust that the firmware install itself didn't nudge the MSP-FET into working. This second time I tested the experimental MSP430.dll, if you look at the new_dll_test2_command_prompt.log that I posted earlier, the write failed right after the installation of the new MSP-FET firmware. Yes, it is a different error when it fails to write than the original MSP-FET firmware.

    error: MSP430: Trouble Writing Memory Block at 0x5c00 on Page 0 of Length 0xa2:
    Could not write device memory
    error: MSP430: File Loader: Verification failed: Target failed to write 0x05C00
    Finished

    Again, if you look at the new_dll_test2_command_prompt.log file, it appears that it fails to write the executable to the MSP430 microcontroller every other time that dslite is run. I see this as progress. Failure at a 50% rate is better than failure at a 100% rate. The problem I have is that every time I run the MSP-FET in UniFlash or CCS, the old firmware is going to be re-fed to the MSP-FET.

    Mike
  • Also, I did share the console output from the MSP-Flasher/DSLite as new_dll_test2_command_prompt.log in my earlier post.
    Here is the link:
    e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/166/new_5F00_dll_5F00_test2_5F00_command_5F00_prompt.log
  • Hello Mike,

    Thanks for sharing these details. I've passed them along to our software teams.

    Regards,

    James

    MSP Customer Applications
  • Is there a method to run the Mass Erase?
    I am attempting to use the standalone tool for our COntract Manufacturer and it does not seem to do the mass erase therefore uniflash GUI must be used, this is unacceptable for production.

    Thanks for any feedback
  • Hello Joshua,

    Keep in mind that the mass erase erases Main, Info, and BSL memory. Is this what you need to do? I'm assuming that you want to erase the device before programming an image. Thus, the Standalone Command Line tool should work fine. Using the cloud-based UniFlash tool, you can configure the Download options (which can select which areas of memory to erase before programming) under "Settings & Utilities". Don't change anything under the Erase options unless you're erasing a specific address range.

    As an alternative, have you considered using MSP430-FLASHER? It's command line programmer that also allows you to erase the device. Here's the User's Guide for your reference.

    www.ti.com/.../slau654d.pdf

    Regards,

    James

    MSP Customer Applications

**Attention** This is a public forum