• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 1147 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.

BSL for MSP430G2553 - Problem TX data block

Paul Fey
Prodigy 110 points
Other Parts Discussed in Thread: MSP430G2553, MSP-FET

Hello!

I try to get my BSL interface working.

What work:

- ACK for the Sync

- ACK for mass erase

- ACK RX pasword

But if I try to get acces to the flash with:

"0x80, 0x14, 0x04, 0x04, 0x00, 0xC0, 0x10, 0x00, 0x6B, 0x2F"

first I get 0x90 and immediatley after that 0xA0.

Is my data frame correct or did I miss something?

Best regards,

Paul

  • 0
    TI__Guru 68116 points
    Hi Paul,

    I double-checked your command and the data frame and checksum looks correct to me. You sent the correct BSL password before trying to do TX_DATA_BLOCK right?

    What are you using to communicate with the BSL - what is your host? If you are using the PC, are you using something like the BSLDEMO2.exe included with the www.ti.com/.../slau319 download? If so, what hardware are you using to connect to the MSP430G2553? And what do you use with BSLDEMO2.exe - do you modify or use the .bat file?

    Alternately, are you maybe simply using a terminal program to communicate with the device BSL and entering sequences there?

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Prodigy 110 points
    Hi Katie,

    thanks for reply. I use an other MSP as programmer. For reading the version is not password protected (slau319j page 17). So just sending the entry sequence and the data frame for reading the bsl versin should be fine.

    Howerver, if I cant get anything out, may be I get something in.
    So here my sequence:
    - bsl entry sequence
    - mass erase - 0x80, 0x18, 0x04, 0x04, 0x00, 0x00, 0x06, 0xA5
    - new bsl entry sequence
    - fresh password - 0x80, 0x10, 0x24, 0x24, 0x00, 0x00, 0x00, 0x00,0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF
    - put something in - 0x80, 0x12, 0x08, 0x08, 0xC0, 0xC0, 0x04, 0x00, 0x55, 0xAA, 0x55, 0xAA

    The result is, mass erase and sending password was successful. Both times I got 0x90.
    But with transmit sequence I got 0x90 and immediatley 0xA0. And if I look into the memory with the ccs everything ist 0xFF, so the mass erase was successful.

    Best regards,

    Paul
  • 0 in reply to Paul Fey
    Guru 58965 points
    I am just guessing.

    When you try to put something in, do it slowly. That is, do not send "0x80, 0x12, 0x08, 0x08, 0xC0, 0xC0, 0x04, 0x00, 0x55, 0xAA, 0x55, 0xAA" one byte after another. Put a short delay (try about 1 msec to begin with).
  • 0 in reply to Paul Fey
    TI__Guru 68116 points
    Hi Paul,

    As a test, you may want to try using BSLDEMO2.exe from www.ti.com/.../slau319 with the MSP-FET, or with the hardware setup from a second launchpad as a bridge as shown in www.ti.com/.../SLAA535, to send the commands from the PC to the target MSP BSL. That should work, and then you can also look at the sequences and also at the signals on a scope, and compare to what you are seeing when you are using your host to try to find what could be causing your issue. I hope this helps show a potential debug path for you.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    TI__Guru 68116 points
    Hi Paul,

    Were you able to figure out your issue?

    -Katie
  • 0 in reply to Katie Pier
    TI__Guru 68116 points
    I will close the thread due to inactivity, but simply post back if you still need help.
    -Katie

**Attention** This is a public forum