From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v5 0/8] WIC update
Date: Tue, 13 Oct 2020 22:56:38 -0700 (PDT) [thread overview]
Message-ID: <d0e712de-95e4-4813-affd-160528a92746n@googlegroups.com> (raw)
In-Reply-To: <cd4b3324-d952-0f71-47b6-ab83070ad34f@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 4296 bytes --]
On Wednesday, October 14, 2020 at 12:00:30 AM UTC+5:30 Jan Kiszka wrote:
> On 13.10.20 20:22, Jan Kiszka wrote:
> > On 07.10.20 12:49, vijaikumar....@gmail.com wrote:
> >>
> >>
> >> On Tuesday, October 6, 2020 at 2:43:04 PM UTC+5:30 i...@radix50.net
> wrote:
> >>
> >> On Mon, Oct 05, 2020 at 09:55:40PM -0700, vijaikumar....@gmail.com
> >> wrote:
> >> > > http://ci.isar-build.org:8080/job/isar_vkk_devel/85/
> >> >
> >> > CI build succeeded.
> >>
> >> Thanks Vijai Kumar. I don't have objections to this one. I assume
> >> Henning's
> >> comments have been addressed in 07/08. We'll test on hikey and let
> >> you know.
> >>
> >>
> >> Yes. It is addressed. Sure let me know how it goes on Hikey.
> >>
> >
> > My integration experiment revealed some issue, but I do not understand
> > yet, where: If you build [1], which is the combination of your series
> > with [2], I get
> >
> > | DEBUG: Executing shell function do_wic_image
> > | INFO: Creating image(s)...
> > |
> > | ERROR: _exec_cmd: tune2fs -L fsbl1
> /tmp/tmp.z4IScQtkyS/isar-image-base-debian-buster-stm32mp15x.wic/tmp.wic.9q0k2f75/tf-a-stm32mp157c-ev1.stm32.1
> returned '1' instead of 0
> > | output: /usr/sbin/tune2fs: Bad magic number in super-block while
> trying to open
> /tmp/tmp.z4IScQtkyS/isar-image-base-debian-buster-stm32mp15x.wic/tmp.wic.9q0k2f75/tf-a-stm32mp157c-ev1.stm32.1
>
> > | tune2fs 1.44.5 (15-Dec-2018)
> > |
> > | stat: missing operand
> > | Try 'stat --help' for more information.
> > | chown: invalid user: '/meta'
> > | ls: cannot access
> '/work/build/tmp/deploy/buildchroot-target/debian-buster-armhf/tmp/tmp.z4IScQtkyS/isar-image-base-debian-buster-stm32mp15x.wic/*.direct':
> No such file or directory
> > | mv: missing destination file operand after
> '/work/build/tmp/deploy/images/stm32mp15x/isar-image-base-debian-buster-stm32mp15x.wic.img'
>
> > | Try 'mv --help' for more information.
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Execution of
> '/work/build/tmp/work/debian-buster-armhf/isar-image-base-stm32mp15x-wic-img/1.0-r0/temp/run.do_wic_image.17923'
> failed with exit code 1:
> > | INFO: Creating image(s)...
> > |
> > | ERROR: _exec_cmd: tune2fs -L fsbl1
> /tmp/tmp.z4IScQtkyS/isar-image-base-debian-buster-stm32mp15x.wic/tmp.wic.9q0k2f75/tf-a-stm32mp157c-ev1.stm32.1
> returned '1' instead of 0
> > | output: /usr/sbin/tune2fs: Bad magic number in super-block while
> trying to open
> /tmp/tmp.z4IScQtkyS/isar-image-base-debian-buster-stm32mp15x.wic/tmp.wic.9q0k2f75/tf-a-stm32mp157c-ev1.stm32.1
>
> > | tune2fs 1.44.5 (15-Dec-2018)
> > |
> > | stat: missing operand
> > | Try 'stat --help' for more information.
> > | chown: invalid user: '/meta'
> > | ls: cannot access
> '/work/build/tmp/deploy/buildchroot-target/debian-buster-armhf/tmp/tmp.z4IScQtkyS/isar-image-base-debian-buster-stm32mp15x.wic/*.direct':
> No such file or directory
> > | mv: missing destination file operand after
> '/work/build/tmp/deploy/images/stm32mp15x/isar-image-base-debian-buster-stm32mp15x.wic.img'
>
> > | Try 'mv --help' for more information.
> > | WARNING: exit code 1 from a shell command.
> > |
> > ERROR: Task
> (mc:stm32mp15x-buster:/repo/meta-isar/recipes-core/images/isar-image-base.bb:do_wic_image)
> failed with exit code '1'
> >
> > Any ideas where to dig?
>
> It must be related to the raw partitions we are defining for the
> bootloader artifacts. But I just copied from
>
>
> https://github.com/STMicroelectronics/meta-st-stm32mp/blob/dunfell/wic/sdcard-stm32mp157c-dk2-optee-1GB.wks.in
>
> It looked indeed strange to me that those raw partitions where declared
> with "--fstype=ext4", but removing that does not solve the issue.
>
> Is your wic revision in line with or even ahead of dunfell?
>
The wic version is 141a3c9ce93bc3d526303021ecf0460c6e9fea8a. Latest master
at that time. Ahead of dunfell.
https://github.com/openembedded/openembedded-core/commit/141a3c9ce93bc3d526303021ecf0460c6e9fea8a
Thanks,
Vijai Kumar K
> Jan
>
> >
> > Jan
> >
> > [1] https://github.com/siemens/isar/commits/jan/wic-testing
> > [2] https://groups.google.com/forum/#!topic/isar-users/ijj6mdBfb2w
> >
>
> --
> Siemens AG, T RDA IOT
> Corporate Competence Center Embedded Linux
>
[-- Attachment #1.2: Type: text/html, Size: 6573 bytes --]
next prev parent reply other threads:[~2020-10-14 5:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 16:52 Vijai Kumar K
2020-10-05 16:53 ` [PATCH v5 1/8] wic: Update to the latest wic from openembedded core Vijai Kumar K
2020-10-05 16:53 ` [PATCH v5 2/8] wic/plugins: Fix wic plugins to work with the latest wic Vijai Kumar K
2020-10-05 16:53 ` [PATCH v5 3/8] wic-img: Satisfy the quirks of " Vijai Kumar K
2020-10-14 8:59 ` vijaikumar....@gmail.com
2020-10-05 16:53 ` [PATCH v5 4/8] wic_fakeroot: Handle standalone pseudo invocations Vijai Kumar K
2020-10-05 16:55 ` [PATCH v5 5/8] meta-isar/conf: Add provision to debug WIC Vijai Kumar K
2020-10-05 16:55 ` [PATCH v5 6/8] debian-common: Add tar as a dependency for wic Vijai Kumar K
2020-10-05 16:55 ` [PATCH v5 7/8] Fix legacy bios boot partition Vijai Kumar K
2020-10-05 16:55 ` [PATCH v5 8/8] meta-isar/canned-wks: Remove unwanted /boot mountpoint Vijai Kumar K
2020-10-05 16:59 ` [PATCH v5 0/8] WIC update vijaikumar....@gmail.com
2020-10-06 4:55 ` vijaikumar....@gmail.com
2020-10-06 9:13 ` Baurzhan Ismagulov
2020-10-07 10:49 ` vijaikumar....@gmail.com
2020-10-13 18:22 ` Jan Kiszka
2020-10-13 18:30 ` Jan Kiszka
2020-10-14 5:56 ` vijaikumar....@gmail.com [this message]
2020-10-14 13:23 ` vijaikumar....@gmail.com
2020-10-14 5:54 ` vijaikumar....@gmail.com
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=d0e712de-95e4-4813-affd-160528a92746n@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=isar-users@googlegroups.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