beagleboard and latest from git
Hi,
I'm trying to get some poky version to boot on my beagle-xm and managed with the distgcc tweak to compile it.
There seems to be something funny going on with u-boot. It looks like it changes to baud rate or something like this, since I cannot see any useful output:
Texas Instruments X-Loader 1.4.4ss (May 13 2011 - 08:39:41) Beagle xM Rev A
Reading boot sector
Loading u-boot.bin from mmc
O�HJ$�z�mq��H�JI�ka
... more stuff coming ...
I followed the instructions for the instructions in README.hardware to create boot.scr
So I just used some older known working u-boot.bin and the kernel comes up until:
regulator_init_complete: incomplete constraints, leaving VDAC on twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) Waiting for root device /dev/mmcblk0p2...
usb 1-2: new high speed USB device using ehci-omap and address 2 hub 1-2:1.0: USB hub found
hub 1-2:1.0: 5 ports detected
usb 1-2.1: new high speed USB device using ehci-omap and address 3 smsc95xx v1.0.4
smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, ae:00:20:f9:52:ae
mmc0: error -110 whilst initialising SD card
... here it stucks ...
What is the "last known good" sato-sdk for the beagleboard?
Regards,
Robert..."If you want more effective programmers, you will discover that they should not waste their time debugging - they should not introduce the bugs to start with." - Dijkstra
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
Hi,
I switched a bit around between various versions in the meantime and that's what I figured out:
1) the latest u-boot (or some configuration of it) from git does not seem to work for the beagleboard
2) if I use U-Boot 2011.03-00038-g8d4addc-dirty (May 13 2011 - 00:01:02) which comes with bernard-5.0.1 things look much better.
U-Boot 2010.12-00038-g8d4addc-dirty (May 13 2011 - 08:44:08) is the suspect. Why does the latest and greatest from git use an older u-boot version than bernard 5.0.1?
I interrupt the u-boot autoboot and do the following:
OMAP3 beagleboard.org # sete console "ttyO2,115200n8" OMAP3 beagleboard.org # mmc rescan ${mmcdev} OMAP3 beagleboard.org # run loaduimage reading uImage
2632316 bytes read
OMAP3 beagleboard.org # run mmcboot
and voila:
Yocto (Built by Poky 5.0) 1.0+snapshot-20110512 beagleboard ttyO2
beagleboard login: root
root@beagleboard:~#
This time even with networking.
This means that the latest and greatest rootfs seems OK.
Regards,
Robert
..."It is NOT portable (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have :-(." - Linus Benedict Torvalds([email protected]),
1991-08-25 23:12:08 PST -
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
Quoted 4 lines · Robert Berger
Hi,
I switched a bit around between various versions in the meantime and that's what I figured out:
Thanks for the analysis Robert. There is a bug open for this:
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1029
If you want to take a shot and preparing a fix, please do. Otherwise, we'll get to it for the M1 milestone.
Thanks,
Darren
Quoted 50 lines
1) the latest u-boot (or some configuration of it) from git does not seem to work for the beagleboard
2) if I use U-Boot 2011.03-00038-g8d4addc-dirty (May 13 2011 - 00:01:02) which comes with bernard-5.0.1 things look much better.
U-Boot 2010.12-00038-g8d4addc-dirty (May 13 2011 - 08:44:08) is the suspect. Why does the latest and greatest from git use an older u-boot version than bernard 5.0.1?
I interrupt the u-boot autoboot and do the following:
OMAP3 beagleboard.org # sete console "ttyO2,115200n8" OMAP3 beagleboard.org # mmc rescan ${mmcdev} OMAP3 beagleboard.org # run loaduimage reading uImage
2632316 bytes read
OMAP3 beagleboard.org # run mmcbootand voila:
Yocto (Built by Poky 5.0) 1.0+snapshot-20110512 beagleboard ttyO2
beagleboard login: root
root@beagleboard:~#This time even with networking.
This means that the latest and greatest rootfs seems OK.
Regards,
Robert
..."It is NOT portable (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have :-(." - Linus Benedict Torvalds([email protected]),
1991-08-25 23:12:08 PST -My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel