• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 79 subscribers
  • Views 562 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.

MSP430FR2433: MSP430FR2433 EVM Kit

Anatya Vallabh
Prodigy 540 points
Part Number: MSP430FR2433

My customer has tested the MSP430FR2433 EVM kit alone and it is working fine. Now they are trying to validate the MSP430FR2433 I2C BSL mode with our gateway board and they have some queries on this point.

The EVM kit working IO voltage is 3.3V and the customer's  gateway board working IO voltage is 1.8V. So they want to make changes on the EVM kit to make it work with 1.8V, so that they can directly wire up the EVM kit with their gateway board to validate the I2C BSL mode.

 

Could you please tell me that Is it possible to make the EVM kit to work with 1.8V?

If so, please suggest the changes to be made on the EVM kit to make it work with 1.8V ASAP.

  • 0
    TI__Genius 13215 points

    Hi Anatya,

    The MSP430FR2433 can't allow 1.8V VCC power supply for working, which you could find the SVS specification on Table 5-2. PMM, SVS and BOR of the device datasheet.

    For you use case, I would like to give you below suggestions:

    1. Add 1.8v-to-3.3v Voltage-Level Shifter between the two parts IOs.

    2. Check whether the gateway board IO could allow the 2.0V high level signal. If yes, you could try to supply the MSP430FR2433 with 2.0V VCC and connect the two parts directly.

  • 0 in reply to SeaFesse
    TI__Prodigy 540 points

    thanks for the response -

    The IO connections can be done like this

    What about I2C lines? Will this level translator circuit work with I2C?

  • 0 in reply to Anatya Vallabh
    Expert 2690 points

    Anatya Vallabh said:
    What about I2C lines? Will this level translator circuit work with I2C?

    Hi Anatya,

    I'm 100% sure it works well on I2C.  Maybe just the value of the RES and which NPN mos you choice will make few differences., which depends on the transmission rate.

  • 0 in reply to Anatya Vallabh
    TI__Genius 13215 points

    Hi Anatya,

    Any further question?

  • 0 in reply to Wei.Jetim Zhao
    TI__Prodigy 540 points

    the customer is trying to use I2C bsl support from the msp platform FR2433 evaluation kit provided,

    the customer is  using “msp430-i2cbsl-tool”  to flash the MSP through BSL mode and they failed in unlocking the device ,

     Tried with “MSP430Flasher.exe -b/e “ (unlock protected bsl/erase all) but still no use

    This is blocking us going further , please help us in fixing ,

    Tried both HW and SW BSL invoke options

  • 0 in reply to Anatya Vallabh
    TI__Genius 13215 points

    Hi Anatya,

    Thanks for come back for further question from you customer.

    For the BSL mode unlock device issue, could you give me a more detailed description about how you customer did and what issue log or phenomenon was shown? So that I could understand your issue progress and help to check if any solution.

    BTW, I would suggest to go through the user's guides of both BSL and MSP430flasher to confirm your customer is doing all the process well.

    MSP430 FRAM Device Bootloader (BSL)

    MSP Flasher user's guide (Rev. E)

  • 0 in reply to Wei.Jetim Zhao
    TI__Prodigy 540 points

    Regarding BSL issue, the log is as below-

    LOG **************************

     

    pi@raspberrypi:~/msp430/msp430-i2cbsl-tool $ ./msp430-i2cbsl-tool -n -i /dev/i2c-0 -s 0x48 -f ../firmware.txt

     

    ---------------------------------------------------------------

       TI MSP430 I2C Linux BootLoader 01.00.00.00

    ---------------------------------------------------------------

    INFO: I2C BUS /dev/i2c-0 specified

    INFO: Slave address 0x48 specified

    INFO: Firmware file ../firmware.txt specified

    INFO: Opening TI-TXT firmware file firmware.txt...  done!

    INFO: Password file not found, defaulting to 0xFFs.

    INFO: Skipped software invoke.

    INFO: Attempting to unlocking device with password... Fail!

    INFO: Device could not be unlocked. Resetting password and trying again.

    INFO: Skipped software invoke.

    INFO: Attempting to unlocking device with password... Fail!

    INFO: Device could not be unlocked. Resetting password and trying again.

    INFO: Skipped software invoke.

    INFO: Attempting to unlocking device with password... Fail!

    INFO: Device could not be unlocked. Resetting password and trying again.

    INFO: Skipped software invoke.

    INFO: Attempting to unlocking device with password... Fail!

    INFO: Device could not be unlocked. Resetting password and trying again.

     

    ERROR: When trying to invoke or unlock device (Response code 0x104).

     clearly says “device could not be unlocked” and highlighted in log provided.

    How can tessolve unlock device ?  these devices come with a specific password ?  the tool using default password 0xFF is it ok ?  if not what is the password file to be used for this chipset ?

     

    The target is

     

    “to flash testapp.txt  (created from CCS) to the MSPFR2433 chip through I2C bsl using raspberry pi as host”

     Tessolve has  followed the doc SWRA500 -- MSP430™ Firmware Updates Over I2C Using Linux to achieve the same, but end up in below mentioned error

  • 0 in reply to Anatya Vallabh
    TI__Prodigy 540 points

    Hi Wei,

    any feedback on the above question and log , please do let me know.

    anatya

  • 0 in reply to Anatya Vallabh
    TI__Genius 13215 points

    Hi Anatya,

    Sorry for reply you late. I will check you log and reply you shortly.

  • 0 in reply to Anatya Vallabh
    TI__Genius 13215 points

    Hi Anatya,

    Comparing your logs to the logs in Figure4 of SWRA500, there may be some issue for Invoking BSL process, which being shown after the log"INFO: PAssword file not found, defaulting to 0xFFs". 

    As the documents says below, could you please take the SLAU550 to check if any issue for the BSL invoking.

    Another important design requirement of performing a BSL update is having a method to invoke the BSL mode on the MSP430 device. For MSP430, the following are ways to invoke the BSL: hardware invocation and software invocation. Hardware invocation requires the user to apply a specific timing pulse to the TEST and RESET pins. Software invocation requires the user to have a custom I 2C command handler that changes the program counter to enter BSL mode. For specifics on software and hardware BSL invocations, see the specific BSL design guide (see MSP430FR57xx, MSP430FR58xx, MSP430FR59xx, MSP430FR68xx, and MSP430FR69xx Bootloader (BSL) User's Guide [SLAU550]).

**Attention** This is a public forum