Problem with customized MPC5200 board(copy from lite5200 design)
Hi, Our hardware group had designed a mpc5200 board using the same design as lite5200. Currently, we are using bdi2000(icecube config) to attempt to access the internal registers. By using the same procedure on lite5200, we can access the registers but we always could not do it on our board. Besides a hardware design flaw, is there any other init procedures that are required to use bdi2000 on our custom board? Did anyone face this kind of problem? rgds Yeo Kee Wee
8xx v2.6 TLB problems and suggested workaround
-Original Message- From: Marcelo Tosatti [mailto:marcelo.tosatti at cyclades.com] On Sat, Apr 09, 2005 at 09:03:54PM +0200, Joakim Tjernlund wrote: On Apr 8, 2005, at 7:07 AM, Marcelo Tosatti wrote: [SNIP] I still think this can be resolved in fault.c. Replace andis. r11, r10, 0x0200/* If set, indicates store op */ beq 2f in the DTLB Error handler with andis. r11, r10, 0x4800/* If set, indicates invalid pte or protection violation */ bne 2f Why does the current code jump to page fault handler in case of store operation? It doesn't. It jumps if some other bit is set as well. In your dcbst case it seems like invalid is set too. I hope that will be enough to work something out in fault.c. Out of curiosity, aren't there any other valid bit combinations for DSISR other than 0x4800 which should allow a fastpath DataTLBError ? Don't know, hopefully Dan knows. I can't find DSISR settings in MPC860UM.pdf neither paper manual. AFAICS it always refer to the PEM when talking about DSISR bit assignments. I can't find section 7-15 as you mentioned in the other email. It is page 7-15 and I think(not having the manual handy) that chapter 7 describes the different exceptions including the DTLB Error. In fault.c you can check if both store and invalid is set simultaneously. If it is, clear the store flag and continue as usual. One point is that by changing the in-kernel dcbst implementation userspace is still vulnerable to the problem. Now fixing the exception handler to deal with such boggosity as Joakim proposes is complete - it handles userspace dcbst callers. Yes, ldso uses dcbst and icbi. Currently it works fine because a normal store has been performed before dcbst/icbi is executed. Jocke
how to get busybox shell prompt on console port?
i'm still wrestling with how to get my 8xx-based board's shell prompt to show up on the console port. i've built a simple 2.6.11.7-based kernel and (busybox-based) root filesystem and, fairly quickly, i realized i needed to use the following kernel boot line: Linux/PPC load: rw root=/dev/ram0 console=ttyCPM0,9600 as the boot proceeds, i eventually see: Serial: CPM driver $Revision: 0.01 $ ttyCPM0 at MMIO 0xfa200a80 (irq = 20) is a CPM UART ttyCPM1 at MMIO 0xfa200a00 (irq = 46) is a CPM UART which seems to be a good sign. however, after all the standard boot output, i'm left with no shell prompt, and i'm assuming it's just because i haven't correctly started the shell thru /etc/inittab with the correct parameters to have it talk to that console port. what would be the correct invocation of /bin/sh in /etc/inittab to reflect my serial/console port setup above? thanks. rday
how to get busybox shell prompt on console port?
I use this line in /etc/inittab (assuming you've built busybox to include sh): ttyCPM0::respawn:-/bin/sh Robert P. J. Day wrote: i'm still wrestling with how to get my 8xx-based board's shell prompt to show up on the console port. i've built a simple 2.6.11.7-based kernel and (busybox-based) root filesystem and, fairly quickly, i realized i needed to use the following kernel boot line: Linux/PPC load: rw root=/dev/ram0 console=ttyCPM0,9600 as the boot proceeds, i eventually see: Serial: CPM driver $Revision: 0.01 $ ttyCPM0 at MMIO 0xfa200a80 (irq = 20) is a CPM UART ttyCPM1 at MMIO 0xfa200a00 (irq = 46) is a CPM UART which seems to be a good sign. however, after all the standard boot output, i'm left with no shell prompt, and i'm assuming it's just because i haven't correctly started the shell thru /etc/inittab with the correct parameters to have it talk to that console port. what would be the correct invocation of /bin/sh in /etc/inittab to reflect my serial/console port setup above? thanks. rday ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
cross-compiling under cygwin?
In message 91B22F93A880FA48879475E134D6F0BEB9C02A at CA1EXCLV02.adcorp.kla-tencor.com you wrote: Yes you can run NFS on Windows. The systems we ship inside our equipment have a Win2k Server host and the embedded boards hang off of And this really supports things like special files, user and group id's, permissions including set-uid and hardlinks and all that? 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 Hello! I'm from outer space, and I've made myself look like a signa- ture. While you are reading this, I'm having sex with your eyes. I know it feels good to you, because you're smiling. I'm very horny, so send me to someone else when you've had enough. Thanks! Sincerely, A Stranger in a Strange Land
how to get busybox shell prompt on console port?
On Sun, 10 Apr 2005, Kylo Ginsberg wrote: I use this line in /etc/inittab (assuming you've built busybox to include sh): ttyCPM0::respawn:-/bin/sh (first, a caveat: even though this is the 2.6 kernel, i'm still using devfs for historical reasons. that will change shortly but may be part of my problems.) i'm pretty sure i tried that combo, and several others like it, and i finally had success with the following entry in /etc/inittab: ::respawn:/bin/sh /dev/console /dev/console 2 /dev/console yes, it's disgusting but it works. once i got a prompt, i noticed that these are the contents of /dev: crw---1 root root 204, 46 Dec 31 1969 NULL0 crw---1 root root 204, 47 Dec 31 1969 NULL1 crw---1 root root 5, 1 Oct 2 08:56 console crw-rw-rw-1 root root 1, 7 Dec 31 1969 full drwxr-xr-x1 root root0 Dec 31 1969 input crw-r-1 root root 1, 2 Dec 31 1969 kmem crw-r--r--1 root root 1, 11 Dec 31 1969 kmsg drwxr-xr-x1 root root0 Dec 31 1969 loop crw-r-1 root root 1, 1 Dec 31 1969 mem drwxr-xr-x1 root root0 Dec 31 1969 misc crw-rw-rw-1 root root 1, 3 Dec 31 1969 null crw-r-1 root root 1, 4 Dec 31 1969 port crw-rw-rw-1 root root 5, 2 Dec 31 1969 ptmx drwxr-xr-x1 root root0 Dec 31 1969 pts drwxr-xr-x1 root root0 Dec 31 1969 pty crw-r--r--1 root root 1, 8 Dec 31 1969 random drwxr-xr-x1 root root0 Dec 31 1969 rd lr-xr-xr-x1 root root4 Sep 25 1969 root - rd/0 drwxr-xr-x1 root root0 Dec 31 1969 shm crw-rw-rw-1 root root 5, 0 Dec 31 1969 tty crw-r--r--1 root root 1, 9 Dec 31 1969 urandom crw-rw-rw-1 root root 1, 5 Dec 31 1969 zero in other words, no /dev/ttyCPM0 which may be why that first solution never worked (i'm still fuzzy on support for the serial/console ports so i'm reading up on that now.) but given that i have a /dev/console, i'll stick with that for now until i have a better fix. and what's the two NULL entries up there? those are new to me. rday
how to get busybox shell prompt on console port?
An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050410/68048509/attachment.htm
how to get busybox shell prompt on console port?
On Sun, 10 Apr 2005, Kylo Ginsberg wrote: Fwiw, I explicitly created the CPM devices; note that the major/minor match those of your NULL nodes.? I'm running 2.6.11.? I'm fuzzy re if/how these devices should be automagically created by the kernel. mknod ttyCPM0 c 204 46 mknod ttyCPM1 c 204 47 chmod 660 ttyCPM* ... crw---1 root root 204, 46 Dec 31 1969 NULL0 crw---1 root root 204, 47 Dec 31 1969 NULL1 well, since i'm using devfs, i'm assuming that's what i get by default. ok, that clears up some of the confusion. thanks. rday
