Re: AW: Compiling glibc-2.3.2 (debian) on mpc8xx ;-)

Re: AW: Compiling glibc-2.3.2 (debian) on mpc8xx ;-)

[David Jander]

On Tuesday 09 March 2004 10:20, you wrote:
> Dear David,
> sadly I have got no answer to your question, but I want to ask you
> something:
> Are you using U-Boot for starting Linux?
> If you do, can you give me a short roadmap, how to port to new
> board?

Yes, we are using u-boot.
Well, here's a list of suggestions based on what we did:
1.- Read the README of u-boot.
2.- Assuming there are already other boards with the same CPU and at least a
more or less similar setup that are supported, pick one of them, and copy the
directory boards/xxxx to boards/yyyy (where yyyy is the name of your board).
3.- Go to include/configs and make a copy of the xxxx.h file. Don't forget to
add your board also to the Makefile.
4.- Watch out for special stuff for the board you are using as start, it could
get in your way.
5.- Check if the xxxx's config and board support files are indeed a good
starting point (clean documented sources, using the newest format of config
files and most important, get to fully understand the source).
6.- Look at several other examples to pick up ideas and learn from the
sources.
7.- Configure your board with the design information, and from what you
learned reading README and the examples.
8.- Leave SDRAM configuration for later (assuming you use a MPC8xx processor,
where SDRAM is a special issue), and look if you get something out of your
serial port first.
9.- Use Jtag or BDM interfaces to place the bootloader into flash.
(We used a homebrewed Jtag interface to program the on-board flash, although
everyone and ther brother in this list will probably say that you MUST do it
with the BDI2000 from abatron via the BDM port).
10.- Have a Scope at hand to examine the CS and address lines (if at all
possible). This may help to see what's going on before the serial port comes
into play.
11.- If you have a mpc8xx processor, read the technical notes from Micron
about how to interface SDRAM to the MPC8xx, and how to program the UPM
correctly. There's a tool from Motorola that let's you draw the waveforms on
screen and obtain the corresponding byte-code for the UPM. This might be
handy. Again look at and learn from what others did.

Good Luck!

Best regards,

--
David Jander
Protonic Holland.
tel.: +31 (0) 229 212928
fax.: +31 (0) 229 210930
Factorij 36 / 1628 AL Zwaag

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

remote access via shell

[Kevin P. Dankwardt]

I have a ppc 5100 that is currently running Linux. I also have downloaded
and looked at the ELDK. Neither appear to have a telnet nor a ssh daemon.
What daemon for remote access is recommended? Are there small versions
especially appropriate for embedded use? Versions that have Make files
conducive to cross-compilation for PPC?

Thanks,
Kevin Dankwardt


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: remote access via shell

[Wolfgang Denk]

In message <KCEOLLHGFJIAFNAMGACHEEPJDFAA.k@kcomputing.com> you wrote:
>
> I have a ppc 5100 that is currently running Linux. I also have downloaded
> and looked at the ELDK. Neither appear to have a telnet nor a ssh daemon.

You didn't look very carefully. telnetd is included with the ELDK as
/usr/sbin/in.telnetd; this is part of the
telnet-server-ppc_???-0.17-23_1 RPM.

> What daemon for remote access is recommended? Are there small versions

Secure Shell of course - if you can afford the size.

> especially appropriate for embedded use? Versions that have Make files
> conducive to cross-compilation for PPC?

;-)

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
The evolution of the human race will not be accomplished in  the  ten
thousand  years  of  tame  animals,  but in the million years of wild
animals, because man is and will always be a wild animal.
                                              - Charles Galton Darwin

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: remote access via shell

[Gerrit Van de Velde]

I'm using sshd (OpenSSH 3.8-p1 i believe) and sftp-server which are 394k
and 60k in size.
Their makefiles are not well adapted but if you have "Building embedded
linux systems" of O'Reilly, you'll build it without any problem

Kind regards,
Gerrit Van de Velde

Kevin P. Dankwardt wrote:

>I have a ppc 5100 that is currently running Linux. I also have downloaded
>and looked at the ELDK. Neither appear to have a telnet nor a ssh daemon.
>What daemon for remote access is recommended? Are there small versions
>especially appropriate for embedded use? Versions that have Make files
>conducive to cross-compilation for PPC?
>
>Thanks,
>Kevin Dankwardt
>
>


--
Kind regards,
ing. Gerrit Van de Velde

Onderzoeksgroep Digitale Technieken
W & K, Campus De Nayer
J. De Nayerlaan 5
2860 Sint-Katelijne-Waver

Tel. 015 / 31 69 44
Fax. 015 / 31 74 53
http://emsys.denayer.wenk.be


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RAM Disk problems

[Kevin A. Sapp]

Hello,

I am trying to bring up a RAM disk as the root file system.
Most everything is working until it come's time to mount it.
The logs are below.

I noticed in mount_block_root the get_fs_names appears
to returning a zero length string.

I have tried root=/dev/ram
root=/dev/ram0
root=/dev/rd/0
and combinatins with noinitrd.

FYI. The RAM disk will be loaded by a bus master and will have
to be persistant.

Any suggestions?
Thanks
Kevin


=> bootm 100000 200000
## Booting image at 00100000 ...
   Image Name:   Linux-2.4.20
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    485362 Bytes = 473.10 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00200000 ...
   Image Name:   Kevin Simple RAMDisk
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    1405884 Bytes =  1.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## initrd at 0x00200040 ... 0x003573FB (len=1405884=0x1573BC)
   Loading Ramdisk to 01c27000, end 01d7e3bc ... OK
kernel addr:00000000
machine_init<6>Memory BAT mapping: BAT2=16Mb, BAT3=8Mb, residual: 7Mb
Linux version 2.4.20 (kevin@linux4) (gcc version 3.2.1) #258 Wed Mar 10
07:55:32
 EST 2004
setup arch<4>ADS setup arch
On node 0 totalpages: 7936
zone(0): 7936 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram rw console=ttyS0,9600 nobats
ip=192.168.82.5
         console passed ttyS0:0
            Checking for registered console ttyS
         Prefered console -1
ADS init IRQ. NR_IRQS=256
ADS time init
ADS calibrate decrementer. FREQ=66666666, tb_ticks_per_jiffy=166666
           stdio console init
serial_console_setup
cons:c00ebc48 str:9600 cons->index:0 Calibrating delay loop... 132.71
BogoMIPS
Memory: 28828k available (828k kernel code, 288k data, 48k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
ADS init
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: devfs_debug: 0x0
devfs: boot_options: 0x1
pty: 256 Unix98 ptys configured
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
*********************SERIAL INIT*************
MPC8260 FCC Ethernet driver
BD rings initialised, RBASE=1B8160, TBASE=1B8360
Created eth0
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 2048 bind 4096)
eth0: OPEN
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.82.5, mask=255.255.255.0,
gw=255.255.255.255,
     host=192.168.82.5, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 1372k freed
Kernel panic: VFS: Unable to mount root fs on 01:00
 <0>Rebooting in 180 seconds..


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: RAM Disk problems

[Wolfgang Denk]

In message <404F26A5.7070807@catapult.com> you wrote:
>
> I am trying to bring up a RAM disk as the root file system.
> Most everything is working until it come's time to mount it.

This is an ext2 based ramdisk? Do you have ext2  support  enabled  in
your kernel? If yes, try disabling devfs.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I mean, I . . . think to understand you, I just don't know  what  you
are saying ...                        - Terry Pratchett, _Soul Music_

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: RAM Disk problems

[Jaap-Jan Boor]

Kevin,

I think I once had the same problem and it was caused by
having the kernel cmd line overwritten. You might check
that.

Jaap-Jan

On Wed, 2004-03-10 at 15:31, Kevin A. Sapp wrote:
> Hello,
>
> I am trying to bring up a RAM disk as the root file system.
> Most everything is working until it come's time to mount it.
> The logs are below.
>
> I noticed in mount_block_root the get_fs_names appears
> to returning a zero length string.
>
> I have tried root=/dev/ram
> root=/dev/ram0
> root=/dev/rd/0
> and combinatins with noinitrd.
>
> FYI. The RAM disk will be loaded by a bus master and will have
> to be persistant.
>
> Any suggestions?
> Thanks
> Kevin
>
>
> => bootm 100000 200000
> ## Booting image at 00100000 ...
>    Image Name:   Linux-2.4.20
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    485362 Bytes = 473.10 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at 00200000 ...
>    Image Name:   Kevin Simple RAMDisk
>    Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
>    Data Size:    1405884 Bytes =  1.3 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
> ## initrd at 0x00200040 ... 0x003573FB (len=1405884=0x1573BC)
>    Loading Ramdisk to 01c27000, end 01d7e3bc ... OK
> kernel addr:00000000
> machine_init<6>Memory BAT mapping: BAT2=16Mb, BAT3=8Mb, residual: 7Mb
> Linux version 2.4.20 (kevin@linux4) (gcc version 3.2.1) #258 Wed Mar 10
> 07:55:32
>  EST 2004
> setup arch<4>ADS setup arch
> On node 0 totalpages: 7936
> zone(0): 7936 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/ram rw console=ttyS0,9600 nobats
> ip=192.168.82.5
>          console passed ttyS0:0
>             Checking for registered console ttyS
>          Prefered console -1
> ADS init IRQ. NR_IRQS=256
> ADS time init
> ADS calibrate decrementer. FREQ=66666666, tb_ticks_per_jiffy=166666
>            stdio console init
> serial_console_setup
> cons:c00ebc48 str:9600 cons->index:0 Calibrating delay loop... 132.71
> BogoMIPS
> Memory: 28828k available (828k kernel code, 288k data, 48k init, 0k highmem)
> Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
> Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
> POSIX conformance testing by UNIFIX
> ADS init
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
> devfs: devfs_debug: 0x0
> devfs: boot_options: 0x1
> pty: 256 Unix98 ptys configured
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> *********************SERIAL INIT*************
> MPC8260 FCC Ethernet driver
> BD rings initialised, RBASE=1B8160, TBASE=1B8360
> Created eth0
> 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 2048 bind 4096)
> eth0: OPEN
> IP-Config: Guessing netmask 255.255.255.0
> IP-Config: Complete:
>       device=eth0, addr=192.168.82.5, mask=255.255.255.0,
> gw=255.255.255.255,
>      host=192.168.82.5, domain=, nis-domain=(none),
>      bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 1372k freed
> Kernel panic: VFS: Unable to mount root fs on 01:00
>  <0>Rebooting in 180 seconds..
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: RAM Disk problems

[Steven Blakeslee]

Also you can try an already created ramdisk that is known to work.  You can
download one from Wolfgang's site.  www.denx.de

-----Original Message-----
From: Jaap-Jan Boor [mailto:jjboor@aimsys.nl]
Sent: Wednesday, March 10, 2004 10:04 AM
To: Kevin A. Sapp
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RAM Disk problems



Kevin,

I think I once had the same problem and it was caused by
having the kernel cmd line overwritten. You might check
that.

Jaap-Jan

On Wed, 2004-03-10 at 15:31, Kevin A. Sapp wrote:
> Hello,
>
> I am trying to bring up a RAM disk as the root file system.
> Most everything is working until it come's time to mount it.
> The logs are below.
>
> I noticed in mount_block_root the get_fs_names appears
> to returning a zero length string.
>
> I have tried root=/dev/ram
> root=/dev/ram0
> root=/dev/rd/0
> and combinatins with noinitrd.
>
> FYI. The RAM disk will be loaded by a bus master and will have
> to be persistant.
>
> Any suggestions?
> Thanks
> Kevin
>
>
> => bootm 100000 200000
> ## Booting image at 00100000 ...
>    Image Name:   Linux-2.4.20
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    485362 Bytes = 473.10 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at 00200000 ...
>    Image Name:   Kevin Simple RAMDisk
>    Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
>    Data Size:    1405884 Bytes =  1.3 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
> ## initrd at 0x00200040 ... 0x003573FB (len=1405884=0x1573BC)
>    Loading Ramdisk to 01c27000, end 01d7e3bc ... OK
> kernel addr:00000000
> machine_init<6>Memory BAT mapping: BAT2=16Mb, BAT3=8Mb, residual: 7Mb
> Linux version 2.4.20 (kevin@linux4) (gcc version 3.2.1) #258 Wed Mar 10
> 07:55:32
>  EST 2004
> setup arch<4>ADS setup arch
> On node 0 totalpages: 7936
> zone(0): 7936 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/ram rw console=ttyS0,9600 nobats
> ip=192.168.82.5
>          console passed ttyS0:0
>             Checking for registered console ttyS
>          Prefered console -1
> ADS init IRQ. NR_IRQS=256
> ADS time init
> ADS calibrate decrementer. FREQ=66666666, tb_ticks_per_jiffy=166666
>            stdio console init
> serial_console_setup
> cons:c00ebc48 str:9600 cons->index:0 Calibrating delay loop... 132.71
> BogoMIPS
> Memory: 28828k available (828k kernel code, 288k data, 48k init, 0k
highmem)
> Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
> Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
> POSIX conformance testing by UNIFIX
> ADS init
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
> devfs: devfs_debug: 0x0
> devfs: boot_options: 0x1
> pty: 256 Unix98 ptys configured
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> *********************SERIAL INIT*************
> MPC8260 FCC Ethernet driver
> BD rings initialised, RBASE=1B8160, TBASE=1B8360
> Created eth0
> 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 2048 bind 4096)
> eth0: OPEN
> IP-Config: Guessing netmask 255.255.255.0
> IP-Config: Complete:
>       device=eth0, addr=192.168.82.5, mask=255.255.255.0,
> gw=255.255.255.255,
>      host=192.168.82.5, domain=, nis-domain=(none),
>      bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 1372k freed
> Kernel panic: VFS: Unable to mount root fs on 01:00
>  <0>Rebooting in 180 seconds..
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: RAM Disk problems

[song sam]

Hello Kevin,

Yeah,first check your command setting as Jaap-Jan said
and make sure it has the right format and correct
content.If it couldn't work,pls try to rebuilding your
LINUX kernel as Wolfgang suggested and download the
workable ramdisk from ftp.denx.de like Steven told.

The setting of ramargs for your reference:

u-boot>setenv ramargs setenv bootargs root=/dev/ram rw

> Jaap-Jan wrote:
>
> > I think I once had the same problem and it was caused by having the
> > kernel cmd line overwritten. You might check that.

Wolfgang Denk wrote:
> This is an ext2 based ramdisk? Do you have ext2 support enabled in
> your kernel? If yes, try disabling devfs.

Steven Blakeslee wrote:
> Also you can try an already created ramdisk that is known to work. You
> can download one from Wolfgang's site. www.denx.de

Hope this would work.

Sam

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: RAM Disk problems

[Kevin A. Sapp]

Thanks to all.
  Wolfgang had it.  No EXT2 support. Duh!

Kevin

>In message <404F26A5.7070807@catapult.com> you wrote:
>
>
>>I am trying to bring up a RAM disk as the root file system.
>>Most everything is working until it come's time to mount it.
>>
>>
>
>This is an ext2 based ramdisk? Do you have ext2  support  enabled  in
>your kernel? If yes, try disabling devfs.
>
>Best regards,
>
>Wolfgang Denk
>
>--
>Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
>Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
>I mean, I . . . think to understand you, I just don't know  what  you
>are saying ...                        - Terry Pratchett, _Soul Music_
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/