On a multi(dual) core device, if load/verify actions are done first on the second CPU after UniFlash startup, then load/verify actions for the first CPU have no effect. It appears that actions are not even run as there is no console output indicating such. Actions on CPU2 will continue to work.

If load/verify actions are done first on the first CPU, then it will work on both first CPU and second CPU.

The issue was reproduced on an F28377D and F28379D. Any dual core program can be used.

The issue has been reproduced on UniFlash 6.3.0 and UniFlash 5.3.1