• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 77 subscribers
  • Views 1324 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.

MSP430F2101 BSL problem

Yves Conselvan
Prodigy 40 points
Other Parts Discussed in Thread: MSP430F2101

Hi everyone,

 

I'm trying to program one msp430f2101 via the bootstrap loader.

I'm using the deprecated code provided for 2xx devices.

I can send the synchronization character (0x80) and receive the response (0x90), but I can't do anything more.

 

when I send a "mass erase" command sequence:

80 18 04 04 00 FF 06 A5 7D B9

the device is always responding A0.

if I try to send "rx password" command sequence:

80 10 24 24 E0 FF 20 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 9B 34

considering the erased password, the device is always returning A0.

Is there another factory default password that I can try?

 

I have connected the supply pins, the data pins (P1.1 and P2.2), the XIN and XOUT pins to a 32Khz oscilator, and the TEST and RST to the bsl initialization sequence.

There is any other connection to do?

 

Any ideas?

 

Yves

 

 

  • 0
    TI__Expert 3315 points

    Hi,

       I just tried this sequence on the same device, my output is below (curly brackets are data from the BSL)

      There is some difference in our Password sequence, but the Mass Erase is identical, so that should ACK.  The only thing I can currently think of: Have you disabled the BSL in this device by writing to the word below the interrupt vector?  Is it failing on a single device, or every one you have tried?

     

    Mass Erase:    [80] {90} [80] [18] [04] [04] [00] [ff] [06] [a5] [7d] [b9] {90}
    Sending Password:   [80] {90} [80] [10] [24] [24] [00] [00] [00] [00] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [ff] [5b] [cb] {90}

  • 0 in reply to Lane Westlund
    Prodigy 40 points

    Hi Lane,

     

    thanks for help. I'm trying to build a prototype so I have manual soldered one device to a test circuit that I can connect in my pront-o-board.

     

    The device came from Texas to the university with 4 others as samples. They are supposed to be new,  so I think that could have damaged the CI in the soldering. I have never accessed the device memory, the first trying was the BSL.

    Use JTAG will be more complicated, because the device F2101IDWR don't have the 2 pin spy-by-wire, so I was first trying BSL.

     

    I will try to use the others samples without soldering.

     

    Yves

  • 0 in reply to Yves Conselvan
    TI__Expert 3315 points

    Hi,

       A couple other quick thoughts then:

     

    1) You do not need a 32KHz crystal to use the BSL (though having one should not cause problems)

    2) It probably isn't the BSL memory issue I described, and I would doubt it was due to soldering dammage, though first trying the device in the MSP430 Target Socket (what did here to get the above TX/RX) might be a good idea, to isolate your problem.

    3)  I'd guess it's due somehow to the bit timing or integrity, causing the Packet RX to fail, but I can't guess at any specific reasons as I am not familiar with your setup.

  • 0 in reply to Lane Westlund
    Prodigy 40 points

    Hi Lane,

     

    thanks for the tips, I will try to get a target socket to isolate the problem.

     

    Because I testing in a pront-o-board doing all connections whit wires I think your guess about the timing or integrity could be the cause.

     

    Thanks for all

     

    Yves

**Attention** This is a public forum