I have a Debian-based OS image that I have been using for more than a year, it works fine
on the C2, C3 and C4 BeagleBoard (not XM). It boots fine on the C5, but the USB host
port doesn’t work. What I see is that the system doesn’t discover
the USB devices plugged into the port, either at boot-up or when plugged in later.
The USB port does deliver power to the devices, though.
I have THREE C5 boards, one from mid 2011, two that are brand new, all show
this same problem.
If there are any settings in the u-boot that need to be changed, please let me know.
I did a printenv and compared the two systems, there are MANY differences. So, maybe
one of those is fouling up the old OS. If I need to load a new version of Linux, a pointer
to a suitable one with a light memory footprint and with <sys/mman.h> configured for
the OMAP GPIO registers would be greatly appreciated.
This has pretty well stalled my entire project. Thanks for any help anyone can provide.
Jon
So... Does the boot loader your using actually support the C5
(u-boot/spl/x-loader/etc)? Just because it works on the C3/C4,
doesn't guarantee anything, specially if it's a year old.. Kernel
version could be a little important..
If unsure, a serial bootlog from power up would be helpful..
Regards,
http://pico-systems.com/codes/C3boot.log
and the same OS on the C5 (where the USB doesn’t work)
http://pico-systems.com/codes/C5boot.log
Are there some settings that need to be different for the C5? Can I
just change the bootloader on the fat32 partition, and leave the
rest of the system the same?
/proc/version shows :
Linux version 2.6.31.6 (root@beaglecnc) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Tue Nov 17 18:2
1:25 EST 2009
Thanks very much for help with this problem!
Jon
http://pico-systems.com/codes/C3boot.log
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31)
Board revision C
http://pico-systems.com/codes/C5boot.log
Texas Instruments X-Loader 1.5.0 (Jun 14 2011 - 22:04:07)
Beagle Rev C5
U-Boot 2009.01-00013-g52eddcd (Feb 03 2009 - 22:25:11)
Board revision Ax/Bx
http://pico-systems.com/codes/C3boot.log
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31)
Board revision C
http://pico-systems.com/codes/C5boot.log
Texas Instruments X-Loader 1.5.0 (Jun 14 2011 - 22:04:07)
Beagle Rev C5
U-Boot 2009.01-00013-g52eddcd (Feb 03 2009 - 22:25:11)
Board revision Ax/Bx
*************
Do you see the difference now? They aren't technically running the
"same" software
software... Upgrade your u-boot on the C5 (and might as well update
the X-Loader as it's been replaced via spl u-boot) as it's not
detecting the board as a revision c and thus TURNING on the usb
voltage rail...
"not" TURNING on the usb voltage rail...
Missing my caffeen.. 
Regards,
Do you see the difference now? They aren’t technically running the
“same” software
software… Upgrade your u-boot on the C5 (and might as well update
the X-Loader as it’s been replaced via spl u-boot) as it’s not
detecting the board as a revision c and thus TURNING on the usb
voltage rail…
“not” TURNING on the usb voltage rail…
Missing my caffeen…
OK, can you give me a little more help with this? If it is written down here, just a pointer
to the instructions should be all I need. But, I’m not clear whether this refers to
changing what is in the NAND flash physically on the Beagle Board, or changing
the u-boot.bin file in the FAT32 partition of the SD card.
Thanks again for the help!
Jon
Your C3 is loading u-boot.bin from nand and your C5 is loading
u-boot.bin from the mmc card... You should choose one over the other,
otherwise your going to have maintance nightmares..
Honestly for a large deployment such as your's i'd actually just nuke
the bootloader on the nand.. Call "nand chip.erase" from u-boot
prompt.. Then for then on (unless you reflash the bootloader) it'll
always default to the MLO/u-boot.bin on the sd card.. Much easier for
across the board upgrades as you just install the new sd card and you
don't run into problems such as an incompatable mlo/u-boot in nand
such as what you've just run into....
Regards,
bunch of stuff, then I rebooted, but the result appears to be the same.
I’m guessing when this works, I’m supposed to get :
*** Warning - bad CRC or NAND, using default environment
and I’m still not getting that. Do I have to perform any other command after
the nand chip.erase ?
Thanks,
Jon
“bricked” the beagle board. It outputs
…40W…
and just hangs there, as the NAND is erased. So, what do I do now???
Jon
Properly format the first partition of your sd card, then copy
MLO/u-boot.img to it..
I have a step by step example here:
http://elinux.org/BeagleBoardUbuntu#Partition_SD_Card
along with example MLO/u-boot files..
After you've create this new sd card with the correct boot files, then
copy the files (skipping the MLO/u-boot.img/u-boot.bin) from your old
sd card to it..
Regards,
OK, this is looking promising… but. I’m probably trying to take too many shortcuts, here.
So, I put these MLO and u-boot.img files on my existing SD card, and the system starts to boot, up until uncompressing the kernel.
I get :
U-Boot 2012.04.01-00005-g45939b4 (Apr 30 2012 - 09:34:17)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Beagle Rev C4
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Die ID #6f7c000400000000040398d314020017
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
gpio: pin 173 (gpio 173) value is 1
gpio: pin 7 (gpio 7) value is 0
SD/MMC found on device 0
reading uEnv.txt
835 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc …
reading uImage
3271552 bytes read
reading uInitrd
6005760 bytes read
Booting from mmc …
Booting kernel from Legacy Image at 80300000 …
Image Name: Linux-2.6.31.6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3271488 Bytes = 3.1 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
Booting from nand …
NAND read: device 0 offset 0x280000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can’t get kernel image!
Has there been a change to the format for a compressed kernel? Or, do I need to load a different kernel that
is compatible with that MLO and u-boot.img? I used your uEnv.txt file from the “step by step example”.
Thanks,
Jon
OK, I tried to follow these instructions carefully, there are a lot of options related to different Beagle and other
variants, which may have tripped me up. I have a BeagleBoard (not XM) C5. I took the vmlinuz-3.2.19-x13
kernel and installed it, and it follows the boot process up to a point. At the end, I get
[ 4.573822] Freeing init memory: 340K
[ 4.746734] mmc0: new SDHC card at address e624
[ 4.764099] mmcblk0: mmc0:e624 SD04G 3.69 GiB
[ 4.780792] udevd[66]: starting version 175
[ 4.794250] mmcblk0: p1 p2 p3
[ 6.170776] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null)
[ 7.172241] init: ureadahead main process (183) terminated with status 5
Sometimes it reboots after this point, otherwise it hangs. The heartbeat led is flashing
normally, and it seems to have loaded the USB-Ethernet driver for my hub with ethernet,
as it is blinking the LED showing Ethernet traffic. But, I can’t log in from the serial port.
(I note the name of the serial console has changed from ttyS0 to ttyO0, could that
have something to do with it?)
Any ideas what might be wrong?
Thanks,
Jon
OK, further data, if I wait long enough, it does start responding to the serial console, so I should
be able to setup passwd and log in.
Thanks,
Jon
OK, so I have the network set up, and can log in via ssh -X, this is great progress.
I installed emacs, and am having a problem with performance. Can’t quite figure
it out, but emacs -nw takes about 10 MINUTES to load up! I also note that
cron seems to be running a LOT, like 99% CPU utilization for 5 minutes, waits a
minute and starts up again. I looked at the cron.x files and didn’t see anything too
strange. Any idea what is causing this?
Thanks,
Jon
So, emacs wants d-bus, so I installed dbus, but it doesn’t make any difference. Still a 10 minute wait,
then get this message:
(emacs:2522): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
//bin/dbus-launch terminated abnormally without any error message
GConf Error: No D-BUS daemon running
Emacs runs OK after that. Also, still have cron burning up a huge amount of CPU time.
Thanks,
Jon