TMS320F280039C: not able to program flash

Hi Praveenlal,

Check the following pointers which might help,

1. Target configuration not set to cJTAG 2-pin advanced mode. The onboard XDS110 on the F28003x LaunchPad runs 2-pin cJTAG by default (TDI/TDO are reallocated to GPIO). A .ccxml left on standard 4-pin JTAG is a documented cause of scan-path errors (SC_ERR_PATH_BROKEN) that show up specifically during flash programming even when RAM debug connects fine.
Fix: open the .ccxml -> Advanced tab -> set "JTAG/SWD/cJTAG Mode" to cJTAG (1149.7) 2-pin advanced modes, Target Scan Format OSCAN2.


F28003x LaunchPad User's Guide: https://www.ti.com/lit/ug/spruj31/spruj31.pdf

FAQ, LAUNCHXL-F280049C and XDS110 (It has identical XDS110/cJTAG design): https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/759254/faq-ccs-launchxl-f280049c-issues-with-launchxl-f280049c-and-xds110

2. Boot switch S3 not in Flash-boot position. S3 must be HIGH, HIGH (GPIO24, GPIO32) for boot-from-flash. Doesn't block programming, but is the top reason programmed code "doesn't take" when power-cycle-tested.


 F28003x LaunchPad User's Guide:https://www.ti.com/lit/ug/spruj31/spruj31.pdf
TMS320F280039C TRM Section 4.5.3: https://www.ti.com/lit/ug/spruiw9b/spruiw9b.pdf

3. Stale/edited device XML or outdated CCS packages. The On-Chip Flash plugin (Debug view -> Tools -> On-Chip Flash) silently misbehaves if the target config wasn't built from the stock dropdown device, or if C2000 Device Support / Debug Server Flash packages are out of date (Help -> Check for Updates).

FAQ, C2000 CCS Flash plugin and UniFlash: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1096194/faq-c2000-ccs-flash-plugin-and-uniflash

4. CSM/device lock. "Device is locked or not connected. Operation cancelled." if flash carries a non-default CSM password (prior programming, OOB demo, inherited project) — needs the password in Debug -> Flash Settings.

RelatedTI E2E : https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/375675/c28xx-flash-programmer-device-is-locked-or-not-connected-operation-cancelled

5. Programming without erasing first. FMSTAT/STATCMD = 0x30 means you're trying to program a 1 over an already programmed 0, erase the sector(s)/chip rather than "Program Only."
TI E2E: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1372916/tms320f280039c-error-c28xx_cpu1-error-during-flash-programming-address-0x00078004-fmstat-statcmd-on-some-devices-0x00000030

6. Stale build after the linker-file swap. Switching _ram_lnk -> _flash_lnk without a full Clean + Rebuild can leave stale object sections still mapped to RAM.

7. Manual-connect workaround: set S3 correctly, open target config manually, Connect to CPU1 manually, browse-load the .out, then Resume instead of Debug.

Cannot Connect To Dev Board: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1233873/tms320f280039c-cannot-connect-to-dev-board

If the above pointers don't help then to narrow down upon the issue can you share the exact CCS view/Console error text when programming is attempted, whether the .ccxml Advanced tab shows cJTAG 2-pin or standard JTAG, current S3 switch position, and CCS12 exact build + C2000Ware/device-support package versions.

Regards 
Arpit