mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* Beaglebone Black defconfigs
@ 2021-06-11 10:05 Konstantin Kletschke
  2021-06-11 10:55 ` Ahmad Fatoum
  2021-06-11 11:08 ` Sascha Hauer
  0 siblings, 2 replies; 7+ messages in thread
From: Konstantin Kletschke @ 2021-06-11 10:05 UTC (permalink / raw)
  To: barebox


[-- 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Beaglebone Black defconfigs
  2021-06-11 10:05 Beaglebone Black defconfigs Konstantin Kletschke
@ 2021-06-11 10:55 ` Ahmad Fatoum
  2021-06-11 11:33   ` Konstantin Kletschke
  2021-06-11 11:08 ` Sascha Hauer
  1 sibling, 1 reply; 7+ messages in thread
From: Ahmad Fatoum @ 2021-06-11 10:55 UTC (permalink / raw)
  To: Konstantin Kletschke, barebox

Hi,

On 11.06.21 12:05, Konstantin Kletschke wrote:
> 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.

The docs (https://www.barebox.org/doc/latest/boards/am335x.html) say the second stage
defconfig is omap_defconfig.
 
> Is the the different prefix in the defconfigs (am33… vs. omap35…) reasonable?

Second stage is much less size limited, because it runs from external SDRAM. This allows
having a config that builds images for multiple different boards and SoCs.

First stage runs from small SRAM, so images usually contain only code for a single
SoC. I haven't checked, but this may explain the different naming.

> 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 haven't been using barebox long enough, but I assume you found references
to old non-multi-image enabled OMAP support. Modern barebox platforms build
multiple images for different boards in one go and thus there are less
defconfigs.

> 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.

Compiling barebox for one SoC and running it on another can lead
to funny effects.

Cheers,
Ahmad

> 
> 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
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Beaglebone Black defconfigs
  2021-06-11 10:05 Beaglebone Black defconfigs Konstantin Kletschke
  2021-06-11 10:55 ` Ahmad Fatoum
@ 2021-06-11 11:08 ` Sascha Hauer
  2021-06-11 11:45   ` Konstantin Kletschke
  1 sibling, 1 reply; 7+ messages in thread
From: Sascha Hauer @ 2021-06-11 11:08 UTC (permalink / raw)
  To: Konstantin Kletschke; +Cc: barebox

Hi Konsti, nice to see you here :)

On Fri, Jun 11, 2021 at 12:05:43PM +0200, Konstantin Kletschke wrote:
> 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.

Yup, correct.

> 
> 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.

That's the config for the beaglebo*ard*, for the beaglebo*ne* you'll
have to use the omap_defconfig. This is the config for all omap/am33xx
boards. The resulting image is images/barebox-am33xx-beaglebone.img.

> 
> 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

Looks consistent. 0x4020f010 is OMAP3_SRAM_SCRATCH_SPACE + 0x10 used in
beagle_board_init_sdram(). It seems you start a binary for the
beagleboard on your beaglebone.

Regards,
 Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Beaglebone Black defconfigs
  2021-06-11 10:55 ` Ahmad Fatoum
@ 2021-06-11 11:33   ` Konstantin Kletschke
  0 siblings, 0 replies; 7+ messages in thread
From: Konstantin Kletschke @ 2021-06-11 11:33 UTC (permalink / raw)
  To: Ahmad Fatoum; +Cc: barebox


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

Dear Ahmad,

thanks for your kind explanations, I really appreciate it.
As Sascha already pointed out, my 1st stage was beaglebone and the second was beagleboard.
Which explains my confusion because it was reasonable. May be I discovered this, if I had investigated
more properly.

Regards
Konstantin



[-- 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Beaglebone Black defconfigs
  2021-06-11 11:08 ` Sascha Hauer
@ 2021-06-11 11:45   ` Konstantin Kletschke
  2021-06-11 12:08     ` Sascha Hauer
  0 siblings, 1 reply; 7+ messages in thread
From: Konstantin Kletschke @ 2021-06-11 11:45 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: barebox


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



> On 11. Jun 2021, at 13:08, Sascha Hauer <sha@pengutronix.de> wrote:
> 
> Hi Konsti, nice to see you here :)

Hi Sascha :-D Nice to see you, too.

> That's the config for the beaglebo*ard*, for the beaglebo*ne* you'll
> have to use the omap_defconfig. This is the config for all omap/am33xx
> boards. The resulting image is images/barebox-am33xx-beaglebone.img.

Thank. You. Very. Much.

E voila, second stage is fine:

[…]
barebox 2021.05.0-00093-g7689055a8 #5 Fri Jun 11 13:24:00 CEST 2021


Board: TI AM335x BeagleBone black
detected 'BeagleBone Black’
[…]


And a coloured command prompt! Are you guys serious? Nice!


> Looks consistent. 0x4020f010 is OMAP3_SRAM_SCRATCH_SPACE + 0x10 used in
> beagle_board_init_sdram(). It seems you start a binary for the
> beagleboard on your beaglebone.

All your assumptions are correct, I have a nice boot loader-coloured-prompt now and
will figure out now to give it my kernel to boot. Expect more stupid questions soon :-)

But you don’t tell me you know this address from brain muscle memory?

Regards
Konsti

[-- 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Beaglebone Black defconfigs
  2021-06-11 11:45   ` Konstantin Kletschke
@ 2021-06-11 12:08     ` Sascha Hauer
  2021-06-11 12:13       ` Konstantin Kletschke
  0 siblings, 1 reply; 7+ messages in thread
From: Sascha Hauer @ 2021-06-11 12:08 UTC (permalink / raw)
  To: Konstantin Kletschke; +Cc: barebox

On Fri, Jun 11, 2021 at 01:45:51PM +0200, Konstantin Kletschke wrote:
> 
> 
> > On 11. Jun 2021, at 13:08, Sascha Hauer <sha@pengutronix.de> wrote:
> > 
> > Hi Konsti, nice to see you here :)
> 
> Hi Sascha :-D Nice to see you, too.
> 
> > That's the config for the beaglebo*ard*, for the beaglebo*ne* you'll
> > have to use the omap_defconfig. This is the config for all omap/am33xx
> > boards. The resulting image is images/barebox-am33xx-beaglebone.img.
> 
> Thank. You. Very. Much.
> 
> E voila, second stage is fine:
> 
> […]
> barebox 2021.05.0-00093-g7689055a8 #5 Fri Jun 11 13:24:00 CEST 2021
> 
> 
> Board: TI AM335x BeagleBone black
> detected 'BeagleBone Black’
> […]
> 
> 
> And a coloured command prompt! Are you guys serious? Nice!

We're not in the 90ies anymore, are we? ;)

> 
> 
> > Looks consistent. 0x4020f010 is OMAP3_SRAM_SCRATCH_SPACE + 0x10 used in
> > beagle_board_init_sdram(). It seems you start a binary for the
> > beagleboard on your beaglebone.
> 
> All your assumptions are correct, I have a nice boot loader-coloured-prompt now and
> will figure out now to give it my kernel to boot. Expect more stupid questions soon :-)
> 
> But you don’t tell me you know this address from brain muscle memory?

Indeed that address looked suspicous to me, but I grepped the sourcecode
for 0x4020f010 and 0x4020f0 afterwards.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Beaglebone Black defconfigs
  2021-06-11 12:08     ` Sascha Hauer
@ 2021-06-11 12:13       ` Konstantin Kletschke
  0 siblings, 0 replies; 7+ messages in thread
From: Konstantin Kletschke @ 2021-06-11 12:13 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: barebox


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


>> And a coloured command prompt! Are you guys serious? Nice!
> 
> We're not in the 90ies anymore, are we? ;)

Yes, there have many things happen when I left bootloader/kernel programming, many.

And yesterday  I realised my u-boot was not reading my uEnv.txt, never did, neither where I put it.
So I bet faster is getting barebox to work than finding out how to make u-boot eating my uEnv.txt.

> Indeed that address looked suspicous to me, but I grepped the sourcecode
> for 0x4020f010 and 0x4020f0 afterwards.

Okay, I am “glad" you needed to verify with grep :-D

Konsti



[-- 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-06-11 12:15 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-11 10:05 Beaglebone Black defconfigs Konstantin Kletschke
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

mail archive of the barebox mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://lore.barebox.org/barebox/0 barebox/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 barebox barebox/ https://lore.barebox.org/barebox \
		barebox@lists.infradead.org barebox@lists.infradead.org
	public-inbox-index barebox

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git