How does it influence the A-Core and M-Core job with the option "m7boot" ?

[fengxianeric]

From the technical chapter within S32G3_LinuxBSP_35.0_User_Manual doc, I got below guidance information,

DISTRO_FEATURES_append += "m7boot"

this document instruct how to build linux fsl packages, but why it refered this information, how does it influence boot M7 core correctly (or building how many files related to M7 core) to run A53 kernel and driver modules smoothingly? 

[Bio_TICFSL]

Hello,

Please take a look at:

https://community.nxp.com/t5/S32G/how-to-boot-AP53-and-M7-core/m-p/1461110

Regards

[fengxianeric]

root@s32g399ardb3:~/release0511/poll# ./ipc-shm-sample.elf

Input number of messages to send: 5
ipc-shm-us-app: ch 0 >> 19 bytes: SENDING MESSAGES: 5
ipc-shm-us-app: send_data_msg(): failed to get buffer for channel ID 1 and size 32
ipc-shm-us-app: exit

[fengxianeric]

[ 6.565206] 8021q: adding VLAN 0 to HW filter on device eth0
[ 9.642413] s32cc-dwmac 4033c000.ethernet: Set TX clock to 125M
[ 9.642449] s32cc-dwmac 4033c000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 9.642481] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 24.022589] ipc_shm_dev: loading out-of-tree module taints kernel.
[ 85.245931] ipc-shm-sample: starting demo...
[ 85.245948] ipc-shm-sample: ch 0 >> 20 bytes: SENDING MESSAGES: 10
[ 85.245958] ipc-shm-sample: send_data_msg(): failed to get buffer for channel ID 1 and size 32
root@s32g399ardb3:~/release0511#

[fengxianeric]

Yes, thanks, I can understand what it means by mannually invoke m7 work, but about production environment I can't input command by uboot. On the other side my question is about the option which I need to build on linux dev environment. what can it produce after enabled the m7boot option ?