[cip-dev] help required to understand isar-cip-core for new platform addition

[cip-dev] help required to understand isar-cip-core for new platform addition

[Adivi, Sai Sree Kartheek]

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Hi All,

I'm trying to add support for TI AM62x SK in isar-cip-core.

As a starting point to see how the images are partitioned and structured, I've build a 6.1 Bookworm image for BeagleBone Black. I see that there is only one ext4 partition which holds the rootfs and there is no fat32 partition for the bootloader.
I've tried to boot it on BBB and it seems to be starting the U-boot from emmc and picking up Filesystem from SD card.

- Is this the expectation for all platforms?
- Doesn't the isar-cip-core image package u-boot? Or am I missing some config option while building?
- Also if the u-boot is not supposed to be packaged, why do we have a u-boot recipe in isar-cip-core?

I would appreciate any insights or guidance from the community. If there are relevant references, past discussions, or documentation regarding this, please let me know.

PS: I've also tried building an image with same configuration for hihope-rzg2m and seen similar observations (wic image doesn't have a bootloader).

Thanks & Regards,
Sai Sree Kartheek Adivi



[-- Attachment #2: Type: text/html, Size: 1665 bytes --]

Re: [cip-dev] help required to understand isar-cip-core for new platform addition

[Jan Kiszka]

On 23.03.25 04:36, Adivi, Sai Sree Kartheek wrote:
> Hi All,
> 
> I'm trying to add support for TI AM62x SK in isar-cip-core.
> 

You may want to study isar upstream for this, namely the BeaglePlay
support there:

https://github.com/ilbers/isar/blob/master/meta-isar/conf/machine/beagleplay.conf
https://github.com/ilbers/isar/blob/master/meta-isar/scripts/lib/wic/canned-wks/beagleplay.wks.in
...

> As a starting point to see how the images are partitioned and
> structured, I've build a 6.1 Bookworm image for BeagleBone Black. I see
> that there is only one ext4 partition which holds the rootfs and there
> is no fat32 partition for the bootloader. 

As discussed in the WG meeting, here is the partitioning:

https://gitlab.com/cip-project/cip-core/isar-cip-core/-/blob/master/wic/bbb.wks

> I've tried to boot it on BBB and it seems to be starting the U-boot from
> emmc and picking up Filesystem from SD card.
> 

Boot ordering issue, most likely. Wipe the eMMC or enforce booting from
SD card via the boot button.

Jan

> - Is this the expectation for all platforms?
> - Doesn't the isar-cip-core image package u-boot? Or am I missing some
> config option while building?
> - Also if the u-boot is not supposed to be packaged, why do we have a u-
> boot recipe in isar-cip-core?
> 
> I would appreciate any insights or guidance from the community. If there
> are relevant references, past discussions, or documentation regarding
> this, please let me know.
> 
> PS: I've also tried building an image with same configuration for
> hihope-rzg2m and seen similar observations (wic image doesn't have a
> bootloader).
> 
> Thanks & Regards,
> Sai Sree Kartheek Adivi
> 
> 

-- 
Siemens AG, Foundational Technologies
Linux Expert Center