From: Sicelo <absicsz@gmail.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: Merlijn Wajer <merlijn@wizzup.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
maemo-leste@lists.dyne.org, u-boot@lists.denx.de
Subject: Re: [maemo-leste] Broken u-boot on n900 hw (possibly CONFIG_POSITION_INDEPENDENT)
Date: Mon, 10 Oct 2022 23:30:21 +0200 [thread overview]
Message-ID: <Y0SO7d+uoayGbtdq@tp440p.steeds.sam> (raw)
In-Reply-To: <20221009193317.5cwxcmntr6ziaphn@pali>
On Sun, Oct 09, 2022 at 09:33:17PM +0200, Pali Rohár wrote:
> Hello!
>
> Current u-boot from master branch does not work on n900 hw. It does not
> show anything on display, there just nokia logo.
>
> In qemu it is working fine and all tests are passing. Also in qemu is
> display working without any problem.
>
> Could you help me to debug it? Maybe something is printed to serial
> console? Or maybe serial console could be used for printf-debugging?
>
> I just figured out that disabling CONFIG_POSITION_INDEPENDENT u-boot
> option make it working again. But it requires to restoring older version
> of lowlevel_init.S file which does not depend on POSITION_INDEPENDENT:
>
> git checkout 7c4ad9821758f98db127e9d6864671c906c02d3b -- board/nokia/rx51/lowlevel_init.S
>
> And also setting CONFIG_SYS_TEXT_BASE=0x80008000 (to some value in RAM).
Hi
I have a really crude serial console setup in place now, but very little
time, and even less experience with u-boot. I should be able to do the
tests for you on Saturday night (UTC+2). Perhaps over IRC might be a
good idea, in case I need some hand-holding, and if you still need the
help by then.
Regards
Sicelo
next prev parent reply other threads:[~2022-10-11 0:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 19:33 Broken u-boot on n900 hw (possibly CONFIG_POSITION_INDEPENDENT) Pali Rohár
2022-10-10 21:30 ` Sicelo [this message]
2022-10-20 20:06 ` [maemo-leste] " Pali Rohár
2022-10-21 19:09 ` Pali Rohár
2022-11-02 0:08 ` Pali Rohár
2022-11-09 20:33 ` Pali Rohár
2022-11-19 14:38 ` Ashish Shah
2022-11-19 18:24 ` Sicelo
2022-11-19 21:13 ` Pali Rohár
2022-11-20 15:33 ` Tom Rini
2022-11-20 16:13 ` Pali Rohár
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=Y0SO7d+uoayGbtdq@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=maemo-leste@lists.dyne.org \
--cc=merlijn@wizzup.org \
--cc=pali@kernel.org \
--cc=pavel@ucw.cz \
--cc=u-boot@lists.denx.de \
/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