Hi Kawin,
Apologies for the late response. When attempting to replicate the issue on our side, we did not see any kernel panics. Outlined below are the steps that we took using the basic LED example from the software enablement guide. As a next step, I would ask you to try to replicate the following steps as well with your M7 binary to see if the kernel panic still occurs. This will give a starting point with a procedure that has been tested to work. In the meantime, if this procedure deviates from the steps you took, please let us know by including the u-boot commands used for loading the M7 binary, u-boot environment variables set, and any relevant changes made to the Linux BSP 30.0 image during the build process.
- Flash pre-build Linux BSP 30.0 fsl-image-auto image from Flexera
- Setup the TFTP server on a PC running Linux (in our case, Ubuntu 18.04 LTS was used). For this, we used the "Setting up a TFTP server" instructions from this arm community article.
- Note that the binary from the LED example project will be stored in the tftpboot folder on the PC versus their test file
- Obtain the IP address of the PC running linux through the following command. This will be referred to as <tftp_server_ip_addr> in the following steps.
$ ifconfig -a
- Connect PFE2 ethernet port of the S32G2 board to your local network. In the case of the RDB2/GoldBox, this is port P3B.
- Boot the board, enter the u-boot console and enter the following commands:
=> initsram 0x34100000 0x700000
=> dhcp
=> tftp 0x34300000 <tftp_server_ip_addr>:led_example_M7_0.bin
=> startm7 0x34501000- Note that the dhcp command will attempt to load image files such as 'C0A0158.img' once it successfully connects and obtains an IP address. You can either cancel the command at that point using Ctrl+C or wait for the load to fail.
