1. If I use MSP430-JTAG-ISO-MK2's standalone mode to program MSP430FR5969 on its launchpad dev board, everything works (I can program both data and code memory).2. If I switch to MSP430-JTAG-ISO-MK2's debugger mode, and use Olimex MSP430 Programmer software to program, I am able to program the data memory, but not the code memory (verify failed after write).

Between setup 1 and 2, no hardware/cable connection is changed/touched.

And in setup 2, I was able to read, erase and verify both memory properly. For write, I was able to write data memory properly, just not the code memory.

After checking with a colleague I can confirm now that at one point of the time this was working... I was able to program the code memory through MK2's debugger mode using Olimex MSP430 Programmer software... Erase first, then write, then verify successfully.

He was having the same problem earlier in a different project but didn't have the time to look into it. In this project I got it working at a point, and shew it to him, he double checked the process and confirmed it was working. Now my setup went bad too for some reason.

To rule out that the case that my launchpad board or the controller went bad, I replaced it with a different development board, which we can use TI's ccs to program and debug successfully. It failed again on this new board. So I am pretty sure the problem is in my setup, not the launchpad board or the controller on this board.

The fact that I can program the controller in standalone mode, that means the connections and firmware from MK2 to the controller should be fine.

I swapped the USB cable between my laptop and the MK2 programmer, it didn't make a difference. The firmware in MK2 should be the same... the most likely variable in this setup seems to be Olimex MSP430 Programmer software on my laptop.

I will try to uninstall the software and the driver and install it back to see if it makes a difference.

Reinstalling Olimex MSP430 Programmer doesn't seem to make a difference. But in the installation process I noticed in terms and condition agreement it mentioned that the software was done before those >64K controllers such as MSP430FR5969 were released. So it does not guarantee to support those new devices.

At the same time it mentioned a newer version of command line tool is released with support for >64K controllers and many bug fixes. Is mspprog-cli-v2.exe the tool it refers to?

And is it a lost cause trying to get this working or do you have any suggestions?

Just to update that we have gone back to use TI's JTAG programmer and it worked like a charm... We picked this programmer initially because we had success using it on a different project in which TI's programmer didn't work. But in this case TI's JTAG programmer won.