Part Number:MSP430F5342
I'm trying to unprotect some previously protected MSP430's and I've run into something strange.
I erased the BSL segments (A,B,C,D at 0x1000 to 0x17ff) and re-programmed. I've used three separate images and none work. Those images are:
BSL.00.06.04.04 From the custom BSL package version 1.00.12.00
BSL.00.07.05.04 From the custom BSL package version 1.00.12.00
Additionally, I've read out the BSL from another (working) board and it is identical byte for byte with 6.04.04. I have verified that the signatures (primary and secondary) are correct, and that the BSL is actually programmed into the device. Just to re-iterate, the "bad" board worked fine until I nuked the BSL and re-programmed it.
When I look at the reset, TCK, RX and TX lines I see correct behavior (Reference SLAU319, section 1.3.2) Comparing a working device vs the non-working device I see everything the same, except that the non-working device never sends anything from it's Tx line.
Trying to debug the boot rom and the BSL is very challenging. The code protection features and some IDE/debugger features seem designed to thwart this at every turn.
I have observed that the boot rom must be calling the BSL_Protect function of the BSL because the SYSBSLPE bit of the SYSBSLC register is set, as are both size bits, which is what the BSL that's loaded into the part is supposed to do.
Is there some configuration item that could have gotten erased when the BSL was nuked that affects BSL operation? I've read everything I can find on the boot, BSL, BSL-Scripter, etc and cannot find anything that's wrong.
