Other Parts Discussed in Thread: MSP430FR6047
I like to communicate with the BSL of a MSP430FR5043 following document slau550ab.pdf.
I connect 9600 bps and when I send e.g. a wrong header or a wrong checksum, I will receive error code 0x51 resp. 0x52 according to Table 4-6 of the document. This should proof that the hardware connection works and I indeed talk to the BSL of the chip. I switch to the BSL using the software command ((void (*))0x1000)() but did not do any other modifications on the boot setup from the app side.
Now I want to unlock the BSL using the byte sequence given in the doc (pp16). This worked well generating the expected response packet when doing the very same process with a MSP430FR6047. However, with the FR5043 the very same commands results in rebooting the original app code in FRAM.
Table 2-1 of slau550ab states that FR5xx devices with FRAM does not do an erase of FRAM and does not do any password protection while 5.1.5.2 of the same document says that on MSP430FR5*** the FRAM code is erased if incorrect password is sent.
