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@xxxx: registered as mmc0 > omap-hsmmc 481d8000.mmc@xxxx: 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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
