All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Config problem I suspect
Date: Fri, 06 Nov 2009 16:21:34 +0000	[thread overview]
Message-ID: <4AF44D0E.8040208@blueyonder.co.uk> (raw)
In-Reply-To: <4AF42564.6090402@blueyonder.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2739 bytes --]

On 06/11/09 13:32, 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
> 
> .config with hashes removed attached.
> Same result with other versions of MLO and u-boot.bin.
> Regards
> Sid.
> 

Sorry attached the wrong file.
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 #2: o-dss2 --]
[-- Type: application/octet-stream, Size: 14533 bytes --]

  parent reply	other threads:[~2009-11-06 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 13:32 Config problem I suspect Sid Boyce
2009-11-06 13:39 ` Gadiyar, Anand
2009-11-06 16:03   ` Sid Boyce
2009-11-06 16:21 ` Sid Boyce [this message]
2009-11-07  0:24   ` Sid Boyce

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=4AF44D0E.8040208@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.