Jump to content
43oh

Does BSL-scripter work with eZ-FET 1.2?


Recommended Posts

I'm trying to use BSL-scripter to erase the FRAM on my custom board since it locked the Spy-By-Wire interface after uploading an incorrect firmware.

 

So I connected the launchpad to the pc using USB, determined the application COM port (5) and hooked up the custom board to SBWTCK, SBWTDIO, RX and TX pins on the FET-side of the launchpad. Spying on the 4 pins is a logic analyser.

 

The following script is used for BSL-scripter:

 


// COM number is "MSP Application UART1", lookup in Device Manager
MODE FRxx UART COM5

VERBOSE

// Get BSL version (e.g. Vendor:[xxxx],CI:[xxxx],API:[xxxx],PI:[xxxx],BuildID:[xxxx])
TX_BSL_VERSION

// Mass erase, some devices don't support this.
MASS_ERASE

 

According to SLAU610B there should be a toggle on TEST/RST to start the FR2433 in BSL mode (see figure 2), but BSL-scripter returns error 0x19 on TX_BSL_VERSION and error 0x15 on MASS_ERASE. The logic analyser sees no activity on any of the pins, except -strangely- the two error codes on the RXD pin of the FET.

 

Can the eZ-FET rev 1.2 on an MSP-EXP430FR6989 launchpad be used with BSL-scripter to erase the memory of an MSP403FR2433?

Link to post
Share on other sites

AFAIK, only G2 LP can be used as BSL hardware base.

 

http://www.ti.com/lit/pdf/slaa535    Launchpad-Based MSP430 UART BSL Interface

 

FR2xx and FR4xx devices can be unlocked by USER CODE ERASE (1A1A) command using mailbox system by SBW / JTAG.This can be done by MSP-Flasher (check erase options), and I guess by any LP with eZ-FET Lite on board..

 

Link to post
Share on other sites

I'm pretty sure that, in one of the many slau's I've read over the last days, there were hints about the eZ-FET 1.2 Emulation also being suitable to do BSL....

 

But never mind. Thanks a million Jazz! Your comment triggered me to try mspflasher again. I tried that route before only using the ERASE_ALL option instead of the ERASE_USER_CODE.

 

Using the eZ-FET Lite on the G2 launchpad this resulted in an error code:

 


c:\ti\MSPFlasher_1.3.10>MSP430Flasher.exe -e ERASE_USER_CODE
* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.10                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ HID0040:COM6 <- Selected
* Initializing interface @ HID0040:COM6...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Performing user code erase...
# Exit: 3
# ERROR: Invalid parameter(s)
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/

Looks like the eZ-FET Lite does not support the ERASE_USER_CODE option. Trying the ERASE_ALL option resulted in "Could not find device (or device not supported)".

 

So I hooked up the FR6989 launchpad and tried MSPflash again using ERASE_USER_CODE: Success! CCS is now able to program the chip again. :D

 

 

c:\ti\MSPFlasher_1.3.10>MSP430Flasher.exe -e ERASE_USER_CODE
* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.10                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM4 <- Selected
* Initializing interface @ COM4...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Performing user code erase...done
* Accessing device...done
* Reading device information...done
*
* ----------------------------------------------------------------------------
* Arguments   : -e ERASE_USER_CODE
* ----------------------------------------------------------------------------
* Driver      : loaded
* Dll Version : 30801000
* FwVersion   : 30800002
* Interface   : TIUSB
* HwVersion   : E 4.0
* JTAG Mode   : AUTO
* Device      : MSP430FR2433
* EEM         : Level 5, ClockCntrl 2
* Erase Mode  : ERASE_USER_CODE
* VCC OFF
* ----------------------------------------------------------------------------
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/

Just a shame that I was so close to the answer 4 days ago. This took a lot of time and frustration...

Link to post
Share on other sites
Using the eZ-FET Lite on the G2 launchpad this resulted in an error code:

 

Looks like the eZ-FET Lite does not support the ERASE_USER_CODE option. Trying the ERASE_ALL option resulted in "Could not find device (or device not supported)".

 

G2 LP does not have (updatable) eZ-FET Lite on board. And does not support new FR devices

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...