1974858_en-US

[#1]

S32G2 IPC communication

Dear members of NXP community,

I have just started working on NXP S32G2 IPC framework. I am following app note AN13750: "Enabling Multicore Application on S32G2
using S32G2 Platform Software Integration" and I had a few questions:

First off, if I understand the flow correctly from the document

1. Build Linux image with IPC and boot the A53 core using SD card.

2. Build the IPC image for M7 using design studio and use the bootloader to load the M7 into its SRAM. The bootloader is provided by the EB Tresos.

3. Start IP-communication from A53 with M7.

Under the assumption that above understanding is correct,

1. Can I directly run the M7 application from design studio with a debugger.

2. Let the linux image boot from SD card on A53.

3. Start IPC communication with M7 from A53 linux.

Is this possible? I do not want to deal with the EB bootloader as of now, unless, my understanding of the whole process is incorrect and this bootloader is crucial to the IPC functioning. Any comments/suggestions are welcome and appreciated.

P.S. : I want to only use 1 M7 core instead of the 3 cores used in the app note.


Best,

Vishnu  

Re: S32G2 IPC communication

@chenyin_h thanks for all your help. I'm going to close this thread and open a new one for RAM related questions.

Best,

Vishnu 

Re: S32G2 IPC communication

Thanks @chenyin_h . I now see that the RAM utilisation is around 4 GB. And the swap space allocated is 0. Is there a way to increase the swap memory? 

Best,

Vishnu 

Re: S32G2 IPC communication

Hello, @Vishnu3 

Thanks for your reply.

BSP images that the A53 used are mainly work with DDR, DDR is initialized and then used at very early stage before U-Boot is running.

BR

Chenyin

Re: S32G2 IPC communication

Hello @chenyin_h ,

Thank you for the response, I managed to get the IPCF example running from U-boot. The normal blink binary is also working however that puts the the kernel into panic when it is booting, I will look into that later.

So I have one last question, when the A53 image is executing, what is the RAM accessible to it? Does it only have access to the 8 MB SRAM or it has DRAM access as well? Please let me know.

Best,

Vishnu

Re: S32G2 IPC communication

Hello, @Vishnu3 

Sorry that I do not see other formal document related to original topic(running IPCF via U-Boot).

It is not recommended directly running the LED binary following the way that from the txt file you mentioned, the description.txt only provide method of using IPCF.bin directly from U-Boot, it is not targeted for other kinds of M core binaries.

BR

Chenyin

Re: S32G2 IPC communication

A quick question, I followed the desciption.txt file. But as a starter I did not load the IPCF project bin, instead I created a simple LED blink project and loaded it from Uboot but it is not working.

Following are the steps I used:

1. Created a NXP DS project that blinks a blue LED on the S32G2. Tested with debugger, generated the bin file.

NOTE: This bin was generated by the NXP and NOT from the IVT. I hope that is okay. Please confirm.

2. I placed this bin file in the boot section of the sd card which contains the A53 image.

3. Inserted the SD card and interrupted the auto boot so that I get access to the Uboot terminal.

4. Following commands were given as per "description.txt" modified as per the blinky project SRAM address


=> dcache off

=> fatload mmc 0:1 0x80000000 Siul2_Dio_Ip_Example_S32G274A_M7.bin

[this returned with reading the bin file]

=> cp.b 0x80000000 0x34000000 0x100000

=> startm7 0x34500400 [interrupt vector address as per map file of blinky project]

[this returns saying that M7 core 0 has started at the address 0x34500400]

RESULT: but the LED does not blink on the board

Best,

Vishnu

Re: S32G2 IPC communicationEdit: "Description.txt"Re: S32G2 IPC communication

@chenyin_h  is there no other document apart from "document.txt" that tells how to load M7 from Uboot. I mean like an application note. 

Best,

Vishnu

Re: S32G2 IPC communication

Hello, @Vishnu3 

Thanks for the reply.

Sure, if any other issues found, you may also create other new posts, we are happy to support.

B R

Chenyin

Re: S32G2 IPC communication

@chenyin_h  thank you for the reply, I am trying the sequence you mentioned, will update in a couple of days.

Best,

Vishnu

Re: S32G2 IPC communication

Hello, @Vishnu3 

Thanks for your post.

If you only want to try the IPCF, and do not want to deal with the bootloader, it is still possible:

1. You may firstly build the IPCF_Example_S32G274A_M7_0 from the IPCF packages, once finished, a M7_0 application would be prepared.

2. Then directly boot the board with BSP(A53), stopped to the console of U-Boot.

3. Under U-Boot, following the instructions that shown from description.txt which could also be found under the IPCF_Example_S32G274A_M7_0.

Then the IPCF communication example could run correctly between both A & M core.

Hope it will help.

BR

Chenyin