AM263P4-Q1: Flash mode selection

Hi Lakshya verma,

1.Can I flash the device directly in OSPI mode using JTAG...?
2.UART0 is connected to the RS-232 transceiver, can we use this UART0 interface to flash the AM263Px internal 8-MB SIP OSPI flash using UART Uniflash? I need to select UART Boot Mode during the flashing process, and is this configuration supported?

Hi Team,

We are working on a custom board based on AM263P4AFONZCZRQ1 and using MCU+ SDK 11.01.00.19.

Could you please clarify whether any migration/customization is required to use the existing SDK JTAG flashing flow on our custom board? If not, could you share the recommended procedure to:

• Flash the application to external NOR Flash via JTAG
• Generate the required SBL/application images
• Configure boot settings
• Boot the application from NOR Flash

Any reference documentation or application notes for custom board bring-up would be greatly appreciated.

Thank you for your support.

Best Regards,
Shilpa

2.UART0 is connected to the RS-232 transceiver, can we use this UART0 interface to flash the AM263Px internal 8-MB SIP OSPI flash using UART Uniflash? I need to select UART Boot Mode during the flashing process, and is this configuration supported?

        Part No: AM263P4AFONFZCZRQ1 custom board whether any migration required?

3.I'm using JTAG for flashing. Should I select JTAG Uniflash or TI UniFlash?  

4.i selected the Jtag Uniflash
The below option shown in the attached screenshot is not available in CCS after debugged. My device uses the SiP package ZCZ-F
    Could you please share the easiest way to store data in flash memory for the SiP package (ZCZ-F), along with reference code for a custom board?

1: Erase Complete Flash

I will get back to you on this

Could you please address my queries at the earliest possible convenience?

Hi Venkata,

2) Let me try UART Uniflash for SIP package and i will get back to you.

For this package (ZCZ-F), migration is required from SDK side. We provide script in SDK for migration to this package
AM263Px MCU+ SDK: Migrating examples from package to package in AM263PX

3)
You can use any.

4)
For easy way, you TI uniflash. It is very user friendly.

For reference CCStudio UniFlash Quick Start Guide

Did you migrate this example to ZCZ-F package?

AM263Px MCU+ SDK: SBL JTAG Uniflash

You just need to put dev boot mode and run a CCS debug session.

One correction from my side

Can I flash the device directly in OSPI mode using JTAG...?
yes you can 

2) Yes, you can, UART uniflash expects the board to be in UART boot mode. UART boot mode is supported.
Refer AM263px TRM Section 5.3

Hi Lakshya

For the UART boot mode, could you please share the reference example and the procedure for UART UniFlash?

Additionally, for custom board flashing you can refer to below FAQ.

(+) [FAQ] AM263P4-Q1: How to flash/program custom external flashes - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums  

...
...
...
[9/3/2026, 8:02:48 PM] [INFO] Cortex_R5_0: GEL Output: CPU reset (soft reset) has been issued through GEL on program load.
[9/3/2026, 8:03:08 PM] [ERROR] Cortex_R5_0: Run failed...
[9/3/2026, 8:03:08 PM] [ERROR] Cortex_R5_0: File Loader: Memory write failed: Timed out waiting for target to halt while executing am263px_cc_flasher.out

Can you give me more context, what were you running?

I followed the above link, while loading the image I have selected the .mcelf and .mcelf_xip images also I have 1 doubt here, what should be the SBL image in case of the custom flasher, and also, I know the boot mode from FLASH is OSPI, so the SBL image(sbl_ospi_multicore_elf.release.tiimage) should be migrated as per custom board?? if yes, then what is the procedure. 
Getting one more issue while flashing the code via JTAG at very 1st time only, 2nd time it is flashing successfully attached the images for your reference.
Please tell us the correct way to resolve these issues

Venkata Rami Reddy Vempati said:

I followed the above link, while loading the image I have selected the .mcelf and .mcelf_xip images also I have 1 doubt here, what should be the SBL image in case of the custom flasher, and also, I know the boot mode from FLASH is OSPI, so the SBL image(sbl_ospi_multicore_elf.release.tiimage) should be migrated as per custom board?? if yes, then what is the procedure. 

Yes, select the SBL OSPI multicore elf image.

Follow this document for migration to ZCZ-F package: https://software-dl.ti.com/mcu-plus-sdk/esd/AM263PX/latest/exports/docs/api_guide_am263px/SOC_MIGRATION.html#autotoc_md603

Venkata Rami Reddy Vempati said:

.mcelf_xip images

Are you planning to execute image from Flash? If yes, follow this: https://software-dl.ti.com/mcu-plus-sdk/esd/AM263PX/latest/exports/docs/api_guide_am263px/BOOTFLOW_XIP.html and load XIP file as well. Else no need to select the XIP file.

Venkata Rami Reddy Vempati said:

Getting one more issue while flashing the code via JTAG at very 1st time only, 2nd time it is flashing successfully attached the images for your reference.

Can you share your image binaries (jtag flashser, sbl ospi multicore elf) with us, we can try to give it a shot on our zcz-f based am263px-cc SIP board. 

Regards,
Shaunak

4774.hello_world_am263px-cc_r5fss0-0_nortos_ti-arm-clang.zip

I see flasher_jtag_uniflash.tiimage is attached instead of the .out in above zip

hello_world_am263px-cc_r5fss0-0_nortos_ti-arm-clang _04_09.zip

Hi Shaunak,

If you have any working example files for a custom board, such as SBL, MCELF, or XIP, could you please share them with me?

I’m still waiting for your response. Please provide it as soon as possible.