This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Trying to program the flash using UNIFLASH and debug emulator then have CPU1 run the code.
Under Program>C28xx_CPU1 I have checked "Run Actions > Run Target After Program Load/Flash Operation"
No Reset Action is set.
I select and "Load Image" successfully, but the target does not run.
Is this feature supposed to start the CPU1 target after programming?
If not, any suggestions on how to start CPU1 target using UNIFLASH?
Thanks.
Other observations where target runs:
1. Disconnected Debug Emulator USB from Computer powers down isolated FTDI chip, then when it is plugged in again FTDI chip is powered and target starts to run.
2. Cycling power to entire board will start the target as well.
================ Details ===========================
UNIFILASH version: 6.3.0.3193
Board based on MCU063A Design using TMS320F28388D running @ 200MHz with 20MHz XTAL
Switch positions:
S1:A Position 1 = ON, JTAG Enabled
S1:A Position 2 = OFF, ISO UART disabled
S2 = Mode 3, GPIO-84/72 = 1/1 = Flash/USB Boot Mode
J1:A USB Emulation connected to Computer using XDS100v2 USB Debug Probe
Hi Huey Duong,
In Uniflash, keep the core connected (click on the core name at the top right corner and enable "Remain Connected after operations") and then do the load operation. Please try if that helps to fix this issue and let me know.
Thanks and regards,
Vamsi
Thank you for the quick response, I have tried your suggestion but the result is the same. Code is not running on CPU1 after programming. Although the status on the tool says C28xx_CPU1 Running Free
Hi Huey Duong,
Thank you for trying that.
I will discuss with our team and get back to you.
Regards,
Vamsi
Hello Huey,
I tried this functionality out with my UniFlash 6.3.0 installation. I believe I can reproduce the issue with my F28388D controlCard. I doesn't seem to occur with my F28069 so it seems specific to certain devices. We are investigating and I will keep you posted of any updates
Thanks
ki