[U-Boot-Users] Questions of uImage on sbc8260 board

[U-Boot-Users] Questions of uImage on sbc8260 board

[duo dong]

The uImage is loaded onto RAM of sbc8260/ATM board.
After starting the uImage, the msg shows:

=>bootm
## Booting image at 00100000 ...
   Image Name:   Linux-2.4.24-pre2
   Created:      2004-12-03   0:48:37 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip
compressed)
   Data Size:    632448 Bytes = 617.6 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Current stack ends at 0x03F75B60 => set upper limit
to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF00
bd address  = 0x03F75FB4
memstart    = 0x00000000
memsize     = 0x04000000
flashstart  = 0x40000000
flashsize   = 0x00400000
flashoffset = 0x00025000
sramstart   = 0x00000000
sramsize    = 0x00000000
immr_base   = 0xF0000000
bootflags   = 0x00000001
vco         =    264 MHz
sccfreq     =     66 MHz
brgfreq     =     66 MHz
intfreq     =    198 MHz
cpmfreq     =    132 MHz
busfreq     =     33 MHz
ethaddr     = 00:A0:1E:A8:7B:CB
IP addr     = 10.0.0.99
baudrate    = 115200 bps
No initrd
## Transferring control to Linux (at address 00000000)
...
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.24-pre2 (root at localhost.localdomain)
(gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0
3.2.2-2a_1)) #1 Thu Dec 2 19:38:30 EST 2004
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line:

Warning: real time clock seems stuck! <<-- ???

Calibrating delay loop... 131.89 BogoMIPS
Memory: 63220k available (1096k kernel code, 384k
data, 56k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536
bytes)
Inode cache hash table entries: 4096 (order: 3, 32768
bytes)
Mount cache hash table entries: 512 (order: 0, 4096
bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384
bytes)
Page-cache hash table entries: 16384 (order: 4, 65536
bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
Starting kswapd
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by
Axis Communications AB.
CPM UART driver version 0.01
ttyS0 on SMC1 at 0x0000, BRG7
ttyS1 on SMC2 at 0x0040, BRG8
ttyS2 on SCC1 at 0x8000, BRG1
ttyS3 on SCC2 at 0x8100, BRG2
pty: 256 Unix98 ptys configured
eth0: FCC2 ENET Version 0.4, 00:A0:1E:A8:7B:CC
RAMDISK driver initialized: 16 RAM disks of 4096K size
1024 blocksize

CFI: Found no TQM8260 Bank 0 device@location zero
<<--??

TQM8260: No supported flash chips found! <<-- ??

NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind
8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

VFS: Cannot open root device "" or 00:00 <<--??
Please append a correct "root=" boot option <<--??
Kernel panic: VFS: Unable to mount root fs on 00:00
<<--??

<0>Rebooting in 180 seconds..
 

Then, system hung.

The u-boot envs are:
=> printenv
bootcmd=version;echo;bootp;setenv bootargs
root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off;bootm
bootdelay=5
baudrate=9600
ethaddr=00:a0:1e:a8:7b:cb
loads_echo=1
do_echo=1
ipaddr=10.0.0.99
serverip=10.0.0.2
netmask=255.0.0.0
hostname=sbc8260
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.0.2 (Nov 27 2004 - 10:55:29)
 
Environment size: 392/262140 bytes

The uImage is build by using TQM8260_config.

Q1. Can the uImage build by using TQM8260_config can
be used on sbc8260 board? If can not, which config I
should use?

Q2. I marked several places above by "<<--??". Any one
see those before? If you do, please let me know how to
fix them.

Thanks,

dd




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[U-Boot-Users] Questions of uImage on sbc8260 board

[Wolfgang Denk]

In message <20041203054507.79341.qmail@web54404.mail.yahoo.com> you wrote:
> The uImage is loaded onto RAM of sbc8260/ATM board.
> After starting the uImage, the msg shows:

You're off topic here. This is the U-Boot  mailing  list.  There  are
other lists for Linux.

> Warning: real time clock seems stuck! <<-- ???

Your real time clock does not tick.

> CFI: Found no TQM8260 Bank 0 device at location zero
> <<--??
> 
> TQM8260: No supported flash chips found! <<-- ??

You're using a TQM8260 configuration on  a  non-TQM8260  board.  This
cannot work.

> VFS: Cannot open root device "" or 00:00 <<--??
> Please append a correct "root=" boot option <<--??
> Kernel panic: VFS: Unable to mount root fs on 00:00
> <<--??

You passed an empty (or blank-filled?) command line,  so  how  should
the kernel know where to find the root filesystem?

> => printenv
> bootcmd=version;echo;bootp;setenv bootargs
> root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
> ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off;bootm

This makes no sense at all. Commands are execurted in order.  SO  you
first  boot  the linux kernel (bootp), and then try to set bootargs -
but the "then" will never happen as U-Boot dows not continue  to  run
after Linux took over.


OK, so we finally got  some  U-Boot  stuff  here,  and  you  are  not
completely off topic ;-)

> Q1. Can the uImage build by using TQM8260_config can
> be used on sbc8260 board? If can not, which config I
> should use?

Of course you can build an uImage using  the  TQM8260  configuration.
But  this uImage will only be useful for TQM8260 boards. You must not
assume that it might run on any other hardware.

> Q2. I marked several places above by "<<--??". Any one
> see those before? If you do, please let me know how to
> fix them.

See above.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Software entities are more complex for their size  than  perhaps  any
other human construct because no two parts are alike. If they are, we
make  the  two  similar parts into a subroutine -- open or closed. In
this respect, software  systems  differ  profoundly  from  computers,
buildings, or automobiles, where repeated elements abound.
                                                   - Fred Brooks, Jr.

[U-Boot-Users] Questions of uImage on sbc8260 board

[Richard Danter]

duo dong wrote:
> 
> Warning: real time clock seems stuck! <<-- ???

This is normal for the sbc8260 and sbc8260ATM - there is no real-time 
clock chip on board. Don't worry about it.

> 
> 
> CFI: Found no TQM8260 Bank 0 device at location zero
> <<--??
> 
> TQM8260: No supported flash chips found! <<-- ??

Your using a build for the wrong board. There is a working build for the 
SBC8260 which should work for the ATM version.

> 
> VFS: Cannot open root device "" or 00:00 <<--??
> Please append a correct "root=" boot option <<--??
> Kernel panic: VFS: Unable to mount root fs on 00:00
> <<--??

You need to specify a valid boot line to tell the kernel to use NFS for 
the root file system.


> 
> The uImage is build by using TQM8260_config.
> 
> Q1. Can the uImage build by using TQM8260_config can
> be used on sbc8260 board? If can not, which config I
> should use?

Use the sbc8260_config. You may need to edit the sbc8260.h file for you 
clock settings, etc.

> 
> Q2. I marked several places above by "<<--??". Any one
> see those before? If you do, please let me know how to
> fix them.

See comments above.

If you need more help then let me know. I don't have an SBC8260ATM to 
hand today, but I can get one.

Rich

[U-Boot-Users] Questions of uImage on sbc8260 board

[duo dong]

Thanks for you and Wolfgong's help.
Now I can just skip the msg of real time clock.

I made some changes of config file and the linux
starts booting without FLASH error msgs.

1. NFS 
> > VFS: Cannot open root device "" or 00:00 <<--??
> > Please append a correct "root=" boot option <<--??
> > Kernel panic: VFS: Unable to mount root fs on
> 00:00
> You need to specify a valid boot line to tell the
> kernel to use NFS for 
> the root file system.

Do I have to use NFS to boot ? My server has problem
and I'm using serial port only now. Is there another
way to avoid using server? If I can, what steps I
should follow?

2. I'm trying to use ramdisk because the server is off
and get errors. The kernel is build with reamdisk and
loaded into RAM. 

The envs are as:
=> printenv
bootdelay=5
ethaddr=00:a0:1e:a8:7b:cb
loads_echo=1
do_echo=1
ipaddr=10.0.0.99
serverip=10.0.0.2
netmask=255.0.0.0
hostname=SBC8260
rootpath=/opt/ELDK/ppc_82xx
bootcmd=bootp
filesize=1E661A
bootargs=boot=/dev/ram rw
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.0.2 (Nov 27 2004 - 10:55:29)
baudrate=57600


3. => bootm
## Booting image at 00400000 ...
   Image Name:   Linux Multiboot-Image
   Created:      2004-12-07  18:20:37 UTC
   Image Type:   PowerPC Linux Multi-File Image (gzip
compressed)
   Data Size:    1992154 Bytes =  1.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Contents:
   Image 0:   591944 Bytes = 578.1 kB
   Image 1:  1400198 Bytes =  1.3 MB
   Verifying Checksum ... OK
   Uncompressing Multi-File Image ... OK
## Current stack ends at 0x03F75B60 => set upper limit
to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF10
bd address  = 0x03F75FB4
memstart    = 0x00000000
memsize     = 0x04000000
flashstart  = 0x40000000
flashsize   = 0x00400000
flashoffset = 0x00025000
sramstart   = 0x00000000
sramsize    = 0x00000000
immr_base   = 0xF0000000
bootflags   = 0x00000001
vco         =    264 MHz
sccfreq     =     66 MHz
brgfreq     =     66 MHz
intfreq     =    198 MHz
cpmfreq     =    132 MHz
busfreq     =     33 MHz
ethaddr     = 00:A0:1E:A8:7B:CB
IP addr     = 10.0.0.99
baudrate    =  57600 bps
## initrd at 0x00490894 ... 0x005E6619
(len=1400198=0x155D86)
   Loading Ramdisk to 03e1f000, end 03f74d86 ... OK
## Transferring control to Linux (at address 00000000)
...
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.24-pre2 (root at localhost.localdomain)
(gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0
3.2.2-
2a_1)) #1 Sun Dec 5 14:04:57 EST 2004
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: boot=/dev/ram rw
Calibrating delay loop... 131.89 BogoMIPS
Memory: 61928k available (1028k kernel code, 376k
data, 56k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536
bytes)
Inode cache hash table entries: 4096 (order: 3, 32768
bytes)
Mount cache hash table entries: 512 (order: 0, 4096
bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384
bytes)
Page-cache hash table entries: 16384 (order: 4, 65536
bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
Starting kswapd
CPM UART driver version 0.01
ttyS0 on SMC1 at 0x0000, BRG7
ttyS1 on SMC2 at 0x0040, BRG8
ttyS2 on SCC1 at 0x8000, BRG1
ttyS3 on SCC2 at 0x8100, BRG2
pty: 256 Unix98 ptys configured
eth0: FCC2 ENET Version 0.4, 00:A0:1E:A8:7B:CC
RAMDISK driver initialized: 16 RAM disks of 4096K size
1024 blocksize
loop: loaded (max 8 devices)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind
8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
crc error<6>Freeing initrd memory: 1367k freed <<--??
VFS: Cannot open root device "" or 00:00 <<--
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00
<<--
 <0>Rebooting in 180 seconds..

4. I did not rebuild the ramdisk image, just use the
one from SELF. Do I need rebuild it?

Thanks again,

dd

--- Richard Danter <richard.danter@ntlworld.com>
wrote:

> duo dong wrote:
> > 
> > Warning: real time clock seems stuck! <<-- ???
> 
> This is normal for the sbc8260 and sbc8260ATM -
> there is no real-time 
> clock chip on board. Don't worry about it.
> 
> > 
> > 
> > CFI: Found no TQM8260 Bank 0 device at location
> zero
> > <<--??
> > 
> > TQM8260: No supported flash chips found! <<-- ??
> 
> Your using a build for the wrong board. There is a
> working build for the 
> SBC8260 which should work for the ATM version.
> 
> > 
> > VFS: Cannot open root device "" or 00:00 <<--??
> > Please append a correct "root=" boot option <<--??
> > Kernel panic: VFS: Unable to mount root fs on
> 00:00
> > <<--??
> 
> You need to specify a valid boot line to tell the
> kernel to use NFS for 
> the root file system.
> 
> 
> > 
> > The uImage is build by using TQM8260_config.
> > 
> > Q1. Can the uImage build by using TQM8260_config
> can
> > be used on sbc8260 board? If can not, which config
> I
> > should use?
> 
> Use the sbc8260_config. You may need to edit the
> sbc8260.h file for you 
> clock settings, etc.
> 
> > 
> > Q2. I marked several places above by "<<--??". Any
> one
> > see those before? If you do, please let me know
> how to
> > fix them.
> 
> See comments above.
> 
> If you need more help then let me know. I don't have
> an SBC8260ATM to 
> hand today, but I can get one.
> 
> Rich
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[U-Boot-Users] Questions of uImage on sbc8260 board

[Wolfgang Denk]

In message <20041207231546.37360.qmail@web54401.mail.yahoo.com> you wrote:
>
> I made some changes of config file and the linux
> starts booting without FLASH error msgs.

Please take this discussion off this list. It has nothing to do  with
U-Boot and is off topic here.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The IQ of the group is the lowest IQ of a member of the group divided
by the number of people in the group.

[U-Boot-Users] Questions of uImage on sbc8260 board

[Richard Danter]

duo dong wrote:
> 
> 1. NFS 
> 
> Do I have to use NFS to boot ? My server has problem
> and I'm using serial port only now. Is there another
> way to avoid using server? If I can, what steps I
> should follow?

No, you do not _have_ to use NFS, but it is a lot easier than using a 
RAMDISK when your developing apps.

> 
> 2. I'm trying to use ramdisk because the server is off
> and get errors. The kernel is build with reamdisk and
> loaded into RAM. 

How exactly are you loading the kernel/ramdisk image?

> 
> 3. => bootm
> ## Booting image at 00400000 ...
>    Image Name:   Linux Multiboot-Image

<snip>

> RAMDISK: Compressed image found at block 0
> crc error<6>Freeing initrd memory: 1367k freed <<--??

I'm not sure what is causing this, was the image corrupted when you 
downloaded? Maybe someone else can help us here..?

> VFS: Cannot open root device "" or 00:00 <<--
> Please append a correct "root=" boot option

Your boot options should have root=/dev/ram0

> Kernel panic: VFS: Unable to mount root fs on 00:00
> <<--
>  <0>Rebooting in 180 seconds..
> 
> 4. I did not rebuild the ramdisk image, just use the
> one from SELF. Do I need rebuild it?

I used one of the Denx ramdisks with no problems and didn't need to 
rebuild anything. I didn't build a unified kernel/ramdisk image though, 
I just loaded the kernel and then the example ramdisk unchanged. Try that.

Rich

[U-Boot-Users] Questions of uImage on sbc8260 board

[Richard Danter]

Sorry all, didn't mean to reply to the whole list.

Rich


Richard Danter wrote:
> duo dong wrote:
> 
>>
>> 1. NFS
>> Do I have to use NFS to boot ? My server has problem
>> and I'm using serial port only now. Is there another
>> way to avoid using server? If I can, what steps I
>> should follow?
> 
> 
> No, you do not _have_ to use NFS, but it is a lot easier than using a 
> RAMDISK when your developing apps.
> 
>>
>> 2. I'm trying to use ramdisk because the server is off
>> and get errors. The kernel is build with reamdisk and
>> loaded into RAM. 
> 
> 
> How exactly are you loading the kernel/ramdisk image?
> 
>>
>> 3. => bootm
>> ## Booting image at 00400000 ...
>>    Image Name:   Linux Multiboot-Image
> 
> 
> <snip>
> 
>> RAMDISK: Compressed image found at block 0
>> crc error<6>Freeing initrd memory: 1367k freed <<--??
> 
> 
> I'm not sure what is causing this, was the image corrupted when you 
> downloaded? Maybe someone else can help us here..?
> 
>> VFS: Cannot open root device "" or 00:00 <<--
>> Please append a correct "root=" boot option
> 
> 
> Your boot options should have root=/dev/ram0
> 
>> Kernel panic: VFS: Unable to mount root fs on 00:00
>> <<--
>>  <0>Rebooting in 180 seconds..
>>
>> 4. I did not rebuild the ramdisk image, just use the
>> one from SELF. Do I need rebuild it?
> 
> 
> I used one of the Denx ramdisks with no problems and didn't need to 
> rebuild anything. I didn't build a unified kernel/ramdisk image though, 
> I just loaded the kernel and then the example ramdisk unchanged. Try that.
> 
> Rich
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 

[U-Boot-Users] Questions of uImage on sbc8260 board

[duo dong]

> How exactly are you loading the kernel/ramdisk
> image?

This time, I loaded the uImage to 100000 and pRamdis
to 200000. The boot code transfers control to Linux as
following:
## Transferring control to Linux (at address 00000000)
...
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.24-pre2 (root at localhost.localdomain)
(gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0
3.2.2-2a_1)) #1 Sun Dec 5 14:04:57 EST 2004
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram0 rw
Warning: real time clock seems stuck!
Calibrating delay loop... 131.89 BogoMIPS
Memory: 61928k available (1028k kernel code, 376k
data, 56k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536
bytes)
Inode cache hash table entries: 4096 (order: 3, 32768
bytes)
Mount cache hash table entries: 512 (order: 0, 4096
bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384
bytes)
Page-cache hash table entries: 16384 (order: 4, 65536
bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
Starting kswapd
CPM UART driver version 0.01
ttyS0 on SMC1 at 0x0000, BRG7
ttyS1 on SMC2 at 0x0040, BRG8
ttyS2 on SCC1 at 0x8000, BRG1
ttyS3 on SCC2 at 0x8100, BRG2
pty: 256 Unix98 ptys configured
eth0: FCC2 ENET Version 0.4, 00:A0:1E:A8:7B:CC
RAMDISK driver initialized: 16 RAM disks of 4096K size
1024 blocksize
loop: loaded (max 8 devices)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind
8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0

 
> > RAMDISK: Compressed image found at block 0
> > crc error<6>Freeing initrd memory: 1367k freed
> <<--??
 
> I'm not sure what is causing this, was the image
> corrupted when you 
> downloaded? Maybe someone else can help us here..?

The crc error is still there as:
RAMDISK: Compressed image found at block 0
crc error<6>Freeing initrd memory: 1367k freed
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 56k init

Then, system stuck.

Someoen can help on this?? please!!

> boot=/dev/ram rw.
Thanks, I made a mistake, it should be root=/dev/ram0
rw, not boot=/...
 
Sorry I response too late. I have another project on
hand, so I can only work on this one couple hours a
day.
 
dd


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[U-Boot-Users] Questions of uImage on sbc8260 board

[Wolfgang Denk]

In message <20041209063404.34374.qmail@web54404.mail.yahoo.com> you wrote:
> 
> This time, I loaded the uImage to 100000 and pRamdis
...

I think I told you before: this  is  the  U-Boot  mailing  list,  and
general Linux questions are OFF TOPIC here.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Never give in.  Never give in.  Never. Never. Never."
- Winston Churchill

[U-Boot-Users] Questions of uImage on sbc8260 board

[Ccool]

Le 3 D?cembre 2004 00:45, duo dong a ?crit :

> VFS: Cannot open root device "" or 00:00 <<--??
> Please append a correct "root=" boot option <<--??
> Kernel panic: VFS: Unable to mount root fs on 00:00
> <<--??

That ain't good ;)

> <0>Rebooting in 180 seconds..
> The u-boot envs are:
> => printenv
> bootcmd=version;echo;bootp;setenv bootargs
> root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
> ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off;bootm
> bootdelay=5
> baudrate=9600
> ethaddr=00:a0:1e:a8:7b:cb
> loads_echo=1
> do_echo=1
> ipaddr=10.0.0.99
> serverip=10.0.0.2
> netmask=255.0.0.0
> hostname=sbc8260
> stdin=serial
> stdout=serial
> stderr=serial
> ver=U-Boot 1.0.2 (Nov 27 2004 - 10:55:29)

you don't have any "bootargs" setup!! this might be it

> Q2. I marked several places above by "<<--??". Any one
> see those before? If you do, please let me know how to
> fix them.

If I understand correctly your problem, it is quite simple actually.  You need 
a variable "bootargs" to be passed to the kernel...  you could do something 
like that:


setenv console=ttyS0,9600 ip=$(ipaddr) root=$(root)

type that and with your u-boot settings, it should work.

good luck
Rapha?l

[U-Boot-Users] Questions of uImage on sbc8260 board

[VanBaren, Gerald]

> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf
> Of Wolfgang Denk
> Sent: Friday, December 03, 2004 2:43 AM
> To: duo dong
> Cc: u-boot-users at lists.sourceforge.net
> Subject: Re: [U-Boot-Users] Questions of uImage on sbc8260 board
>
> In message
> <20041203054507.79341.qmail@web54404.mail.yahoo.com> you wrote:
> > The uImage is loaded onto RAM of sbc8260/ATM board.
> > After starting the uImage, the msg shows:

[snip]

> OK, so we finally got  some  U-Boot  stuff  here,  and  you 
> are  not completely off topic ;-)
>
> > Q1. Can the uImage build by using TQM8260_config can be used on
> > sbc8260 board? If can not, which config I should use?
>
> Of course you can build an uImage using  the  TQM8260  configuration.
> But  this uImage will only be useful for TQM8260 boards. You
> must not assume that it might run on any other hardware.
>
> Best regards,
>
> Wolfgang Denk

Just to be totally complete, there is a sbc8260 target for u-boot, has
been for years and works fine.  A quick google search and eyeballing of
the WindRiver brochure gives me the impression that the sbc8260 ATM
board is a respin of the sbc8260 board with the ATM PHYs on-board (looks
like the same memory configuration -- that is a biggie for getting
u-boot running initially).  I'm guessing that the sbc8260 target would
be a MUCH better starting point than the TQM8260.

gvb


******************************************
The following messages are brought to you by the Lawyers' League of
IdioSpeak:

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************