What are the details of running the installer from SD? When I
boot on my BeagleBoard, this fails as I no longer have the
default boot environment.
To be clear, what are the U-Boot commands being executed when
the installer (SD:uImage.bin) is run?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
hi Gary,
Please consult the wiki page for details:
http://code.google.com/p/0xdroid/wiki/boot_nand
Thanks for your interest.
Sincerely,
Jim Huang (jserv)
http://0xlab.org/
hi Gary,
Thanks for your notice. It was broken due to some network problems. Fixed now.
We are really sorry for that. Please keep posting if you encounter
any troubles.
Also, the uImage.bin image seems wrong/broken - it's only 400KB
whereas previous versions were 1.9MB
http://downloads.0xlab.org/installer/beagle-donut-0x3/uImage.bin
--
I don't see how this applies - surely the process is to boot
first using the SD card *only* which then sets up the NAND
partitions, etc.
Can you provide a boot log of bringing up 0xdroid on the
BeagleBoard from scratch (all the U-Boot commands, etc)?
--
Yes. I would suggest you to use working Linux system to flash kernel
and root file system
images instead of using u-boot. Feel free to check the instructions:
http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing
> Can you provide a boot log of bringing up 0xdroid on the
> BeagleBoard from scratch (all the U-Boot commands, etc)?
>
NOTE: it is possible to boot from SD, but we don't prepare the
installer for that at the moment.
You can do that manually as issue #52 denotes:
http://code.google.com/p/0xdroid/issues/detail?id=52
That worked better - it booted from the SD card (as I expected),
then ran the automated installer. Sadly, when I reboot (from NAND)
I get this error:
No MMC card found
Booting from nand ...
NAND read: device 0 offset 0x280000, size 0x400000
NAND read from offset 280000 failed -74
4194304 bytes read: ERROR
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.29-omap1-00007-gdebf08
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2244000 Bytes = 2.1 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Note: I verified the files I downloaded:
[root@hermes beagle-donut-0x3]# md5sum -c md5sum.txt
android-beagle.ubi: OK
0xkernel-beagle.bin: OK
Ideas?
--You received this message because you are subscribed to the Google Groups "0xlab-devel" group.
To post to this group, send email to 0xlab...@googlegroups.com.
To unsubscribe from this group, send email to 0xlab-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/0xlab-devel?hl=en.
Good point. Thanks!
Thus, for the sake of boot time and compatibility, we should enforce
kernel image
size < 2 MB as the manner of release build. Issue tracked here:
http://code.google.com/p/0xlab-kernel/issues/detail?id=5
cheers,