* EST SBC8260
@ 2000-12-08 15:17 Louis Krigovski
0 siblings, 0 replies; 8+ messages in thread
From: Louis Krigovski @ 2000-12-08 15:17 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I am trying to boot HardHat Linux on EST SBC8260 board and I am stuck
with following error:
tty_io.c: process 1 (swapper) used obsolete /dev/cua - update software to
use /dev/ttyS0
I tried replacing all occurences of TTYAUX_MAJOR to TTY_MAJOR in uart.c
and I also tried making console symbolic link to ttyS0, but neither
change helped. Any idea what might be causing it?
Thanks,
--Louis
Linux version 2.4.0-test2 (lkrigovs@lub1021.lss.emc.com) (gcc version 2.95.2
19991030 (2.95.3 prerelease/franzo)) #27 Fri Dec 8 10:01:12 EST 2000
Boot arguments: root=/dev/nfs rw
nfsroot=168.159.39.21:/opt/hardhat/devkit/ppc/82xx/target
nfsaddrs=168.159.39.21
On node 0 totalpages: 2560
zone(0): 2560 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/nfs rw
nfsroot=168.159.39.21:/opt/hardhat/devkit/ppc/82xx/target
nfsaddrs=168.159.39.21
Calibrating delay loop... 87.86 BogoMIPS
Memory: 8732k available (868k kernel code, 376k data, 52k init)
[c0000000,c0a00000]
Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
kmem_create: Poisoning requested, but con given - bdev_cache
Inode-cache hash table entries: 1024 (order: 1, 8192 bytes)
kmem_create: Poisoning requested, but con given - inode_cache
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.3
Based upon Swansea University Computer Society NET3.039
kmem_create: Poisoning requested, but con given - skbuff_head_cache
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
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 512 bind 512)
Starting kswapd v1.6
CPM UART driver version 0.01
ttyS00 at 0x0000 is a SMC
ttyS01 at 0x0040 is a SMC
ttyS02 at 0x8100 is a SCC
ttyS03 at 0x8200 is a SCC
pty: 256 Unix98 ptys configured
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: registered device at major 7
loop: enabling 8 loop devices
eth0: SCC ENET Version 0.1, 00:a0:11:22:22:68
eth1: FCC ENET Version 0.1, 00:a0:11:a2:22:68
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 168.159.39.21, my address is 168.159.38.189
kmem_create: Forcing size word alignment - nfs_fh
Looking up port of RPC 100003/2 on 168.159.39.21
Looking up port of RPC 100005/2 on 168.159.39.21
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 52k init
tty_io.c: process 1 (swapper) used obsolete /dev/cua - update software to
use /dev/ttyS0
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EST SBC8260
@ 2000-12-14 18:36 Louis Krigovski
0 siblings, 0 replies; 8+ messages in thread
From: Louis Krigovski @ 2000-12-14 18:36 UTC (permalink / raw)
To: linuxppc-embedded
I found few more things:
Once its stuck I can see CPU spining on exception 800 (Floating Point
Unavailable) which calls load_up_fpu. Then load_up_fpu in turn
enables FPU bit in msr and executes lfd fr0,THREAD_FPSCR-4(r5)
which in turns generates trap 800 and again calls load_up_fpu.
So I am spining in those 2 functions. Any idea how to approach finding
what is causing it. According to MontaVista manual thing should just boot
up.
--Louis
> Date: Fri, 8 Dec 2000 10:17:00 -0500 (EST)
> From: Louis Krigovski <lkrigovs@emc.com>
> Subject: EST SBC8260
> To: linuxppc-embedded@lists.linuxppc.org
> MIME-Version: 1.0
> Content-MD5: 6/JpVvWXvOpkV8MzNhI1rA==
> X-Mailing-List: <linuxppc-embedded@lists.linuxppc.org>
> X-Loop: linuxppc-embedded@lists.linuxppc.org
>
>
> Hi,
> I am trying to boot HardHat Linux on EST SBC8260 board and I am stuck
> with following error:
>
> tty_io.c: process 1 (swapper) used obsolete /dev/cua - update software to
> use /dev/ttyS0
>
> I tried replacing all occurences of TTYAUX_MAJOR to TTY_MAJOR in uart.c
> and I also tried making console symbolic link to ttyS0, but neither
> change helped. Any idea what might be causing it?
>
> Thanks,
>
> --Louis
>
>
>
> Linux version 2.4.0-test2 (lkrigovs@lub1021.lss.emc.com) (gcc version 2.95.2
> 19991030 (2.95.3 prerelease/franzo)) #27 Fri Dec 8 10:01:12 EST 2000
> Boot arguments: root=/dev/nfs rw
> nfsroot=168.159.39.21:/opt/hardhat/devkit/ppc/82xx/target
> nfsaddrs=168.159.39.21
> On node 0 totalpages: 2560
> zone(0): 2560 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/nfs rw
> nfsroot=168.159.39.21:/opt/hardhat/devkit/ppc/82xx/target
> nfsaddrs=168.159.39.21
> Calibrating delay loop... 87.86 BogoMIPS
> Memory: 8732k available (868k kernel code, 376k data, 52k init)
> [c0000000,c0a00000]
> Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
> kmem_create: Poisoning requested, but con given - bdev_cache
> Inode-cache hash table entries: 1024 (order: 1, 8192 bytes)
> kmem_create: Poisoning requested, but con given - inode_cache
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.3
> Based upon Swansea University Computer Society NET3.039
> kmem_create: Poisoning requested, but con given - skbuff_head_cache
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> 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 512 bind 512)
> Starting kswapd v1.6
> CPM UART driver version 0.01
> ttyS00 at 0x0000 is a SMC
> ttyS01 at 0x0040 is a SMC
> ttyS02 at 0x8100 is a SCC
> ttyS03 at 0x8200 is a SCC
> pty: 256 Unix98 ptys configured
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: registered device at major 7
> loop: enabling 8 loop devices
> eth0: SCC ENET Version 0.1, 00:a0:11:22:22:68
> eth1: FCC ENET Version 0.1, 00:a0:11:a2:22:68
> Sending BOOTP requests.... OK
> IP-Config: Got BOOTP answer from 168.159.39.21, my address is 168.159.38.189
> kmem_create: Forcing size word alignment - nfs_fh
> Looking up port of RPC 100003/2 on 168.159.39.21
> Looking up port of RPC 100005/2 on 168.159.39.21
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 52k init
> tty_io.c: process 1 (swapper) used obsolete /dev/cua - update software to
> use /dev/ttyS0
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* EST SBC8260
@ 2001-03-22 16:01 Michael E Crowe
2001-03-22 17:18 ` Dan Malek
0 siblings, 1 reply; 8+ messages in thread
From: Michael E Crowe @ 2001-03-22 16:01 UTC (permalink / raw)
To: linuxppc-embedded
Hey guys,
I know therre have been several topics on this board already, but none
have answered a question that I have. In order to put a linux kernel
onto this board, do I have to also purchase a JTAG from WindRiver like
the VisionProbe or is the monitor that resides on the board enough to
get PPCBoot working on it?
Thanks,
Mike
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EST SBC8260
2001-03-22 16:01 EST SBC8260 Michael E Crowe
@ 2001-03-22 17:18 ` Dan Malek
2001-03-22 20:32 ` Scott Howard
0 siblings, 1 reply; 8+ messages in thread
From: Dan Malek @ 2001-03-22 17:18 UTC (permalink / raw)
To: Michael E Crowe; +Cc: linuxppc-embedded
Michael E Crowe wrote:
> .... In order to put a linux kernel
> onto this board, do I have to also purchase a JTAG from WindRiver like
> the VisionProbe or is the monitor that resides on the board enough to
> get PPCBoot working on it?
The early boards I used didn't have much of a monitor, so I always
used JTAG.
The main problem is the Wind tools assume the monitor is in the on-board
flash, and the SIMM is a flash disk. If you power up the board, the
monitor will re-write the SIMM into something it understands, so you
can't put code out there and expect it to survive (at least with the
recent versions I have seen). If you can convince the on-board monitor
the flash the local part, well, you get one chance at PPCBoot :-).
Buy an Abatron BDI2000. You can use it for lots of things, including
programming/debugging PPCBoot and the Linux kernel once you get to
that point. It's worth every penny if you place any value on your
time.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EST SBC8260
2001-03-22 17:18 ` Dan Malek
@ 2001-03-22 20:32 ` Scott Howard
2001-03-22 21:38 ` Wolfgang Denk
0 siblings, 1 reply; 8+ messages in thread
From: Scott Howard @ 2001-03-22 20:32 UTC (permalink / raw)
To: linuxppc-embedded
The EST monitor ('VisionWare') has the ability to download images via
TFTP, either directly to RAM or to a file in its on-board flash file
system.
The catch is that the image has to be in EST's 'BDX' format. ELF files
can be converted to BDX using EST's 'convert' utility. Your EST
salesperson or FAE should be able to get you a copy of this program.
I was also able to load and boot a Linux kernel from the on-board
monitor. When building the kernel, you need to use the command 'make
vmlinux'. 'make zImage' creates an ELF file where the compressed kernel
image does not appear in the file's program header, and thus it will not
convert properly into BDX format. If you are using a RAM disk as your
root filesystem, then the RAM disk image also needs to be converted to
BDX format so it can be downloaded as well.
The last detail is that the kernel uses a value for the IMMR register
that is different from that set up by visionWare, and it loads at
address 0 which is protected by the visionWare monitor; so some minor
mods are necessary to the boot code to load at some other address,
re-write the IMMR, relocate to zero and then continue with the remainder
of the boot process.
Scott
Dan Malek wrote:
>
> Michael E Crowe wrote:
>
> > .... In order to put a linux kernel
> > onto this board, do I have to also purchase a JTAG from WindRiver like
> > the VisionProbe or is the monitor that resides on the board enough to
> > get PPCBoot working on it?
>
> The early boards I used didn't have much of a monitor, so I always
> used JTAG.
>
> The main problem is the Wind tools assume the monitor is in the on-board
> flash, and the SIMM is a flash disk. If you power up the board, the
> monitor will re-write the SIMM into something it understands, so you
> can't put code out there and expect it to survive (at least with the
> recent versions I have seen). If you can convince the on-board monitor
> the flash the local part, well, you get one chance at PPCBoot :-).
>
> Buy an Abatron BDI2000. You can use it for lots of things, including
> programming/debugging PPCBoot and the Linux kernel once you get to
> that point. It's worth every penny if you place any value on your
> time.
>
> -- Dan
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EST SBC8260
2001-03-22 20:32 ` Scott Howard
@ 2001-03-22 21:38 ` Wolfgang Denk
0 siblings, 0 replies; 8+ messages in thread
From: Wolfgang Denk @ 2001-03-22 21:38 UTC (permalink / raw)
To: Scott Howard; +Cc: linuxppc-embedded
In message <3ABA6144.CF8D07C1@sthoward.com> you wrote:
>
...
> The last detail is that the kernel uses a value for the IMMR register
> that is different from that set up by visionWare, and it loads at
> address 0 which is protected by the visionWare monitor; so some minor
> mods are necessary to the boot code to load at some other address,
> re-write the IMMR, relocate to zero and then continue with the remainder
> of the boot process.
This still seems a long way to go when you can just install PPCBoot
and have full Linux support.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Were there fewer fools, knaves would starve. - Anonymous
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* EST SBC8260
@ 2001-11-30 19:11 Andrew Dixon
0 siblings, 0 replies; 8+ messages in thread
From: Andrew Dixon @ 2001-11-30 19:11 UTC (permalink / raw)
To: 'linuxppc-embedded@lists.linuxppc.org'
Hi All,
I'm starting a project to get Linux up on the EST sbc8260 boards that we
have in our lab. I was just wondering if I should try a PPC specific
kernel like the one that benh maintains or if a stock linux kernel would
do the trick.
Any suggestions, tips, hints, etc. . . would be greatly appreciated.
Thanks,
Andy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* EST sbc8260
@ 2001-11-30 20:45 Andrew Dixon
0 siblings, 0 replies; 8+ messages in thread
From: Andrew Dixon @ 2001-11-30 20:45 UTC (permalink / raw)
To: ppclist
Hi Everyone,
I'm trying to boot linux on the EST sbc8260 boards that we've got in our
lab and I was wondering if anyone could recommend a kernel to use.
Specifically I was wondering if it's better to use the standard kernel
from http://www.kernel.org or if another, ppc specific, tree (like the
one benh maintains) would be better.
Any hints, tips, suggestions, etc. . . would be greatly appreciated.
Thanks,
Andy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2001-11-30 20:45 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-03-22 16:01 EST SBC8260 Michael E Crowe
2001-03-22 17:18 ` Dan Malek
2001-03-22 20:32 ` Scott Howard
2001-03-22 21:38 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 20:45 EST sbc8260 Andrew Dixon
2001-11-30 19:11 EST SBC8260 Andrew Dixon
2000-12-14 18:36 Louis Krigovski
2000-12-08 15:17 Louis Krigovski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).