Re: support for multi instance zephyr in same soc
Yes, the whole “board” concept needs an overhaul to become instead “instances” or “targets” as you say.
In the nRF5340, which is a dual-core asymmetric Cortex-M33, we used “cpuapp” and “cpunet” to distinguish between the application core and the network core:
From: devel@... <devel@...> On Behalf Of Scott Branden via Lists.Zephyrproject.Org
Sent: 04 February 2020 02:23
To: Kumar Gala <kumar.gala@...>
Subject: Re: [Zephyr-devel] support for multi instance zephyr in same soc
Thanks Kumar - we will go with this convention for naming the target. ie board_cpu.
It will work out as long as there are not multiple cpu's on the same board that need different zephyr builds.
At that point you would need board_cpu_n
Really "boards" directory should be renamed "targets"?
On Sun, Feb 2, 2020 at 9:01 AM Kumar Gala <kumar.gala@...> wrote: