Access to R5F core

Module: Aquila AM69 on Aquila Dev Board OS: Torizon OS 7.6.0+build.36 (scarthgap)

Goal: build and load a bare-metal “hello world” R5F firmware on MAIN_R5F1_0 via Linux remoteproc, with UART output visible on the dev board’s UART4 debug port.

Observations:

  1. Torizon IDE Extension (3.4.2) has no R5F project template for Aquila AM69.

  2. /lib/firmware/ contains only app_remoteswitchcfg_server for R5F0_0 (CPSW9G helper); no example firmware for R5F1, R5F2.

  3. /lib/firmware/ is on read-only OSTree mount; firmware_class.path → /var/firmware works as a runtime workaround but doesn’t survive reboot.

  4. The K3 R5F driver rejects firmware ELFs whose only PT_LOAD segments target DDR (bad phdr da 0xa1100000); a working reference firmware (the CPSW one) has segments at ATCM (0x0), BTCM (0x41010000), and DDR — implying the bare-metal pattern requires reset vectors in TCM, not DDR.

Request: prebuilt example firmware (.xer5f) for one of the available MAIN R5F cores, OR documented build procedure for producing one from the PDK against Aquila’s device tree.

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


I can see you’re working with the Aquila AM69 module for R5F core development. Based on the available documentation, I need to clarify that the sources I have access to focus primarily on NXP i.MX platforms for heterogeneous multicore processing, not TI AM69 platforms (1)(2).

Current Documentation Coverage

The available Toradex documentation covers RemoteProc usage specifically for NXP i.MX platforms (1). The RemoteProc framework documentation explains how to load *.elf binaries and manage remote cores, but the specific examples and procedures are tailored for i.MX8 series modules (1).

For device tree overlays, the documentation shows that TI AM62 platforms have some support, but AM69 is not specifically covered in the available overlay examples (3).

Key Observations from Your Setup

Your observations about the K3 R5F driver requirements are technically sound - the driver expecting reset vectors in TCM rather than DDR aligns with typical bare-metal R5F firmware patterns. The firmware path issue you’ve identified (/lib/firmware/ being read-only on OSTree) is also a known characteristic of Torizon OS (3).

Recommendation

Since the available documentation doesn’t cover TI AM69 R5F development specifically, and you’re working with a newer platform (Aquila AM69) that may not have comprehensive documentation coverage yet, I’d recommend:

  1. Check the TDX-Info tool to verify your exact platform configuration
  2. Look for TI-specific SDK documentation for AM69 R5F development, as the build procedures may differ significantly from the NXP-focused examples in the current Toradex documentation

The lack of R5F project templates in the Torizon IDE Extension for AM69 suggests this platform may still be in early support phases for HMP development.

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

Unfortunately, according to TI its not possible since the R5Fs on the AM69 SOC are closed for TI-provided software only

Do you have timeline to release the SoM with TDA4VH chips, in that case?

Our target release is the end of Q2, subject to TI supplying the TDA4 SoCs according to their current schedule.

Hi Himanshu,

Just want to reiterate that we have Aquila TDA4 modules. We are in Q2 and the team has made the first samples that we can ship out to customers.

Best,

Michael Park
Toradex

Ok great, Just to re-confirm, R5F cores on AM69 SoM are not accessible because TI has closed it out, right? I am asking Main and MCU domain R5F cores both.

If we want to order Aquila TDA4 SoM, how can we order?

Regards,

Himanshu

I’d say TI does not support it on AM69.

For TDA4, please check this thread. Please note that using the R5F core(s) is not specific to Toradex module implementation but rather an SoC property. Therefore, please use TI support channels for related inquiries.

Our team has produced the first samples with TDA4, which we can now ship to customers. You can order it online; or email shop.us@toradex.com to place an order.

Hello,

We Aquila AM69 SoMs today that are attached to Aquila Carrier board and Clover board respectively. If we order TDA4 SoMs, would there be incompatibility, or features that may not work if we plug and play SoM modules?

I do not see specific price online for TDA4 modules, could you confirm one?

The price depends on the module configuration, especially the RAM and flash size. Please send your request for a quote to shop.us@toradex.com.

Hi @hdevi ,

There should be high compatibility between the TDA4 and the AM69. Difference really is the R5 core support which is on TDA4 but not on AM69.

Best,

Ok, thanks for confirming.