[U-Boot] Need Help in bulding U-boot-2010-06 for OpenRD client

kalyan karnati kriskalyan21 at gmail.com
Wed Jul 7 20:10:18 CEST 2010


Hi Prafulla/Albert,

Thanks alot for your help.
Finally using kwbimage.cfg solved the problem and my openRD_client came up
:)

Now, I want to boot Uimage and Filesystem from an MMC card. But the MMC
support was not enabled, I added the configurations for MMC support to
openrd_cleint.h.
---------------------------------
/* MMC support flags */
#define CONFIG_CMD_EXT2    1
#define CONFIG_CMD_FAT    1
#define CONFIG_MMC    1
#define CONFIG_GENERIC_MMC    1
#define CONFIG_CMD_MMC    1
-----------------------------------------------

But the U-boot doesn't detect the card. From the startup messages, I
observed that the driver for Kirkwood openrd_client is not found from
u-boot.
Is there any patch or work around available to enable the boot from MMC ?

---------------------------------------
U-Boot 2010.06 (Jul 07 2010 - 11:49:16)
OpenRD-Client

U-Boot code: 00600000 -> 00654810  BSS: -> 0069B060
SoC:   Kirkwood 88F6281_A0
RAM Configuration:
Bank #0: 00000000 256 MiB
Bank #1: 10000000 256 MiB
Bank #2: 00000000 0 Bytes
Bank #3: 00000000 0 Bytes
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
*MMC:*
Net:   egiga0, egiga1
Reset Ethernet PHY
smi_reg_read:(adr 8, off 21) value= 1070
smi_reg_read:(adr 8, off 0) value= 1140
smi_reg_read:(adr 8, off 0) value= 1140
88E1116 Initialized on egiga0
smi_reg_read:(adr 24, off 21) value= 1070
smi_reg_read:(adr 24, off 0) value= 1140
smi_reg_read:(adr 24, off 0) value= 1140
88E1116 Initialized on egiga1
-----------------------------------------

Then I tried using USB. But when I use the commands to load uImage into RAM,
some messages are shown and it never stops. I had to power cycle to go
u-boot prompt again. So loading any file/image into the RAM is not working
:( can you please help me on this ??

Please find the logs:

Marvell: setenv mainlineLinux yes
setenv arcNumber 2361
saveenv
reset

Marvell>> usb start
(Re)start USB...
USB:   Kirkwood-ehci: init hccr f1050100 and hcor f1050140 hc_length 64
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
req=5 (0x5), type=0 (0x0), value=1, index=0
USB_REQ_SET_ADDRESS
Len is 0
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
req=9 (0x9), type=0 (0x0), value=1, index=0
USB_REQ_SET_CONFIGURATION
Len is 0
req=6 (0x6), type=128 (0x80), value=768, index=0
USB_DT_STRING config
req=6 (0x6), type=128 (0x80), value=769, index=1
USB_DT_STRING config
req=6 (0x6), type=128 (0x80), value=770, index=1
USB_DT_STRING config
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
req=0 (0x0), type=160 (0xa0), value=0, index=0
req=3 (0x3), type=35 (0x23), value=8, index=1
Len is 0
req=0 (0x0), type=163 (0xa3), value=0, index=1
req=0 (0x0), type=163 (0xa3), value=0, index=1
req=1 (0x1), type=35 (0x23), value=16, index=1
Len is 0
.........................
.........................
dev=0065e9cc, pipe=c8010303, buffer=004fe994, length=31, req=(null)
TOKEN=0x80008c01
dev=0065e9cc, pipe=c8008383, buffer=004fea50, length=512, req=(null)
TOKEN=0x8d00
dev=0065e9cc, pipe=c8008383, buffer=004fe9e0, length=13, req=(null)
TOKEN=0x80008d00
1 Storage Device(s) found
*
**Marvell>> ext2load usb 0:1 0x00800000 /uImage
*
TOKEN=0x8c01
dev=0065e9cc, pipe=c8008383, buffer=004fd408, length=13, req=(null)
TOKEN=0x80008d00
dev=0065e9cc, pipe=c8010303, buffer=004fd3d4, length=31, req=(null)
TOKEN=0x80008c00
dev=0065e9cc, pipe=c8008383, buffer=0114f000, length=1024, req=(null)
TOKEN=0x80008d00
dev=0065e9cc, pipe=c8008383, buffer=004fd420, length=13, req=(null)
TOKEN=0x8d00
 <46178, 0, 1024>
dev=0065e9cc, pipe=c8010303, buffer=004fd3bc, length=31, req=(null)
TOKEN=0x8c00
dev=0065e9cc, pipe=c8008383, buffer=004fd408, length=13, req=(null)
TOKEN=0x80008d00
dev=0065e9cc, pipe=c8010303, buffer=004fd3d4, length=31, req=(null)
TOKEN=0x80008c01
dev=0065e9cc, pipe=c8008383, buffer=00525c50, length=1024, req=(null)
TOKEN=0x80009d00
dev=0065e9cc, pipe=c8008383, buffer=004fd420, length=13, req=(null)
TOKEN=0x8d00
ext2fs_read_block 00005a63
 <46278, 0, 1024>
dev=0065e9cc, pipe=c8010303, buffer=004fd3bc, length=31, req=(null)
TOKEN=0x8c01


Thanks,
Kalyan Karnati.


On Wed, Jul 7, 2010 at 10:05 AM, Albert ARIBAUD <albert.aribaud at free.fr>wrote:

> Le 07/07/2010 13:44, Prafulla Wadaskar a écrit :
>
>
>  you should use u-boot.bin to load in RAM @ 0x600000 (TEXT_BASE)
>>
>
> That's what I do, either through JTAG or by tftp/go in resident u-boot.
>
>
>  for boot from RAM, you must need at least SDRAM configured, so JTAG is the
>> way
>>
>
> JTAG does work indeed. Howvever, when:
>
> - I power up the board;
> - ROM boot loads u-boot from NAND and starts it;
> - I stop u-boot and get to the prompt;
> - I 'tftp' an u-boot.bin image into RAM at 1000000;
> - I 'go' to 1000000
>
> ... the tftp'ed image fails to boot although SDRAM is obviously already
> configured.
>
> OTOH, openOCD boots the RAM image fine, so I guess OpenOCD does some inits
> that the boot rom plus resident u-boot don't.
>
> Amicalement,
> --
> Albert.
>


More information about the U-Boot mailing list