CODECOMPOSER: J-Link (Segger) + AM263P4_ZCZ_F: CCS/UniFlash Flash Failures and Device Detection Issues

Junsin Park

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: AM263P4, UNIFLASH

I am attempting to flash an image using the Segger J-Link debugger on a custom board based on the AM263P4_ZCZ_F MCU.
However, flashing has failed in both Code Composer Studio (CCS) and TI UniFlash.
I have a few questions regarding this setup.

< Development Environment >
Board: AM263P4_ZCZ_F (with on-chip 8MB flash) – custom board
TI CCS Version: 20.5.0.28__1.11.0
TI UniFlash Version: 9.5.0.5651
Debugger: Segger J-Link ULTRA+ V4.00 (J-Link/J-Flash SW V9.32)

< Questions >

Is it possible to flash using the “CCS → Run → Flash Project” menu when using a Segger J-Link debugger?
Debugging works normally, but flashing via “Flash Project” does not work.
Is it possible to flash using J-Link in TI UniFlash?
TI UniFlash also fails to flash.
Due to company security policy, I cannot attach the log file; instead, I am attaching a screenshot.
If there are any reference resources or user guides available for the AM263P4_ZCZ_F + Segger J-Link environment, I would appreciate it if you could share them.
When debugging in CCS or attempting to flash in UniFlash, the J-Link debugger does not detect the device, so I always have to manually select it (AM263P4_R5_0).

Is it possible to resolve this issue through CCS or UniFlash settings? Or should I contact Segger for support?
- When debugging in CCS: a popup appears stating that it cannot find “AM263PX.”
- When flashing in UniFlash: a popup appears stating that it cannot find “AM263PX_ZCZ_F.”

3 months ago

0 Nilabh Anand 3 months ago

TI__Guru 60060 points

Hi Junsin,

Which boot mode is configured on your custom board?

0 Ted Huh 3 months ago in reply to Nilabh Anand

TI__Expert 3505 points

Hello Nilabh,

Customers wants to add reply in this thread but they don't have a permission to reply. I attached the logs instead of them4237.ds.log

Fullscreen 1184.uniflash_gui_debug_log.txt Download

14:44:09:791 log - NWAgentAPI: dinfraConfigue resolved successfully.
14:44:09:943 error - {}
14:44:09:954 error - {}
14:44:09:963 error - {}
14:44:09:965 error - {}
14:44:09:986 error - {}
14:44:09:988 error - {}
14:44:10:020 error - {}
14:44:10:021 error - {}
14:44:10:031 error - {}
14:44:10:042 error - {}
14:44:10:047 error - {}
14:44:10:052 error - {}
14:44:10:054 error - {}
14:44:10:722 error - {}
14:44:10:726 error - {}
14:44:10:757 error - {}
14:44:10:957 error - {}
14:44:11:971 error - {}
14:44:11:986 error - {}
14:44:11:995 error - {}
14:44:12:150 error - {}
14:44:12:158 error - {}
14:44:12:168 error - {}
14:44:14:950 error - {}
14:44:14:956 error - {}
14:44:16:480 error - {}
14:44:16:509 error - {}
14:44:16:823 error - {}
14:44:16:837 error - {}
14:44:16:838 error - {}
14:44:17:201 error - {}
14:44:17:204 error - {}
14:44:17:396 error - {}
14:44:17:400 error - {}
14:44:17:401 error - {}
14:44:17:529 error - {}
14:44:17:530 error - {}
14:44:17:530 error - {}
14:44:17:976 error - {}
14:44:17:978 error - {}
14:44:17:978 error - {}
14:44:18:365 error - {}
14:44:18:366 error - {}
14:44:18:366 error - {}
14:44:19:875 error - {}
14:44:19:877 error - {}
14:44:19:877 error - {}
14:44:22:077 error - {}
14:44:25:784 debug - Target Configuration. Device: AM263Px_ZCZ_F, Connection: segger_j-link_connection, LP: false
14:44:25:943 debug - ufDS, session.configured, partnum of current session = am263px_zcz_f
14:44:25:971 debug - addTargetStateListener on Cortex_R5_0
14:44:26:006 error - {}
14:44:30:334 debug - session service: save()
14:45:35:914 debug - returning new configure
14:46:28:629 debug - configured
14:46:54:652 debug - connect to core Cortex_R5_0
14:48:36:311 debug - session service: save()
14:49:02:449 error - {}
14:49:02:452 error - {}
14:49:02:452 error - {}
14:49:26:447 debug - returning cached configure
14:49:49:093 debug - returning cached configure
14:50:01:499 debug - connect to core Cortex_R5_0
14:50:05:474 error - {}
14:50:05:476 error - {}
14:50:05:476 error - {}

In their custom board, it has same jumpers as LP, so they tested both DevBoot mode and OSPI mode but both does not working well.

Regards,

Ted

0 Nilabh Anand 3 months ago in reply to Ted Huh

TI__Guru 60060 points

Hi Ted,

can you share, how they are connecting the Jlink interface to JTAG pins on their custom board.

0 Ted Huh 3 months ago in reply to Nilabh Anand

TI__Expert 3505 points

Hello Nilabh,

I think the connection is right, because it works well for the CCS debug mode. RAM loading works well but it seems like when they try to loading it to the flash it fails. I will try to connect their target board with XDS110 first. but if Segger J-link is not supporting flash download, it is not good situation because customer already have J-link a lot.

Physical connection is TCK, TDI, TDO, TMS and bothe JTAG and cJTAG 4pin did not work.

Regards,

Ted