[#6063] In latest trunk, boot u-boot from uart and ethernet cant work

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

[#6063] In latest trunk, boot u-boot from uart and ethernet cant work

Submitted By: Vivi Li

Open Date

2010-06-09 06:04:36     Close Date

2010-06-10 03:18:48

Priority:

Medium     Assignee:

Mike Frysinger

Category:

N/A     Fixed In Release:

N/A

Found In Release:

N/A     Status:

Closed

Board:

Ezbrd     Processor:

BF518

Silicon Revision:

    Resolution:

N/A

Is the bug repeatable?:

N/A     

Summary: In latest trunk, boot u-boot from uart and ethernet cant work

Details:

 

Boot u-boot from uart in bf518f-ezbrd, ethernet cant work.

 

--

test@Linux123-ViviLi:/tftpboot> bfin-uclinux-ldr -l /tftpboot/u-boot.ldr /dev/ttyS0 && kermit -l /dev/ttyS0 -b 57600 -C connect

Loading LDR /tftpboot/u-boot.ldr ... OK!

Opening /dev/ttyS0 ... OK!

Configuring terminal I/O ... OK!

Trying to send autobaud ... OK!

Trying to read autobaud ... OK!

Checking autobaud ... OK!

Autobaud result: 115200bps 29.491mhz (header:0xBF DLL:0x10 DLH:0x00 fin:0x00)

Sending blocks of DXE 1 ... [11/11] (100%)[board said: 怘€æ€˜€ffž€æžþž`x]

[board said: ˜x˜x]

[board said: †ž]

[board said: x`fx~fx]

[board said: †ø~]

[board said: ]

[board said: ˜˜f~]

[board said: †žøžø†fæàž†žøžf††þžæxþ†æ€˜€žþžææ†~]

[board said: f昘]

[board said: ˜˜˜†]

[board said: f˜˜`˜†€f€˜€]

[board said: xžæøž˜ø]

[board said: æ˜æ˜†~]

[board said: †˜øž˜˜øfxfžžæ€˜€þ˜f~]

[board said: ˜˜øfxfžžæ€˜€f†ø†ø†~]

[board said: žæ€˜€ž˜~`†~]

[board said: žæføfxx†f€˜€ø˜f~˜øžæàææ†x†ž]

[board said: øž]                                                                                                   OK!

You may want to run minicom or kermit now

Quick tip: run 'ldr <ldr> <tty> && minicom'

Connecting to /dev/ttyS0, speed 57600

Escape character: Ctrl-\ (ASCII 28, FS): enabled

Type the escape character followed by C to get back,

or followed by ? to see other options.

----------------------------------------------------

 

bfin> printenv

bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600

bootcmd=run ramboot

bootdelay=5

baudrate=57600

loads_echo=1

autoload=no

rootpath=/romfs

netmask=255.255.255.0

hostname=bf518f-ezbrd

loadaddr=0x1000000

nc=set ncip ${serverip};set stdin nc;set stdout nc

ubootfile=u-boot.ldr

update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 +$(filesize);erase 0x20000000 +$(filesize);cp.b $(loadaddr) 0x20000000 $(filesize)

addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off

ramfile=uImage

ramargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600

ramboot=tftp $(loadaddr) $(ramfile);run ramargs;run addip;bootm

nfsfile=vmImage

nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3

nfsboot=tftp $(loadaddr) $(nfsfile);run nfsargs;run addip;bootm

flashboot=bootm 0x20100000

ethact=Blackfin EMAC

gatewayip=10.100.4.174

serverip=10.100.4.174

ipaddr=10.100.4.50

ethaddr=00:E0:22:FE:7A:2E

stdin=serial

stdout=serial

stderr=serial

 

Environment size: 1105/8188 bytes

bfin> ping 10.100.4.174

Using Blackfin EMAC device

ping failed; host 10.100.4.174 is not alive

bfin>

--

 

Follow-ups

 

--- Mike Frysinger                                           2010-06-09 18:44:52

i'm guessing you actually mean "cant work" and not "can

work"

 

--- Vivi Li                                                  2010-06-10 03:16:14

Yeah, you are right.

 

I checked with latest u-boot svn2321, ethernet can work.

So close this bug.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes