mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: perachet7@gmail.com
To: barebox@lists.infradead.org
Subject: rk3188 (radxa rock pro) boot failure w/ barebox 2018-04 and later
Date: Thu, 13 Sep 2018 13:18:54 +0200	[thread overview]
Message-ID: <1597963.4YffofffW7@think-future.de> (raw)

Hey list,

Between 2018-04 and 2018-05 tar release, barebox stops booting on rk3188 
(radxa rock pro).

A git bisect reveals (see end of mail for commit detail): 
	first bad commit: [2a94e821ba2e64890ac47b9ba177c7b6585b23be] ARM: For 
relocatable image force TEXT_BASE 0x0.

As was suggested on #barebox, I tried setting TEXT_BASE=0x10 at this commit 
but it's a no fix. 

It is however booting even later releases if the trailing "if !RELOCATABLE" is 
removed. I have yet to have a deeper look at the code modified by 
HAVE_CONFIGURABLE_TEXT_BASE and RELOCATABLE.

Furthermore, it seems the commit itself is only triggering a boot failure. The 
proper code causing it is probably hiding someplace else.

Any direction, ideas or hints given is appreciated.

Thanks.

cheers

S.



Following said commit:

git show 2a94e821ba2e64890ac47b9ba177c7b6585b23be
commit 2a94e821ba2e64890ac47b9ba177c7b6585b23be
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Fri Mar 9 09:12:08 2018 +0100

    ARM: For relocatable image force TEXT_BASE 0x0
    
    Nothing else should be used for the relocatable image case, so
    force TEXT_BASE to 0x0 and do not show it in the menu.
    
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index e7edc2ad4..563475205 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -2,7 +2,7 @@ config ARM
        bool
        select HAS_KALLSYMS
        select HAS_CACHE
-       select HAVE_CONFIGURABLE_TEXT_BASE
+       select HAVE_CONFIGURABLE_TEXT_BASE if !RELOCATABLE
        select HAVE_IMAGE_COMPRESSION
        default y
 
@@ -19,6 +19,10 @@ config ARM_USE_COMPRESSED_DTB
        select UNCOMPRESS
        select LZO_DECOMPRESS
 
+config TEXT_BASE
+       hex
+       default 0x0
+
 menu "System Type"
 
 config BUILTIN_DTB



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2018-09-13 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 11:18 perachet7 [this message]
2018-09-13 12:37 ` Sam Ravnborg
2018-09-14 18:20   ` Панов Андрей
2018-09-17  6:37     ` Sascha Hauer
     [not found]   ` <8463281536949204@think-future.de>
2018-09-14 21:41     ` perachet7
     [not found] ` <20180913123746.GA18653@think-future.de>
2018-09-14 21:33   ` perachet7
2018-09-17  7:30 ` Sascha Hauer

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=1597963.4YffofffW7@think-future.de \
    --to=perachet7@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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