From: <daniel.sangorrin@toshiba.co.jp>
To: <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Cc: <isar-users@googlegroups.com>
Subject: [isar-cip-core] porting isar-cip-core to iwg20m
Date: Tue, 4 Jun 2019 06:15:40 +0000 [thread overview]
Message-ID: <TY2PR01MB332320DC786A54F33FF95C9FD0150@TY2PR01MB3323.jpnprd01.prod.outlook.com> (raw)
Hi Jan,
I am trying to port isar-cip-core to the iwg20m board.
So far I managed to create a WIC SDCard image with 2 partitions:
- boot: an VFAT partition to store the uImage and devicetree
- root: the root filesystem
[Note] u-boot.bin is installed on an SPI memory with a JTAG debugger, so it's not in the image.
I would appreciate your help with a couple of problems:
- The kernel is built correctly, but I need to transform it into an uImage. I guess I can install u-boot-tools and do a mkimage in some postinstall script, but isn't this supposed to be automatized?
For example, in meta-debian, I just need to define KERNEL_IMAGETYPE=uImage and the UBOOT_ENTRYPOINT. The rest is done for me.
- In case, I want to build u-boot (not strictly necessary but it would be good to have it), do I have to create a whole recipe including debian rules like in the jailhouse-images repository [1]!?
In meta-debian, I just need to define a few variables (git repo, config, entrypoint) and the u-boot packages will be created automatically. Those scripts may be needed for very detailed customization (e.g. Trusted firmware), but the common case should be automatized.
[1] https://github.com/siemens/jailhouse-images/tree/master/recipes-bsp/u-boot
- What is the correct way to specify the device tree for the kernel?
I added DTB_FILE="mydt.dtb" to my machine config, and then added that to IMAGE_BOOT_FILES. That worked, but is that the correct way to do it? There is no documentation about this.
- For the kernel configuration, I want to use shmobile_defconfig (already in the kernel source) plus a few extra configurations that I have on another file. Is that possible? So far I had to concatenate my configurations to shmobile_defconfig which is redundant.
- How can I install the kernel into the boot partition?
Currently, the kernel binary and symbols are deployed into the the /boot folder of the "root" partition instead of the "boot" partition. I would like the /boot folder to be deployed into the FAT partition. And maybe also get fstab filled automatically.
I send the actual code/metadata separately on another e-mail.
https://lists.cip-project.org/pipermail/cip-dev/2019-June/002409.html
Thanks,
Daniel
next reply other threads:[~2019-06-04 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 6:15 daniel.sangorrin [this message]
2019-06-04 6:28 ` Jan Kiszka
2019-06-04 6:37 ` daniel.sangorrin
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=TY2PR01MB332320DC786A54F33FF95C9FD0150@TY2PR01MB3323.jpnprd01.prod.outlook.com \
--to=daniel.sangorrin@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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