From: "Mathieu Tétreault" <mathieu.alexandre.tetreault@gmail.com>
To: barebox@lists.infradead.org
Subject: Beaglebone black issue loading booting kernel
Date: Sun, 11 Oct 2015 06:51:06 -0400 [thread overview]
Message-ID: <CAO+PXKMVbPc5m2FqCcRudUz2Hxsu_UBxUSa-HZvvFA_uu+vDmA@mail.gmail.com> (raw)
I compiled barebox to run on the beaglebone black using the
am335x_mlo_defconfig and am335x_defonfig which gaves me the
barebox-am33xx-beaglebone.img(barebox.bin) and
barebox-am33xx-beaglebone-mlo.img(MLO).
This part works fine since I'm able to get in barebox and the board is
detected as beaglebone black
=== log ===
barebox 2015.10.0-00084-g54bf386 #2 Fri Oct 9 15:18:17 EDT 2015
Board: TI AM335x BeagleBone black
detected 'BeagleBone Black'
=========
If I let the autoboot start it always ends up looking for a NFS server
which I don't have right now.
What I have right now is an SD card with a rootfs generated by Yocto.
This rootfs is able to boot using the u-boot binary that yocto
compiled.
When I use:
===
barebox@TI AM335x BeagleBone black:/ global.bootm.image=/boot/uImage
barebox@TI AM335x BeagleBone black:/ global.bootm.oftree=/boot/boneblack.dtb
barebox@TI AM335x BeagleBone black:/
global.linux.bootargs.dyn.root="root=/dev/mmcblk0p2 rootfstype=ext4
rootwait"
===
I got the following log
===
barebox@TI AM335x BeagleBone black:/ bootm
Image Name: Linux-3.14.19-yocto-standard
OS: Linux
Architecture: ARM
Type: Kernel Image
Compression: uncompressed
Data Size: 5068000 Bytes = 4.8 MiB
Load Address: 80008000
Entry Point: 80008000
Loading U-Boot uImage '/boot/uImage'
Loading devicetree from '/boot/boneblack.dtb'
commandline: console=ttyO0,115200n8 ip=dhcp root=/dev/mmcblk0p2
rootfstype=ext4 rootwait
===
The last line I see on the terminal is the commandline:.... and then
it hangs there. I compared the load address and entry point with the
one that u-boot is using and they're the same.
I tried using the barebox internal dtb and providing an external one
that didn't changed anything.
From my understanding even if the rootpath is wrong the kernel should
start and later on I should receive an kernel panic/oops or something
like that.
Does anyone knows how I could debug that issue?
Regards,
Mathieu
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2015-10-11 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 10:51 Mathieu Tétreault [this message]
2015-10-12 8:24 ` Sascha Hauer
2015-10-12 9:27 ` Antony Pavlov
2015-10-12 10:14 ` 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=CAO+PXKMVbPc5m2FqCcRudUz2Hxsu_UBxUSa-HZvvFA_uu+vDmA@mail.gmail.com \
--to=mathieu.alexandre.tetreault@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