AM263P4-Q1: AM263P4-SIP Package Custom board Flash

Hi,

Jayakeerthana P said:

And also please let us know whether AM263P4 can support external flash memory?

Yes AM263P4 support external flash memory only. There i no internal flash variant for this device. Even the SIP package is not a true internal flash, SIP variant uses stacked flash connected internally within the package, rather than flash memory embedded directly on the main microcontroller silicon die.

Jayakeerthana P said:

We are facing some issue in flashing custom board using AM263P4-Q1 SIP package

Can you please let me know what issues you face and what flashing procedure is being followed

Jayakeerthana P said:

Is there any guide or referene available for flashing the Custom board.We tried to migrate from SDK,but some errors has occured

Can you please share the errors. Ideally you should be able to connect to the UniFlash tool and detect the device. Is it working? What boot-mode do you use?

Regards,
Shaunak

We are migrating the SDK code.While loadig in Unifalsh it is showing multiple files load error.In CCS we are able detect the device ID 
[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

Hi,

1. Can you please confirm if the flasher jtag uniflash is adapted to custom board pinmux? And the migration script is run: software-dl.ti.com/.../SOC_MIGRATION.html

2. Also i see the SBL image is not used in the second image and just app and XIP image is used. You will need both, the custom flasher as seen in your 3rd image as well as an SBL OSPI binary which i see is missing in first 2 images.

Regards,
Shaunak

Hi,
For custom board,any example files available for SBL and tiiimage.In migration we are facing some issue.

Hi Jayakeethana,

All SDK examples are available only for EVM compliant hardware. The migration document can help you with migration process.

Can you please share what exact issue you run into? If errors, pls share error logs.

Regards,
Shaunak

We are seeing below error,

[9/4/2026, 1:10:09 PM] [INFO] CortexR50: GEL Output: Enabling XTALTEMPSENSE32K Clocks [9/4/2026, 1:10:09 PM] [INFO] CortexR50: GEL Output: TEMPSENSE Clock Enabled (32KHz) [9/4/2026, 1:10:09 PM] [INFO] CortexR50: GEL Output: Enabling XTALMMC32K Clocks [9/4/2026, 1:10:09 PM] [INFO] CortexR50: GEL Output: XTALMMC Clock Enabled (32KHz) [9/4/2026, 1:10:09 PM] [INFO] CortexR50: GEL Output: All IP Clocks are Enabled [9/4/2026, 1:10:09 PM] [INFO] CortexR50: AM263PxZCZF [9/4/2026, 1:10:09 PM] [INFO] CortexR50: Board Selected : EVM [9/4/2026, 1:10:09 PM] [INFO] CortexR50: Part Selected : SIP (On-Chip Flash) [9/4/2026, 1:10:09 PM] [INFO] CortexR50: GEL Output: CPU reset (soft reset) has been issued through GEL on program load. [9/4/2026, 1:10:10 PM] [INFO] CortexR50: Writing 1 chunk at offset 0x0 [9/4/2026, 1:10:31 PM] [ERROR] CortexR50: Run failed… [9/4/2026, 1:10:31 PM] [ERROR] CortexR50: Trouble Removing Breakpoint with the Action "Remain Halted" at 0x7000e368: (Error -1066 @ 0x7000E368) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 20.3.0.3656) [9/4/2026, 1:10:31 PM] [ERROR] CortexR50: File Loader: Memory write failed: Timed out waiting for target to halt while executing flasherjtaguniflasham263px-ccr5fss0-0nortosti-arm-clang.out [9/4/2026, 1:10:31 PM] [INFO] CortexR5_0: Writing 1 chunk at offset 0x0

Can you please confirm if you are able to run all steps documented here: https://software-dl.ti.com/mcu-plus-sdk/esd/AM263PX/latest/exports/docs/api_guide_am263px/SOC_MIGRATION.html#autotoc_md603

I see above error logs are from UniFlash tool. This is different from the Migration script.

Step-1: Run migration script (document linked above)

Step-2: Then rebuild the SBL OSPI and flasher jtag uniflash binaries (if your custom board pinmux is different, pls ensure you set the correct pinmux in sysconfig, if using TI EVM, this re-configuring step can be skipped, just re-build)

Step-3: Point to the newly built flasher jtag binary, SBL OSPI binary, application binary.
If you are not executing code from Flash and just using it to store image and run it from RAM, there is no need to select "XIP" image. 

If you want to run image from external flash, pls follow this document to enable XIP and only then select the "XIP" image in uniflash when flashing.

Regards,
Shaunak

So,Flash in package is present in MCU on die(Consider as external) that means no physical  external flash.
You are also considering the same corret

And also why we are seeing continously timeout error

Hi Jayakeerthana,

Would you please confirm if the steps in my previous response are followed and what is the outcome of those. I would not be able to help further if i do not understand the issue clearly, the outcome of following the steps on your end.

Regards,
Shaunak

Hi Jayakeerthana,

We have multiple duplicate threads mentioning same issue from CYIENT account. Requesting to follow the steps shared in this thread:  AM263P4-Q1: AM263P4-Q1: AM263P4- Flash or Booting through JTAG 

Regards,
Shaunak

Hi Shaunak,
   We have tried all the possible way. In ccs we are able to complete all the steps. But while in uniflash we are facing multiple load files error or timeout error

In Uniflash,we are trying it through jtag