rpmsg-imx93

[UNTESTED] — v0.6 paper-correct, blocked on iMX93 memory map

The iMX93 SoM preset's memory_map: values are TBD pending an authoritative HW writeup. west alp-build no longer aborts on TBD metadata — instead the orchestrator records a status: blocked carve-out in system-manifest.yaml, and the generated <alp/system_ipc.h> carries an #error directive so the consumer compile fails with a clear message. Structural files in this example are correct in shape today.

Heterogeneous-compute demo for E1M-NX9101 (NXP i.MX 93). Same pattern as rpmsg-v2n but for the i.MX 9-family heterogeneous SoC:

• a55_cluster — Yocto consumer under linux/.
• m33 — Zephyr producer under m33/. The iMX93's M33 carries no system-manager role, so the core ID is just m33 (not m33_sm).

Source: examples/rpmsg-imx93/.

board.yaml

schema_version: 2

som:
  sku: E1M-NX9101
  hw_rev: r1

carrier:
  name: E1M-EVK              # 35x35 EVK — same carrier as the AEN family

cores:
  a55_cluster:
    os: yocto
    app: ./linux
    image: alp-image-edge
    libraries: [mbedtls, nlohmann_json]
  m33:
    os: zephyr
    app: ./m33
    peripherals: [adc, pwm, i2c, gpio]
    libraries: [cmsis_dsp]

ipc:
  - kind: rpmsg
    endpoints: [a55_cluster, m33]
    carve_out_kb: 512
    name: alp_default_rpmsg

The iMX93's M33 has no cache, so the default non-cacheable region wins — same policy as V2N.

See also

• Heterogeneous builds walkthrough
• <alp/rpc.h>
• rpmsg-v2n — canonical V2N counterpart