• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 960 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/MSP430FR2633: Problem with update FW via I2C

Peter Tsao
Prodigy 140 points
Part Number: MSP430FR2633


Tool/software: Linux

Hi all

I am new in FR2633.

I am trying to update FW via I2C (guide: swra500.pdf MSP430™ Firmware Updates Over I2C Using Linux)

My host is Raspberry 3 Model B and connect with FR2633 by SDA, SCL, 3.3V, GND (is there wire miss?)

The I2C address is 0x0a (not 0x48?)

After entering the command "./msp430-i2cbsl-tool -i /dev/i2c-1 -s 0x0a -f firmware.txt"

The log is shown as bellow:

---------------------------------------------------------------
TI MSP430 I2C Linux BootLoader 01.00.00.00
---------------------------------------------------------------
INFO: I2C BUS /dev/i2c-1 specified
INFO: Slave address 0xa specified
INFO: Firmware file ../../../msp4302.txt specified
INFO: Opening TI-TXT firmware file firmware.txt... done!
INFO: Password file not found, defaulting to 0xFFs.
INFO: Invoking BSL (Attempt 1)... Invoke sent!
INFO: Delaying for 2 seconds to wait for invoke... done!
INFO: Attempting to unlocking device with password... Fail!
INFO: Device could not be unlocked. Resetting password and trying again.
INFO: Invoking BSL (Attempt 2)... Invoke sent!
INFO: Delaying for 2 seconds to wait for invoke... done!
INFO: Attempting to unlocking device with password... Fail!
INFO: Device could not be unlocked. Resetting password and trying again.
INFO: Invoking BSL (Attempt 3)... Invoke sent!
INFO: Delaying for 2 seconds to wait for invoke... done!
INFO: Attempting to unlocking device with password... Fail!
INFO: Device could not be unlocked. Resetting password and trying again.
INFO: Invoking BSL (Attempt 4)... Invoke sent!
INFO: Delaying for 2 seconds to wait for invoke... done!
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).

The error code is I2C Transaction error

Could you know how to solve this problem?

Thanks,

Best Regards

Peter

  • 0
    TI__Genius 9570 points
    Hi Peter,

    Thanks for your posting, we will look into this and get back to you ASAP.

    Regards,
    Ling
  • 0 in reply to Ling Zhu2
    Prodigy 140 points

    Hi Ling

    Thanks for your reply

    Here are my  Raspberry Pi & FR2633 circuit and jumper

    They are only connect by four wires (SCL, SDA, 3.3V, GND)

    And I am only test for the firmware upgrade approach (msp430-i2cbsl-tool)

    Thanks,

    Best Regards

    Peter

  • 0 in reply to Peter Tsao
    TI__Genius 9570 points
    Hi Peter,

    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]). For hardware
    invocation, the timing pulse must be applied on the TEST and RESET pins before calling the terminal
    application. If the hardware invocation is used, specify the –n option to omit the software invocation. If the
    –n flag is not specified before any BSL command is issued, the terminal program sends an I2C write
    transaction of the bytes specified in the invokeString array of the main.c file. By default, this invoke string
    is represented by a character sequence of {0xCA, 0xFE, 0xDE, 0xAD, 0xBE, 0xEF, 0xBA, 0xBE}.

    Ling
  • 0 in reply to Peter Tsao
    TI__Genius 9570 points
    Hi Peter

    Have you solved your issue?

    Ling
  • 0 in reply to Ling Zhu2
    Prodigy 140 points

    Yes

    I used software invocation to enter BSL.

    Now, I can see address 0x48 with i2cdetect

    Thx

**Attention** This is a public forum