MCP750 cannot type anything to bash
I am porting linux-2.4.7 to MCP750 board. It booted fine and got bash prompt. It cannot take anything I type form serial console. So, I put agetty to inittab and it passed the command to bash. Anyone has ideas what's wrong? BTW, the same thing happened to me when porting to i386 system using serial console. Thanks in advance. Ying Lin The follwoing is boot log. Copyright Motorola Inc. 1988 - 2000, All Rights Reserved PPC1 Debugger/Diagnostics Release Version 4.9 - 07/10/00 RM01 COLD Start Local Memory Found =0800 (134217728) MPU Clock Speed =367Mhz BUS Clock Speed =67Mhz Reset Vector Location : ROM Bank B Mezzanine Configuration: Single-MPU Current 60X-Bus Master : MPU0 Idle MPU(s): NONE L2Cache: 1024KB, 147Mhz System Memory: 128MB, ECC Enabled (ECC-Memory Detected) PPC1-Bugnbo Network Booting from: DEC21140, Controller 0, Device 0 Device Name: /pci at 8000/pci1011,9 at e,0:0,0 Loading: zImage.initrd.prep Client IP Address = 150.21.30.210 Server IP Address = 150.21.30.212 Gateway IP Address = 0.0.0.0 Subnet IP Address Mask = 255.255.255.0 Boot File Name = zImage.initrd.prep Argument File Name = Network Boot File load in progress... To abort hit BREAK Bytes Received =2510476, Bytes Loaded =2510476 Bytes/Second =313809, Elapsed Time =8 Second(s) Residual-Data Located at: $07F88000 loaded at: 5400 00017218 relocated to: 0080 00811E18 board data at: 07F88000 07F8EA0C relocated to: 0080B30C 00811D18 zimage at: D400 0009B231 relocated to: 00812000 0089FE31 initrd at: 0009B231 0026838B relocated to: 008A 00A6D15A avail ram: 0040 0080 Linux/PPC load: Uncompressing Linux...done. Now booting the kernel Ramsize from residual data was 0 -- Probing for value Ramsize default to be 32M Total memory = 32MB; using 128kB for hash table (at c01a) Linux version 2.4.7 (root at plymouth) (gcc version 2.95.3 20010315 (release)) #242PReP architecture On node 0 totalpages: 8192 zone(0): 8192 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: time_init: decrementer frequency = 16.666726 MHz Calibrating delay loop... 732.36 BogoMIPS Memory: 28636k available (1004k kernel code, 464k data, 100k 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 PCI: Probing PCI hardware PCI:00:00.0 Resource 4 [ff00-] is unassigned PCI: device 00:06.0 has unknown header type 7f, ignoring. PCI: device 00:07.0 has unknown header type 6f, ignoring. PCI: device 00:0b.0 has unknown header type 7f, ignoring. PCI:00:10.0 Resource 4 [-] is unassigned PCI:00:11.0 Resource 4 [-] is unassigned PCI:00:12.0 Resource 4 [-] is unassigned PCI:00:13.0 Resource 4 [-] is unassigned PCI:00:14.0 Resource 4 [-] is unassigned PCI:00:15.0 Resource 4 [-] is unassigned PCI:00:16.0 Resource 4 [-] is unassigned Memory resource not set for host bridge 0 Setting PCI interrupts for a Mesquite cPCI (MCP750) PCI:00:00.0: Resource 3: 00fc-00ff (f=10f) PCI:00:01.0: Resource 3: fffc- (f=10f) Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Starting kswapd v1.8 pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI edttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A block: queued sectors max/low 18938kB/6312kB, 64 slots per queue RAMDISK driver initialized: 16 RAM disks of 8192K 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 2048 bind 2048) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 1844k freed VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 100k init 4k pmac 4k chrp 4k openfirmware INIT: version 2.78 booting INIT: Entering runlevel: 2Starting Network SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device SIOCADDRT: No such device loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 bash-2.04# (none) login: ls bin dev etc lib lost+found proc sbin tmp usr bash-2.04# (none) login: cat /etc/inittab id:2:initdefault: l2:2:wait:/etc/init.d/rcS 1:2345:respawn:/bin/bash 2:6:wait:/etc/init.d/umountfs
Anybody able to build linux kernel for PPC440?
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020409/65e61ae6/attachment.txt
Anybody able to build linux kernel for PPC440?
Sanjay, At 10:16 PM 4/8/2002, you wrote: Anybody is able build the linux kernel for PPC440 using linux_2_4_devel tree. I tried but i got few unresolved error? I did it last Friday, just after Matt had pushed his changes. There were minor problems during the compilation of do_mounts.c and nfsctl.c - just add missing include of linux/init.h Take care, Eugene Surovegin mailto:ebs at innocent.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
8260 - Spurious interrupt when calling __sti()
I have a custom board that uses an 8260 (rev. A.1 1K22A). We've had for a long time a problem of spurious interrupt. On kernel 2.4.10, at boot up, the following message was written to the console: Unhandled interrupt 0, disabled This message did not appear on kernel 2.4.18 (I don't know why), but in /proc/interrupts, the number at the right of BAD was increasing slowly. When flooding the board through the network, thus generating a lot of interrupts, the number of BAD increased faster (but not as fast as the fenet). [root at 10.20.125.254 /]# cat /proc/interrupts CPU0 4:290 8260 SIU Edge uart 33: 192388 8260 SIU Edge fenet BAD:738 Putting traces in the interrupt handler, it appeared that the interrupt happened in '__sti()' (arch/ppc/kernel/misc.S), just after calling 'mtmsr' to turn on the 'EE' bit. I added a 'sync', between 'ori r3,r3,MSR_EE' and 'mtmsr r3', and it has fixed the problem. My questions are: - Did anybody encountered the same problem on that core? - Did anybody seen something about that in the user's manual and/or the errata? - Is my fix correct, and should it be brought to other calls to 'mtmsr' ? Jean-Denis Boyer, B.Eng., System Architect Mediatrix Telecom Inc. 4229 Garlock Street Sherbrooke (Qu?bec) J1L 2C8 CANADA (819)829-8749 x241 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
vidinfo for Optrex DMF-50840 LCD
All, Has anyone used an Optrex DMF-50840 LCD module on an Embedded Planet MPC823e platform? I am trying to alter the vidinfo_t to make it work but the Optrex spec sheet doesn't outline the wait-between-lines, vert-sync-pulse-width, etc. Any all help is appreciated. I am using HHL 2.2.14. Regards, Michael Pergola Software Engineer Danfoss Air-Conditioning Refrigeration Division 7941 Corporate Blvd. Baltimore, MD 21236 (410) 931-6778 x4259 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
8260 - Spurious interrupt when calling __sti()
Jean-Denis, See comments below. []'s, Scopmailto:scop at vanet.com.br -- We all lie in the gutter, but some of us look up at the stars. -- Oscar Wilde Tuesday, April 09, 2002, 11:53:45 AM, you wrote: JDB I have a custom board that uses an 8260 (rev. A.1 1K22A). Same CPU and rev, other custom board. JDB We've had for a long time a problem of spurious interrupt. JDB On kernel 2.4.10, at boot up, the following message was written to the JDB console: JDB Unhandled interrupt 0, disabled We have this with kernel 2.4.16. JDB This message did not appear on kernel 2.4.18 (I don't know why), Didn't try 2.4.18, yet. JDB but in /proc/interrupts, the number at the right of BAD was increasing JDB slowly. snip JDB Putting traces in the interrupt handler, it appeared that the interrupt JDB happened in '__sti()' (arch/ppc/kernel/misc.S), just after calling 'mtmsr' JDB to turn on the 'EE' bit. JDB I added a 'sync', between 'ori r3,r3,MSR_EE' and 'mtmsr r3', JDB and it has fixed the problem. I'll try that, thanks. JDB My questions are: JDB - Did anybody encountered the same problem on that core? yes. JDB - Did anybody seen something about that in the user's manual and/or the JDB errata? no. JDB - Is my fix correct, and should it be brought to other calls to 'mtmsr' ? I don't have the knowledge to answer that :-( JDB JDB Jean-Denis Boyer, B.Eng., System Architect JDB Mediatrix Telecom Inc. JDB 4229 Garlock Street JDB Sherbrooke (Qu?bec) JDB J1L 2C8 CANADA JDB (819)829-8749 x241 JDB JDB ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
8260 - Spurious interrupt when calling __sti()
Jean-Denis Boyer wrote: On kernel 2.4.10, at boot up, the following message was written to the console: Unhandled interrupt 0, disabled How often did you see these? This message will indicate there was a hardware interrupt posted to the processor but when we read the vector register nothing was pending. Usually race conditions between devices removing the interrupt signal and interrupts being enabled. This message did not appear on kernel 2.4.18 (I don't know why), but in /proc/interrupts, the number at the right of BAD was increasing slowly. I'm not sure the processor specific irq function is properly returning a status to the do_IRQ function. In this case, the spurious counter will be incremented without any message. I do what the comment indicates, return a -1 if no more pending, but I think there is a hole in the code that can erroneously update the counter. It's no big deal, since it functionally works fine. Putting traces in the interrupt handler, it appeared that the interrupt happened in '__sti()' (arch/ppc/kernel/misc.S), just after calling 'mtmsr' to turn on the 'EE' bit. Just think about this for a minute.If there was an interrupt pending, why are you surprised it occurs as soon as you enable interrupts in the MSR? I added a 'sync', between 'ori r3,r3,MSR_EE' and 'mtmsr r3', and it has fixed the problem. A 'sync' or an 'isync'? The mtmsr is supposed to be an instruction synchronizer, so if you required an 'isync' for proper operation then it would be a silicon mask concern. If you really added a 'sync' instruction, this implies to me there is some driver that isn't properly synchronizing its state with a device. An operation to acknowledge the interrupt from the driver is stuck in the pipeline, you enable the interrupts again, the processor is handed an interrupt, the device is acknowledged (from the pipeline), and in the interrupt handler we don't find anything. I would be looking for a driver bug someplace. Thanks. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
question concerning ram filestructure
I'm working with linux 2.4 on an embedded planet ep405. I have been trying to get a ram file structure working but I'm getting a reoccuring error. RAMDISK: Compressed image found at block 0 crc errorFreeing initrd memory: 2201k freed Kernel panic: VFS: Unable to mount root fs on 01:00 0Rebooting in 180 seconds.. I've seen this before on different ports of linux but I have not been able to figure it out. Does anyone have suggestions? Steven Blakeslee ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
IBM walnut, gcc, NIC and recent kernel?
Hi, Lately I find myself playing around with this IBM walnut board and hardhat linux 1.2 with a 2.4.0 based kernel, cross compiling with Montavista's gcc on an intel box. I'd like to use a more recent kernel, but I have some questions. I downloaded 2.4.18 along with the powerpc patch from kernel.org. Then, changed the Makefile to set CROSS_COMPILE = to montavista's compiler, and ARCH = ppc. Then it seems the walnut's network driver turns up missing, so I tried copying over the *405*.[ch] files from the drivers/net directory of the 2.4.0 montavista kernel. (realizing that's probably not going to work straightaway) and hacked the Config.in to try to make it attempt a compile. Well, the assembler complained about some unsupported relocation type in ppc4xx_pic.o, so I suspect I need a newer gcc, assembler, etc. (had nothing to do with network driver, I think) So, it occurs to me that other folks must be using this walnut, and perhaps solved these problems already. So if someone has recommendations about a specific recent kernel that works well with the walnut, and has network support for it, that'd be nice. Also any hints on getting gcc friends to work for intel-ppc cross compiler with a recent kernel would be appreciated. Also, if I'd be better off sticking with hardhat linux (or something else) for an embedded application than trying to use the kernel.org kernels for some reasons, please feel free to educate me about that. Thanks, -- steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
IBM walnut, gcc, NIC and recent kernel?
Hi, Jim Duey sent a HOWTO to the list in Jan 2002 titled Walnut(405GP) Kernel Compiling HowTo. you might want to search the mailing list archives. http://lists.linuxppc.org/index.html#search Actually even I would be interested in knowing if you could get the walnut board working with the kernel from ppc.bkserver.net. It does help to have the latest kernel as it is easy to get support from fellow developers, tends to be more tested and integration with other software components is possible. Regards Amit Stephen Cameron wrote: Hi, Lately I find myself playing around with this IBM walnut board and hardhat linux 1.2 with a 2.4.0 based kernel, cross compiling with Montavista's gcc on an intel box. I'd like to use a more recent kernel, but I have some questions. I downloaded 2.4.18 along with the powerpc patch from kernel.org. Then, changed the Makefile to set CROSS_COMPILE = to montavista's compiler, and ARCH = ppc. Then it seems the walnut's network driver turns up missing, so I tried copying over the *405*.[ch] files from the drivers/net directory of the 2.4.0 montavista kernel. (realizing that's probably not going to work straightaway) and hacked the Config.in to try to make it attempt a compile. Well, the assembler complained about some unsupported relocation type in ppc4xx_pic.o, so I suspect I need a newer gcc, assembler, etc. (had nothing to do with network driver, I think) So, it occurs to me that other folks must be using this walnut, and perhaps solved these problems already. So if someone has recommendations about a specific recent kernel that works well with the walnut, and has network support for it, that'd be nice. Also any hints on getting gcc friends to work for intel-ppc cross compiler with a recent kernel would be appreciated. Also, if I'd be better off sticking with hardhat linux (or something else) for an embedded application than trying to use the kernel.org kernels for some reasons, please feel free to educate me about that. Thanks, -- steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
question concerning ram filestructure
RAMDISK: Compressed image found at block 0 crc errorFreeing initrd memory: 2201k freed Kernel panic: VFS: Unable to mount root fs on 01:00 0Rebooting in 180 seconds.. I've seen this before on different ports of linux but I have not been able to figure it out. Does anyone have suggestions? Steven Blakeslee I just had the same symptom in my port this morning. In my case, the kernel was not picking up the initrd_start or initrd_size from the boot loader. It was a bug in my *_setup.c file. I tossed out the use of r4 and r5 and switched to using parse_bootinfo in platform_init(). That fixed it. It could also be a problem in the boot loader. Greg Griffes ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
question concerning ram filestructure
Steven, I must retract my previous message. After closer scrutiny of your log message, I realized that you are getting a crc error, I assume during the decompression. I did not have that problem. I wonder if it could be a difference in gzip that is used to compress the ram disk on the host and the gunzip version built into your kernel. Just speculating. Greg RAMDISK: Compressed image found at block 0 crc errorFreeing initrd memory: 2201k freed Kernel panic: VFS: Unable to mount root fs on 01:00 0Rebooting in 180 seconds.. I've seen this before on different ports of linux but I have not been able to figure it out. Does anyone have suggestions? Steven Blakeslee I just had the same symptom in my port this morning. In my case, the kernel was not picking up the initrd_start or initrd_size from the boot loader. It was a bug in my *_setup.c file. I tossed out the use of r4 and r5 and switched to using parse_bootinfo in platform_init(). That fixed it. It could also be a problem in the boot loader. Greg Griffes ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
IBM walnut, gcc, NIC and recent kernel?
--- Amit D. Chaudhary amitc at brocade.com wrote: Stephen Cameron wrote: Well, the assembler complained about some unsupported relocation type in ppc4xx_pic.o, so I suspect I need a newer gcc, assembler, etc. (had nothing to do with network driver, I think) I'd come across similar errors and it turned out that the #defines used in the instruction weren't defined for the processor. For eg, I'd a mtspr SPRN_S, r0 and SPRN_S wasn't defined for the processor I was using. A grep -r on the symbol used in the instruction in include/asm-ppc would help. chyrag. = Chirag Kantharia chyrag at yahoo.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
