Hardware / Special jobs: radar and motors / Step 4 of 4
LP-AM263P (AM263P)
The AM263P is a microcontroller in TI's AM26x family: 400 MHz Arm Cortex-R5F, 32 MB of flash, 3 MB of RAM.
Quick facts
| Board | LP-AM263P |
|---|---|
| Chip | AM263P |
| Core | 4x Cortex-R5F |
| Clock | 400 MHz |
| Flash | 32 MB |
| RAM | 3 MB |
| Radio | None |
| Notable peripherals | 32 PWM modules; 5 12-bit ADCs; 8 CAN-FD; 2 Gigabit Ethernet ports on the board; PRU-ICSS |
| On-board debug probe | Built into the board |
| Where to buy | TI.com |
| Toolchains that ran | TI compilers, FreeRTOS |
Get it running
First blink: 1 min 18 s from plug-in to a changed blink (terminal).
- Tools: MCU+ SDK 26.01.00.08, CCStudio 21.0.1, TI Arm Clang 5.1.1.LTS, SysConfig 1.28.0. The SDK pins older versions (CCStudio 20.5.0, SysConfig 1.27.0, TI Arm Clang 4.0.4.LTS); the newer ones built every example tried
- Build TI's blink: In
examples/drivers/i2c/i2c_led_blink/am263px-lp/r5fss0-0_nortos/ti-arm-clangrunmake i2c_led_blink.release.out DEVICE=am263px PROFILE=release TOOLS_PATH=$HOME/ti CCS_PATH=/Applications/ti/ccs2101/ccs CGT_TI_ARM_CLANG_PATH=/Applications/ti/ti-cgt-armllvm_release SYSCFG_PATH=/Applications/ti/sysconfig_1.28.0 - Open the console first: A reader on
...1must be running before the load; the examples print once, milliseconds after start - Load:
DSLite load -c am263p/AM263Px_ZCZ_C_<serial>.ccxml -t 120 i2c_led_blink.release.outinto RAM; 4.4 to 7.6 s per 0.9 MB image, first load 78 s - Check: The reader prints
I2C LED Blink Test Started ...; the LEDs go on, then off one at a time, ten times, about 16 s
Every step, with the setup: the board's README.
What works
- CoreMark: 5,854.01 (TI compiler, -O3, on-chip RAM; 400 MHz; 3 runs)
- Interrupt latency, pend to first handler line: 144 cycles (bare metal; 400 MHz; 3 runs)
- GPIO toggle: 10.02 cycles (TI Arm Clang, -O3, on-chip RAM; 400 MHz; 3 runs)
- Control loop, trigger to new PWM value: 1.1943 µs (TI Arm Clang, -Os; 400 MHz; 3 runs)
- RTOS task switch round trip: 5.128 µs (FreeRTOS; 400 MHz)
- Memory bandwidth, STREAM-style triad: 327.2 MB/s (TI Arm Clang; 400 MHz; 3 runs)
- Vendor examples that build from a terminal: 249 of 284 (TI Arm Clang; 400 MHz)
- Dhrystone 2.1: 1.9408 DMIPS/MHz (-O3; 400 MHz)
Download every result for this board (CSV), or compare it on this board on the Benchmarks page.
Fixes
- If you see Empty console after
DSLite load, open...1before the load. - If you see DSLite error -615, plug in the USB-C supply; delete the property.
- If you see
ModuleNotFoundError: No module named 'construct', ignore it for a RAM load. - If you see
DSLite loadtimes out at 90 s, run it again. - If you see
Error: Could not fetch next record for SQL statement (database disk image is malformed), remove the one slot no process holds. - If you see
Does not match the target endianness, not loadedon the third core, load that core once with the GEL connection file. - If you see Console shows the previous program after a load, debugger System Reset.
- If you see
Flash_norOspiPhyTune : PHY enabling failed!!! Continuing without PHY.., flash still works at 16.7 MHz; back up the sector at0x80000first.
For AI assistants
Point your assistant at this board's AGENTS.md (build, flash and fix notes) and the repository's llms.txt (the index).
Sources: am263p/README.md, am263p/AGENTS.md, am263p/FAQ.md, data/results/am263p.csv, site/data/portfolio.json.