From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Chris Paterson <Chris.Paterson2@renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Hung Tran <hung.tran.jy@renesas.com>,
Pavel Machek <pavel@denx.de>,
cip-dev <cip-dev@lists.cip-project.org>
Subject: Re: Preparing isar-cip-core for RZ/Five
Date: Wed, 5 Oct 2022 20:21:51 +0200 [thread overview]
Message-ID: <20221005182151.GA16437@duo.ucw.cz> (raw)
In-Reply-To: <b6504b75-d609-d46b-55fb-3fd2b00780c7@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Hi!
> > But due to the weird U-Boot setup, I had to add some hacks, rather than
> > a proper boot process.
>
> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commits/wip/rzfive
>
> Test by flashing the image to an SD-Card switching to SD booting on the
> module.
>
> Maybe we can find a better solution for the boot procedure before moving
> forward with this.
>
> Anyway, now we have a real distribution on this board. Pavel, can you
> re-check what you observed, if those issues persist with Debian?
I believe I was running Debian; two versions and Ubuntu, IIRC :-).
Can you check if ldconfig and gcc work for you? That were the
roadblocks I was hitting. If they do, I'll be interested in details of
your setup.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-10-05 18:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 18:36 Preparing isar-cip-core for RZ/Five Jan Kiszka
2022-10-03 20:12 ` Chris Paterson
2022-10-04 7:15 ` Jan Kiszka
2022-10-04 18:28 ` Jan Kiszka
2022-10-04 19:36 ` Jan Kiszka
2022-10-04 19:47 ` Jan Kiszka
2022-10-05 18:21 ` Pavel Machek [this message]
2022-10-06 6:29 ` Jan Kiszka
2022-10-06 6:49 ` Jan Kiszka
2022-10-06 7:07 ` Jan Kiszka
2022-10-06 7:08 ` Prabhakar Mahadev Lad
2022-10-06 7:26 ` Jan Kiszka
2022-10-06 11:43 ` Pavel Machek
2022-10-06 11:51 ` Jan Kiszka
2022-10-06 22:07 ` ldconfig segfault on RZ/Five was " Pavel Machek
2022-10-06 22:32 ` Pavel Machek
2022-10-07 8:18 ` Jan Kiszka
2022-10-07 10:19 ` Pavel Machek
2022-10-08 8:27 ` Jan Kiszka
2022-10-09 8:29 ` Jan Kiszka
2022-10-09 8:42 ` [cip-dev] " Biju Das
2022-10-11 9:30 ` Jan Kiszka
2022-10-11 10:34 ` Biju Das
2022-10-11 18:51 ` Florian Bezdeka
2022-10-11 20:15 ` Jan Kiszka
2022-10-11 20:48 ` Prabhakar Mahadev Lad
2022-10-12 9:50 ` Prabhakar Mahadev Lad
2022-10-13 8:36 ` Ulrich Hecht
2022-10-13 10:35 ` Pavel Machek
2022-10-13 21:47 ` Pavel Machek
2022-11-29 18:57 ` Prabhakar Mahadev Lad
2022-12-10 7:23 ` Jan Kiszka
2022-12-10 20:25 ` Pavel Machek
2022-12-12 13:51 ` Prabhakar Mahadev Lad
2022-12-12 13:24 ` Prabhakar Mahadev Lad
2022-10-09 19:20 ` Chris Paterson
2022-10-05 5:43 ` [cip-dev] " Biju Das
2022-10-04 22:30 ` Prabhakar Mahadev Lad
2022-10-05 5:45 ` 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=20221005182151.GA16437@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=hung.tran.jy@renesas.com \
--cc=jan.kiszka@siemens.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).