mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: barebox@lists.infradead.org
Subject: Beaglebone Black defconfigs
Date: Fri, 11 Jun 2021 12:05:43 +0200	[thread overview]
Message-ID: <97CB9693-C624-4014-8E73-6FDCA035BD62@inside-m2m.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1982 bytes --]

Hello,

I am currently trying to bring up barebox for my Beaglebone Black devices.

I did an "ARCH=arm CROSS_COMPILE=arm-buildroot-linux-gnueabihf- make am335x_mlo_defconfig”, make and
copied resulting barebox-am33xx-beaglebone-mlo.img to MLO into my FAT boot partition.

Then I did "ARCH=arm CROSS_COMPILE=arm-buildroot-linux-gnueabihf- make omap3530_beagle_defconfig”, make 
and copied resulting barebox-beagleboard.img to barebox.bin into my boot FAT.

Is the the different prefix in the defconfigs (am33… vs. omap35…) reasonable? 
Is this approach generally reasonable?

Many references in internet to matching
defconfigs I found refer to non existing ones, there seems to happen great overhaul meanwhile. 
I am also asking because, well, it does not work:

barebox 2021.05.0-00093-g7689055a8 #2 Fri Jun 11 09:01:36 CEST 2021


Board: TI AM335x BeagleBone
detected 'BeagleBone Black'
omap-hsmmc 48060000.mmc@0.of: registered as mmc0
omap-hsmmc 481d8000.mmc@0.of: registered as mmc1
booting from MMC
mmc1: detected MMC card version 5.1
mmc1: registered mmc1
unable to handle paging request at address 0x4020f010
pc : [<8ffbbd5a>]    lr : [<8ffbbd89>]
sp : 9ffeffb0  ip : 00000000  fp : 00014e2c
r10: 00125920  r9 : 8ffbbce5  r8 : 9ffe4000
r7 : 80000000  r6 : 9fe1a46e  r5 : 402f0400  r4 : 8ffbbcdc
r3 : 0000060a  r2 : 4020f010  r1 : abe742c3  r0 : 80000000
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32

no stack data available

This repeats endlessly. I investigated the data sheet and if I am correct 0x4020f010 seems to be a reserved
area in L3 memory map.

Kind Regards
Konsti

INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen

Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010

konstantin.kletschke@inside-m2m.de
http://www.inside-m2m.de 

Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover


[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4124 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

             reply	other threads:[~2021-06-11 10:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 10:05 Konstantin Kletschke [this message]
2021-06-11 10:55 ` Ahmad Fatoum
2021-06-11 11:33   ` Konstantin Kletschke
2021-06-11 11:08 ` Sascha Hauer
2021-06-11 11:45   ` Konstantin Kletschke
2021-06-11 12:08     ` Sascha Hauer
2021-06-11 12:13       ` Konstantin Kletschke

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=97CB9693-C624-4014-8E73-6FDCA035BD62@inside-m2m.de \
    --to=konstantin.kletschke@inside-m2m.de \
    --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