U-boot1.1.4 porting problem on PPC 440GX
In message 20060502225540.GA25045 at gate.ebshome.net Eugene Surovegin wrote: Start with asking your hardware people about such differences. ...and then post to a mailing list (like u-boot-users) where your questions fit. Here they are off topic. 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 Q: Do you know what the death rate around here is? A: One per person.
MPC5200 I2C unstable?
Hi, I'm using a MPC5200 based board (namely TQM5200) and the linuxppc_2_4_devel-2005-10-25-1440 kernel from denx.de. To get the serial ports more stable, I've applied the serial port patch by Achim Machura (can be found in http://marc.theaimsgroup.com/?l=linuxppc-embeddedm=112901824515097w=2). The patch needed small adjustments, but nothing too large -- mostly different line numbers. Also, to get the first I2C interface to work, I've had to change the file drivers/i2c/i2c-tqm5200.c followingly: -#define MPC5xxx_I2C1_ENABLE0 /* Disable */ +#define MPC5xxx_I2C1_ENABLE1 /* Enable */ The code compiles OK, but the I2C bus gets stuck after a short while. Has anyone else experienced something similar? I tried to Google for information but didn't find anything relevant. Maybe I just didn't know the right keywords to search for? Thanks in advance, Kimmo Surakka This message has been scanned by F-Secure Anti-Virus ### OXFORD INSTRUMENTS http://www.oxford-instruments.com/ ### Unless stated above to be non-confidential, this E-mail and any attachments are private and confidential and are for the addressee only and may not be used, copied or disclosed save to the addressee. If you have received this E-mail in error please notify us upon receipt and delete it from your records. Internet communications are not secure and Oxford Instruments is not responsible for their abuse by third parties nor for any alteration or corruption in transmission.
Impossible to open the root console with 2.6.15
Hi there, I am trying to use ELDK 4.0 on my TQM860L board. I have compiled the included 2.6.15 kernel with reasonable options, but when I try to boot it, I do not get the prompt after the message Uncompressing Kernel Image ... OK Actually, I know that the system is not hanging because 1) I see there is network traffic between the board and the NFS server 2) There are messages written in /var/log/messages, and I see that the initialization is completed (even my /etc/rc.local has been executed) So I suspect that the problem comes from reading/writing on the console. As my /etc/inittab has the line ... 3:2345:respawn:/sbin/mingetty --noclear console ... I have put a wrapper around the binary mingetty and I have checked that indeed it is called... only that I do not see anything on the screen. I am pretty sure that this problem is related to the kernel because if I boot on a 2.4 kernel with the same root filesystem everything works fine. With the 2.4 kernel I had the following messages in /var/log/messages . Jan 22 12:16:34 tqm kernel: ttyS0 at 0x0280 is on SMC1 using BRG1 Jan 22 12:16:34 tqm kernel: ttyS1 at 0x0380 is on SMC2 using BRG2 . and with the 2.6 .. Jan 26 20:25:26 tqm kernel: ttyCPM0 at MMIO 0xfff00a80 (irq = 20) is a CPM UART Jan 26 20:25:26 tqm kernel: ttyCPM1 at MMIO 0xfff00a90 (irq = 19) is a CPM UART .. I have tried to create these devices with the following characteristics: .. crw-rw 1 root root 204, 46 mai 3 14:43 dev/ttyCPM0 crw-rw 1 root root 204, 47 mai 3 14:43 dev/ttyCPM1 .. but to no avail. I have seen that there are many new options related to serial lines in the new kernel, so I guess that I am doing something wrong. Thanks in advance for any hint. Jean-Marie Teuler : Jean-Marie Teuler : : : Laboratoire de Chimie Physique : T?l?phone (33) (1) 69 15 42 05 : : Universit? de Paris-sud: T?l?copie (33) (1) 69 15 61 88 : : B?timent 349 : M?l teuler at lcp.u-psud.fr : : 91 405 Orsay Cedex : Web http://www.lcp.u-psud.fr :
MPC5200 I2C unstable?
As far as I know there are hardware problems on the MPC5200 I2C interface. They should be solved in the revision B Arno Hi, I'm using a MPC5200 based board (namely TQM5200) and the linuxppc_2_4_devel-2005-10-25-1440 kernel from denx.de. To get the serial ports more stable, I've applied the serial port patch by Achim Machura (can be found in http://marc.theaimsgroup.com/?l=linuxppc-embeddedm=112901824515097w=2). The patch needed small adjustments, but nothing too large -- mostly different line numbers. Also, to get the first I2C interface to work, I've had to change the file drivers/i2c/i2c-tqm5200.c followingly: -#define MPC5xxx_I2C1_ENABLE0 /* Disable */ +#define MPC5xxx_I2C1_ENABLE1 /* Enable */ The code compiles OK, but the I2C bus gets stuck after a short while. Has anyone else experienced something similar? I tried to Google for information but didn't find anything relevant. Maybe I just didn't know the right keywords to search for? Thanks in advance, Kimmo Surakka This message has been scanned by F-Secure Anti-Virus ### OXFORD INSTRUMENTS http://www.oxford-instruments.com/ ### Unless stated above to be non-confidential, this E-mail and any attachments are private and confidential and are for the addressee only and may not be used, copied or disclosed save to the addressee. If you have received this E-mail in error please notify us upon receipt and delete it from your records. Internet communications are not secure and Oxford Instruments is not responsible for their abuse by third parties nor for any alteration or corruption in transmission. ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
kernel debugging
Hello. This is more a general question to see what others do out here. I am begining to get sick of printk debugging. I work on two different PPC boards. An 860 and 8260. I want to get some feedback on the best kernel debugger to use. I have been looking at three. 1. kgdb 2. kdb 3. UML I am leaning towards kgdb, but before I jump in I thought I'd put this out to the best group I could think of linuxppc. Because I am sure most of you are using something! :) Thanks. -stv
Performance improvement Montavista 3.0 MPC8260 by D-cache enable
I want to confirm if the Montavista linux version 3.0 for the MPC8260 has the data cache working. I work on an SDH unit that uses 2 channels and we are about to recieve a shipment of new harware that has to support 4 serial optical channels. I need to confirm if the version of linux we are using has the data chache enabled as I am about to spend a lot of time on the data cache. Thank you, Best Regards, Om Vadlapatla __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
kernel debugging
This is more a general question to see what others do out here. I am begining to get sick of printk debugging. I work on two different PPC boards. An 860 and 8260. I want to get some feedback on the best kernel debugger to use. I have been looking at three. 1. kgdb 2. kdb 3. UML I am leaning towards kgdb, but before I jump in I thought I'd put this out to the best group I could think of linuxppc. Because I am sure most of you are using something! :) Hey Steve, You've missed the most important one; a hardware debugger. I believe most people using PPC use a BDI2000 from Abatron. They're about $3k. I recently received one, but haven't had time to work on my PPC stuff, so can't comment further. I'm sure everyone else on the list will help with comments. Note that if you use a bunch of different PPC cores, you need to add $1k per core for the firmware uploads to the BDI2000. So if you are working with say AMCC 440, Freescale e300/G2, e500, etc you'll need a firmware image for each due to the debug core differences (I guess). The US distributor for the BDI2000 is Ultimate Solutions, www.ultsol.com. Cheers Dave
Impossible to open the root console with 2.6.15
Jean-Marie Teuler wrote: Hi there, I am trying to use ELDK 4.0 on my TQM860L board. I have compiled the included 2.6.15 kernel with reasonable options, but when I try to boot it, I do not get the prompt after the message Uncompressing Kernel Image ... OK It could be a FAQ: http://www.denx.de/wiki/DULG/LinuxHangsAfterUncompressingKernel But in fact, wwe had a similar case recently (no console outputs, but linux running OK) and I am told that the problem was with the virtual terminal option that needed to be disabled: Device Drivers - Character devices - [ ] Virtual Terminal serial drivers- * CPM SCC/SMC serial port support * Support for console CMP SCC/SMC serial port.. -- Best regards, ___ jean-francois simon - themis computer 5, rue irene joliot curie 38330 eybens - france +33 (0)870 448 638 +33 (0)4 76 14 77 85 ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services pr?f?r?s : v?rifiez vos nouveaux mails, lancez vos recherches et suivez l'actualit? en temps r?el. Rendez-vous sur http://fr.yahoo.com/set
Fw: Configuring PCI w/ 44x
Eugene Surovegin ebs at ebshome.net wrote on 05/02/2006 07:49:16 PM: On Tue, May 02, 2006 at 04:58:32PM -0400, Stephen Winiecki wrote: I have a question regarding configuring PCI with 44x. Using 2.6.17-rc3 as a reference, PCI_CONFIG is defined for the 44x defconfigs, and Kconfig is not enabled to reflect/change the setting for 44x. When I update arch/ppc/Kconfig to enable configuring or not configuring PCI with 44x, and then don't configure it, the kernel won't compile: Hmm, you cannot disable PCI for 44x in the current 2.6. It's always enabled. If you changed Konfig to be able to do so, why are you complaining here? It's not enough to just change Konfig, you have to modify Ocotea port as well. Look for example how this is handled for 85xx. Patches are welcome. -- Eugene I was first wondering if for some reason defaulting/forcing PCI to always be configured for 44x was intentional. I was second reporting the fact that if a change is made to not configure PCI for 44x, the kernel will not compile. Steve -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060503/a78f022f/attachment.htm
Fw: Configuring PCI w/ 44x
On Wed, May 03, 2006 at 01:11:26PM -0400, Stephen Winiecki wrote: Eugene Surovegin ebs at ebshome.net wrote on 05/02/2006 07:49:16 PM: On Tue, May 02, 2006 at 04:58:32PM -0400, Stephen Winiecki wrote: I have a question regarding configuring PCI with 44x. Using 2.6.17-rc3 as a reference, PCI_CONFIG is defined for the 44x defconfigs, and Kconfig is not enabled to reflect/change the setting for 44x. When I update arch/ppc/Kconfig to enable configuring or not configuring PCI with 44x, and then don't configure it, the kernel won't compile: Hmm, you cannot disable PCI for 44x in the current 2.6. It's always enabled. If you changed Konfig to be able to do so, why are you complaining here? It's not enough to just change Konfig, you have to modify Ocotea port as well. Look for example how this is handled for 85xx. Patches are welcome. -- Eugene I was first wondering if for some reason defaulting/forcing PCI to always be configured for 44x was intentional. Yes. I think it's quite obvious from the way it's configured in Konfig. I was second reporting the fact that if a change is made to not configure PCI for 44x, the kernel will not compile. Well, I don't follow you here. You made the wrong change and report here that it broke the build. How is this interesting? Your report looked as you discovered a bug, when in fact you broke the build yourself. And again, if disabling PCI is important to you you are welcome to submit patches instead of sending misleading e-mails to this list. -- Eugene
Performance improvement Montavista 3.0 MPC8260 by D-cache enable
How do you suggest I go about enabling the data cache with out running into the machine check exception (0200 exception). I need the data cache as there is lot of data access in the applications we run on our SDH unit. OS Montavista 3.0 Processor MPC8260 Register required to madify: HID0 (bit 17 to be set) = controlword is: HID0 OR 04000 = sets the 17th bit but this gives me the 0200 exception are there any kernel routines I can run to get this to work? Thank you, Sincerely, Om Vadlapatla --- srideep.devireddy at wipro.com wrote: Data chache is not enabled you have to enable it .. srideep -Original Message- From: linuxppc-embedded-bounces+srideep.devireddy=wipro.com at ozlabs.org [mailto:linuxppc-embedded-bounces+srideep.devireddy=wipro.com at ozlabs.org ] On Behalf Of Om Vadlapatla Sent: Wednesday, May 03, 2006 7:57 PM To: linuxppc-embedded at ozlabs.org Subject: Performance improvement Montavista 3.0 MPC8260 by D-cache enable I want to confirm if the Montavista linux version 3.0 for the MPC8260 has the data cache working. I work on an SDH unit that uses 2 channels and we are about to recieve a shipment of new harware that has to support 4 serial optical channels. I need to confirm if the version of linux we are using has the data chache enabled as I am about to spend a lot of time on the data cache. Thank you, Best Regards, Om Vadlapatla __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Sandpoint X3B and 7447 - boot problems
Hi, I'm a new member on this list. I've been trying to get my Sandpoint X3B/mpmc7447 to boot a stock Linux kernel from kernel.org (tried 2.6.14 and 2.6.16). I'm running into a boot issue, I load zImage.elf (using DINK32 v13.1.1) - I get the Linux/PPC load: prompt and then nothing (no more text, and no more serial port response). I been searching through the archives - I did come across one email that mentioned that Motorola(Freescale) started to ship Sandpoint X3B's with serial #'s 6000 with different switch settings (my board has a serial # greater than 6000). I haven't changed any switch settings from the defaults, the comments in arch/ppc/platforms/sandpoint.c seem to make reference to switch settings for the X1/2 board - but nothing about the X3B. In all my searching I have yet to find any reference to what the switch settings for the X3B rev should be for Linux. If anyone has any pointers regarding the switch settings for the X3B - or anything else that might help - I would appreciate any help I can get. Here's my environment: Development Environment: - RedHat Enterprise Linux 4.0 ELDK 4.0 cross devlopment tools (I'm successufully building zImage for sandpoint_defconfig and cross compiling for ppc_74xx-) build steps: export CROSS_COMPILE=ppc_74xx- make ARCH=ppc CROSS_COMPILE=ppc_74xx- sandpoint_defconfig make ARCH=ppc CROSS_COMPILE=ppc_74xx- zImage Board: - Sandpoint X3B , serial # 6000 DINK32 v13.1.1 Altimus (MPMC7447) v1.1 Memory: Map B (CHRP) 128MB at CL3 Thanks, -Simon. -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060503/3d62e5f3/attachment.htm
mpc8270 : i2c support
Hello jfaslist, on Wed, 03 May 2006 14:33:37 jfaslist wrote: But when we try to access i2c devices from under linux 2.6 using the /dev/i2c-0 special file we get an ENODEV on opening that file. I think it is because we lack an adapter driver. If I look in the official kernel, it looks like the adapter driver for the mpc8270 i2c system is ./drivers/i2c/busses/i2c-mpc.c. Is this correct? No. It is for: MODULE_DESCRIPTION (I2C-Bus adapter for MPC107 bridge and MPC824x/85xx/52xx processors); In DENX ELDK there is also a i2c-mpc8260.c, but we couldn't get that to work either. OK, this was the right driver ... but it was tested on a MPC826x Processor. Hmmm I think there are differences in the memory map between MPC826x and MPC827x ... can you try following Hack in include/asm-ppc/cpm_8260.h? -#define PROFF_I2C ((16 * 1024) - 64) +#define PROFF_I2C ((8 * 1024) - 64) [If it solves the problem, we must do this on a better way ;-)] I think i had the same problem with a 2.4er Kernel ... Yes, this is in my queue, but not merged in our official 2.4er Tree ... Maybe you have to set other Portsettings in drivers/i2c/busses/i2c-cpm2.c cpm2_iic_init() ... ? What should I do to be able to access i2c devices using the /dev/i2c-0 file? I feel I need to modify the i2c adapter driver to follow the driver model, but in what ways? Bring up the driver running, and then read: Documentation/i2c/dev-interface. Best regards Heiko
Where to look for CRAMFS
Greetings. I have an embedded board using i.MX21. What I want to know is: how do I tell the kernel where my CRAMFS root file system is? I mean, I put it in a specific memory address, but how does the kernel know where it is?! What happens here is that the kernel looks in some address and don't find the Magic Number CRAMFS stores in its own start address. I have a bad magic number msg because my root fs is somewhere else. Can anyone help me, plz? Thanks in advance. Sauro Engineer Z Tec www.ztec.com.br +55 61 3322-2544
Sandpoint X3B and 7447 - boot problems
On Wed, May 03, 2006 at 01:45:19PM -0500, Simon Smith wrote:
Hi,
I'm a new member on this list. I've been trying to get my Sandpoint
X3B/mpmc7447 to boot a stock Linux kernel from kernel.org (tried 2.6.14 and
2.6.16). I'm running into a boot issue, I load zImage.elf (using DINK32
v13.1.1) - I get the Linux/PPC load: prompt and then nothing (no more
text, and no more serial port response).
I been searching through the archives - I did come across one email that
mentioned that Motorola(Freescale) started to ship Sandpoint X3B's with
serial #'s 6000 with different switch settings (my board has a serial #
greater than 6000). I haven't changed any switch settings from the
defaults, the comments in arch/ppc/platforms/sandpoint.c seem to make
reference to switch settings for the X1/2 board - but nothing about the X3B.
In all my searching I have yet to find any reference to what the switch
settings for the X3B rev should be for Linux.
If anyone has any pointers regarding the switch settings for the X3B - or
anything else that might help - I would appreciate any help I can get.
I just booted last night's kernel.org tree on a sandpoint 7447A X3B
with serial # 6000. I used the default config file, just like you.
The switches on the processor card are set as shown below. The on and
off match the physical markings on the switches as you look at them.
SW1: on,off,off,off,off,off,off,on
SW2: on,off,on,off,off,on,on,on
SW3: on,off,off,off,on,on,on,off
FYI, this is the info printed by dink for you to compare with:
I/O system initialized...
Memory Enabled: [ 128MB at CL=2 ]
Caches Enabled: [ L1I(32K), L1D(32K) ]
Register Inits: [ 32 GPRs, 32 FPRs, 224 SPRs, 32 VPRs ]
## ####
## ####
####
### ## ### ####
#### ## #### ## ##
#### ## #### ##
#### ## #### ## ##
## ## #### ####
((( ( (AltiVec) ) )))
Version : 13.1.1, Metaware Build
Released : INTERIM( build 784 on Dec 16 2003 15:50:00 )
Written by : Motorola CPD/NCSG PowerPC Applications, Austin, TX
System : Sandpoint X3 with Valis (MPMC7447A)
Processor : MPC7447A V1.1 @ 1000 MHz, 100 MHz memory
Memory : Map B (CHRP) 128MB at CL=2
Copyright 1993-2003, by Motorola Inc.
DINK32[MPC7447A] {1}
