hi,Niranj_369
Thank you for contacting us.
1.We do not have the newer version of AN13750, you also can refer to the AN13750 for your S32G3 platform, the steps are similar。
2.You can refer to the demo of IPCF in RTD, and you can try to test how to load the IPCF sample from u-boot.
Hope this can help you.
BR
Joey
hi,Niranj_369
Thank you for your reply.
1. In step 7, how can i find the address of the address of the interrupt vector.
>>>You need to find it in .map file as the following picture.
2. After executing these commands, if i execute boot commands, will both the cores are active?
>>>Yes，you can boot M core in uboot.
3. Is there any simple example for m7 that i can try to check if it works(ie M7 fIrmware boot)?. Currently im using the IPCF M7 firmware. but im facing some issues while enabling IPCF in A53 core.
>>>You can try to add the operation of LED/register/Uart in M7 project and check the M7 status.
4. For enabling IPCF in A53 core, is the ipc-shm drivers only enough or i need dtb changes or other changes
ipc-shm-dev.ko, ipc-shm-uio.ko. ipc-shm-multiinstance.ko - do i need to insmod all these drivers?
Im getting the below error while insmoding ipc-shm-multiinstance.ko
>>> You can refer to the file of description file to add .ko files. The .dtb/Image files need to compatible with IPCF.
Hope this can help you.
BR
Joey
hi,Niranj_369
You can configure the S32DS IDE to create the .bin file.
1. Properties->Settings->Cross Settings->Check the Create flash image -> Apply and Close
2.General->Check the Raw binary, then rebuild the project, you can find the .bin file in folder of Debug_RAM.
Hope this can help you.
BR
Joey
hi，Niranj_369
Thank you for your reply.
1.Are these loading steps valid for any M7 firmware, or only for IPCF examples?
>>>Other M7 Image also can be loaded through these steps. But you need to solve the conflict between A and M core, including clock and pin etc.
Also, do you can test the M7 Image only on M7 core? is the LED will blink?
2.Can I reduce the size of the .bin file, or is there another recommended approach to fit it within the M7_0 SRAM range? or is there any other way to overcome this?
>>> You can modify the link file for this as the following picture.
Hope this can help you.
BR
Joey
I'm using a sequence of U-Boot commands to load the M7 firmware on the S32G3 platform. All commands execute successfully, but the expected functionality—LED blinking—is not working.
dcache off
mw.q 0x34100000 0x0 0x40000
fatload mmc 0:4 0x80000000 led.bin
cp.b 0x80000000 0x34350010 0x300000
startm7 0x34451000
QN 1:where can i find the correct load address used in the memory copy command. Specifically, I need clarity on the address and size parameters, what each represents, and where to obtain them. My goal is to boot the M7_0 core of the S32G3 device. Attached the firmware files for reference.
QN 2:I’d like to know whether it's possible to load an ELF file directly from U-Boot. If so, I need the exact commands and guidance on how to determine the correct memory address to use.
Qn 3: I attempted to load the ELF file using the bootelf command, but it resulted in an exception error. I want to understand why this happens and what causes the failure.
=> bootelf 0x80000000
"Error" handler, esr 0xbf000002
elr: 00000000ff91fbc8 lr : 00000000ff91fbc4 (reloc)
elr: 00000000ff91fbc8 lr : 00000000ff91fbc4
QN4: readelf -h led.elf that the class is ELF32. is it expected. is the the reason for the bootelf failure?
QN5: When I load the LED blinking ELF file using Lauterbach, it works correctly. However, when I try to load the corresponding binary instead, it fails with an unknown symbol error. I need to know what address should be used when loading the .bin file in the Lauterbach CMM script.
QN6: I have used the linker script modification provided to reduce the size of the bin file. will it affect the functionality of the bin file?
Thanks @Joey_z
I have built the 4.10.0 M7 IPCF application and attempted to boot both cores by halting at the A53's U-Boot, loading the M7 firmware into SRAM, starting it, and then proceeding to boot the A53 core. However, when the M7 firmware is loaded prior to booting the A53, the boot process halts midway. The attached image compares the A53 boot logs: the left side shows the log with M7 firmware loaded, where the boot fails, and the right side shows the successful boot when the M7 firmware is not loaded.
Note: This only happens with IPCF example. I have successfully done parallel booting with led and lin m7 firmware examples.
To isolate the issue, I commented out all logic in the M7 firmware's main function, yet the A53 still fails to boot completely. Could you please help explain the root cause of this behavior and suggest how to resolve it?
Additionally, I attempted to insert the IPC shared memory drivers (ipc-shm-dev.ko and ipc-shm-sample_multi-instance.ko) while the M7 firmware was not loaded. Inserting ipc-shm-sample_multi-instance.ko resulted in an error. Is this failure due to the absence of the M7 firmware? If not, could you please clarify the cause and advise on how to fix it?
Note : Im using bsp43.0 with kernel version 6.6. IPCF upfdatesite version 4.10.0 and ipc-shm version 4.10.0.
Thanks @Joey_z
The issue was due to the linker configuration. Initially, I used a linker script that split the SRAM across three cores. Later, I switched to the IPCF example configuration, which allocates the entire SRAM to a single M7 core. With that change, I'm now able to boot the A53 core after loading the M7 firmware — enabling parallel boot.
After that, I tried loading the IPCF drivers on the A53 side by following the steps from the S32DS M7 IPCF example documentation.
The ipc-shm-dev.ko module loads successfully, though it logs the expected warning:
[ 42.983443] ipc_shm_dev: loading out-of-tree module taints kernel.
However, when I try to load ipc-shm-sample.ko, it fails with a synchronous external abort.
For reference, I built the drivers from the SW32G_IPCF_4.10.0_D2405 branch against our current kernel version (6.6), and the M7 core is running IPCF firmware version 4.10.0.
Could you please help me identify what might be causing the crash or suggest a fix?
