From: "Adivi, Sai Sree Kartheek" <s-adivi@ti.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: [cip-dev] help required to understand isar-cip-core for new platform addition
Date: Sun, 23 Mar 2025 03:36:25 +0000 [thread overview]
Message-ID: <86937cf5-aa90-4e40-a24d-ab2eae156a3c@email.android.com> (raw)
[-- 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 --]
next reply other threads:[~2025-03-23 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 3:36 Adivi, Sai Sree Kartheek [this message]
2025-03-25 9:02 ` [cip-dev] help required to understand isar-cip-core for new platform addition Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86937cf5-aa90-4e40-a24d-ab2eae156a3c@email.android.com \
--to=s-adivi@ti.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox