MSP430FR5969-SP: Issue invoking BSL through software using serial port terminal

This issue is being handled offline. 

Hi Jace, 

Thank you for looking into this issue, I have an update on it. The write up is below. Have you guys been able to make any head way with either recreating this issue or being able to come up with any solution?

I don't think I mentioned this in my last write up but we were able to program it twice via the bootloader when we invoked it with software. Once with the Mass Erase command and then the correct password, and then once with the bad password then correct password. Ever since then when either the mass erase command is sent or a good password the chip resets itself. 

--Begin Update--

Update: Instead of passing a bad password using the RX Password command first I sent the correct password for the BSL for our application. The correct password is found by reading the hex values from the interrupt vector table, memory locations 0xffe0 - 0xffff. Below is a screen capture of our interrupt vector table. 

As before I invoke the BSL via the software. Then I send the RX Password command via RealTerm. 

0x80 0x21 0x00 0x11  0x4f 0x1e 0x4f 0x1e 0x4c 0xb2 0x4f 0x1e 0x4f 0x1e 0x4f 0x1e 0x4e 0x3e

0x4f 0x1e 0x4d 0x58 0x4f 0x1e 0x4f 0x1e 0x4f 0x1e 0x4f 0x1e 0x4f 0x1e 0x4f 0x1e 0x4e 0xfe 0x88 0x11

 When I pas these values through with the correct checksum the chip resets itself. When I pass the incorrect checksum values through I receive a 0x52 which is expected since the checksum is incorrect. Below is the Oscope capture of the system reset. When the chip gets reset/powered on it automatically spits our some engineering data for us to let us know that its ready, (the purple line getting toggled towards the right of the capture.

When sending a correct RX Password or a Mass Erase command the chip resets itself.

Not sure where to go from here. If you can offer any insight it would be greatly appreciated. Thank you for your time and help.

Stefan