From: <daniel.sangorrin@toshiba.co.jp>
To: <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Cc: <nobuhiro1.iwamatsu@toshiba.co.jp>, <isar-users@googlegroups.com>
Subject: RE: porting iwg20m to isar-cip-core
Date: Wed, 5 Jun 2019 08:27:59 +0000 [thread overview]
Message-ID: <TY2PR01MB33231DCBB1664127B91D0673D0160@TY2PR01MB3323.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <d0acd9f6-2f30-2407-c202-5600b3750352@siemens.com>
Hi Jan,
> From: isar-users@googlegroups.com <isar-users@googlegroups.com> On Behalf Of Jan Kiszka
> On 05.06.19 04:16, Daniel Sangorrin wrote:
> > I wanted to use uImage because that's what is used in the
> > iwg20m manual, and it's known to work on Deby as well.
> > Ref:
> https://gitlab.com/cip-project/cip-core/deby/blob/master/poky/meta-cip-iwg20m/README.IWG20M.txt
> > Do you suggest that we should use bootz instead of bootm?
> > Is uImage not recommended or something? I have used uImage in many boards.
>
> BTW, we chose bootz (and distro boot) in order to be able to boot also stock
> Debian kernels - which work on a (slowly) increasing number of boards. I.e. Isar
> is modeled around the ideal case, not legacy ones.
I was surprised to see so many u-boot debian packages:
https://packages.debian.org/search?keywords=u-boot
For now, please let me go the legacy way (ask users to 'setenv' things). Do you have an example of how to emulate boot.scr on older u-boot versions. I
Iwamatsu-san is going to upgrade/mainstream the u-boot support for Renesas iwg20m. Once that is done I will modify the recipe.
# One thing though: if the flash process fails, you really need to get a JTAG device to unbrick the board (not sure if OpenOCD JTAG devices would be supported).
Thanks,
Daniel
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
> isar-users+unsubscribe@googlegroups.com.
> To post to this group, send email to isar-users@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/d0acd9f6-2f30-2407-c202-5600b3750352%40siemens.com.
> For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2019-06-05 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 2:16 Daniel Sangorrin
2019-06-05 2:16 ` [isar-cip-core] iwg20m: temporary patch for review v2 Daniel Sangorrin
2019-06-07 14:55 ` [cip-dev] " Ben Hutchings
2019-06-05 5:34 ` porting iwg20m to isar-cip-core daniel.sangorrin
2019-06-05 5:51 ` Jan Kiszka
2019-06-05 6:00 ` Jan Kiszka
2019-06-05 8:27 ` daniel.sangorrin [this message]
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=TY2PR01MB33231DCBB1664127B91D0673D0160@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 \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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