Other Parts Discussed in Thread: MSP-FET,
We are wanting to confirm if the following info from the SLAU320AG can resolve the locked debugging issue for MSP430FR2110 (we want to erase the lock and the firmware) using in MSP-FET programmer:
* -----/|-------------------------------------------------------------------- * * / |__ * * /_ / MSP Flasher v1.3.20 * * | / * * -----|/-------------------------------------------------------------------- * * * Evaluating triggers... * Invalid argument for -e trigger. Default used (ERASE_ALL). * Checking for available FET debuggers: * Found USB FET @ COM11 <- Selected * Initializing interface @ COM11...done * Checking firmware compatibility: * FET firmware is up to date. * Reading FW version...done * Setting VCC to 3000 mV...done * Accessing device... # Exit: 16 # ERROR: The Debug Interface to the device has been secured * Powering down...done * Disconnecting from device...done
If so, we are using the above code to connect with the device with a host running the TEST and REST pins for JMB connection.
Does the code flow follow the above guide? (Based on the code example given by SimpleLink Host for MSP430 JTAG Mailbox SLAA763)
int unlockDevice (void)
{
// restart device
ClrTST();
ClrRST();
ConnectJTAG();
// Apply again 4wire/SBW entry Sequence
EntrySequences_RstLow_SBW(); //Restart JTAG – Keep RST low device do not start
ResetTAP(); // reset TAP state machine -> Run-Test/Idle
// shift in JTAG mailbox exchange request
IR_Shift(IR_JMB_EXCHANGE);
DR_Shift16(0xA55A);
DR_Shift16(0x1A1A);
StopJtag();
// wait until LPM4
MsDelay(100);
// connect to device again, apply entry sequence
ConnectJTAG();
// Apply again 4wire/SBW entry Sequence.
EntrySequences_RstHigh_SBW();
// reset TAP state machine -> Run-Test/Idle
ResetTAP();
if(SyncJtag_AssertPor() != SC_ERR_NONE)
{
return(SC_ERR_GENERIC);
}
}
Although we can get the device ID the above does not seem to erase/unlock the JTAG, if(SyncJtag_AssertPor() != SC_ERR_NONE) always returns an error waiting for sync.
