On 06/11/09 13:39, Gadiyar, Anand wrote: > Sid Boyce wrote: >> I have been trying the linux-2.6.32-rc5-omap-dss2 kernel and it halts >> with a USB error, DEBUG_LL configured. >> Reading boot sector >> Loading u-boot.bin from mmc >> >> >> U-Boot 2009.01-dirty (Feb 19 2009 - 12:23:21) >> >> I2C: ready >> OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz >> OMAP3 Beagle board + LPDDR/NAND >> DRAM: 256 MB >> NAND: 256 MiB >> Using default environment >> >> MUSB: using high speed >> In: serial usbtty >> Out: serial usbtty >> Err: serial usbtty >> Board revision C >> Serial #6b22000300000000040323090d00a00a >> Hit any key to stop autoboot: 0 >> reading boot.scr >> >> 679 bytes read >> Running bootscript from mmc ... >> ## Executing script at 80200000 >> reading x-load.bin.ift >> >> 19840 bytes read >> ***** Replacing x-load ***** >> Usage: >> nand - NAND sub-system >> >> HW ECC selected >> >> NAND erase: device 0 offset 0x0, size 0x80000 >> ^MErasing at 0x0 -- 25% complete.^MErasing at 0x20000 -- 50% >> complete.^MErasing at 0x40000 -- 75% complete.^MErasing at 0x60000 -- >> 100% complete. >> OK >> >> NAND write: device 0 offset 0x0, size 0x20000 >> 131072 bytes written: OK >> >> NAND write: device 0 offset 0x20000, size 0x20000 >> 131072 bytes written: OK >> >> NAND write: device 0 offset 0x40000, size 0x20000 >> 131072 bytes written: OK >> >> NAND write: device 0 offset 0x60000, size 0x20000 >> 131072 bytes written: OK >> reading u-boot-f.bin >> >> ** Unable to read "u-boot-f.bin" from mmc 0:1 ** >> ***** Erasing environment settings ***** >> Usage: >> nand - NAND sub-system >> >> >> NAND erase: device 0 offset 0x160000, size 0x20000 >> ^MErasing at 0x160000 -- 100% complete. >> OK >> reading normal.scr >> >> 603 bytes read >> ***** Executing normal.scr ***** >> ## Executing script at 80200000 >> reading uImage.bin >> >> 3160016 bytes read >> ***** Kernel: /dev/mmcblk0p1/uImage.bin ***** >> reading ramdisk.gz >> >> ** Unable to read "ramdisk.gz" from mmc 0:1 ** >> ***** RootFS: /dev/mmcblk0p2 ***** >> ## Booting kernel from Legacy Image at 80200000 ... >> Image Name: Linux-2.6.32-rc5-omap-dss2 >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 3159952 Bytes = 3 MB >> Load Address: 80008000 >> Entry Point: 80008000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Error, the USB hardware is not on B mode >> Left long enough, there are more messages ... and it hangs at "Waiting for root device /dev/mmcblk0p2...". > > I don't think this error comes from the stock linux-omap kernel. > Can you locate it in the kernel that you compiled? (grep -r maybe?) > The " B mode" message is part of drivers/net/wireless/ath5k/qcu.c, so i can disable ath5k as I don't have such a device. > Or in your u-boot? > > > Do you have a USB cable connected? Is the ID pin on the connector > connected to the USBOTG port on your board accidentally grounded? > > - Anand > > All devices are on the EHCI port. Attaching the full output - I left it at the "B mode" display, went out for a few hours and saw the remainder when I returned. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks
Attachment:
o-dss2
Description: Binary data
