SPI again
Hi I spent a lot of time searching on the net and in this mailing list about a problem I'm having with the SPI but so far the information I found didn't help me too much (I found great suggestions anyway)... I really needs suggestions. I'm working on an Embedded Planet Card (CLX), PPC860 with the kernel 2.4.17 from MontaVista (Hard Hat Pro 2.1). I'm developing a kernel module that include also the SPI, i.e. I have my code to handle the SPI, I'm not using the device driver for the SPI inside the kernel. So I'm using ioremap (I also used ioremap_nocache) to obtain the DPR and register area for the SPI, I allocate the BDs with the help of the m8xx_cpm_dpalloc() function (I've not yet applied the patches to allow the release of the DPR allocated, but at the moment is ok). Is important to know that the SPI management I'm trying to use under Linux, is working under other platforms (for example VxWorks, PsOS, MQX, ecc.), i.e. I'm confident about how to program and use the SPI itself. All seems ok, all the registers and DPR area contains the expected values. The problem is that when I fire the SPI I can see only 1 clock coming out on the SPICLK pin. And no data are sent out to the other SPI pins. Ah, the Hw is ok. Same hardware with different platform/OS is working fine. I tried to compile the kernel with and without the RISC patches for the SPI (beside I'm using SCC1 for ethernet and not using I2C at all) and of course modifying the SPI driver accordingly. No way, I continue to see only 1 clock coming out every time I fire the SPI. So .. anybody has some suggestions about what can be ? Thanks in advance !!! C'ya Steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Frozen ! any idea ?
Hi all ... just my little testimonial about the problem. Well, Linux and the little board were always working. The freeze actually was minicom on the host, used to "speak" to the console !!! I don't know why minicom freeze after 1 minute but sure I will not use it anymore ! So Linux is working well on the board. Now I have to solve the problem to have the kernel running if compiled with the gdbserver option enabled. In order to try to debug something I enabled the KDGB in the kernel (following the instructions on the MontaVista documentation). I recompiled the kernel, no errors .. but when I try to load and start it : [Go 0040] loaded at: 0041 004A81F4 relocated to: 0040 004981F4 board data at: 00495128 00495144 relocated to: 004052C4 004052E0 zimage at: 00405960 004945AA avail ram: 00499000 0100 Linux/PPC load: root=/dev/nfs rw ip=auto Uncompressing Linux...done. Now booting the kernel That's it. Stops. No warning, no errors .. just stops. I'm sure this is not a minicom problem this time ... any ideas ? Many many thanks in advance C'ya Steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Frozen ! any idea ?
At 09:00 AM 12/02/2002 -0500, Steven Blakeslee wrote: >Do you have the watch dog timer enabled? This could be the problem. On the kernel or on the board ? On the board is disabled and on the kernel I didn't find any option about the watchdog. Thanks Steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Frozen ! any idea ?
Hi all ! I have (for me) a curious problem. I have an Embedded Planet RXP Classic credit card (ppc860) loaded with a 2.4.17 kernel (compiled with MontaVista Pro 2.1). I'm able to load correctly the kernel and the filesystem .. all is working just fine, but after 1 minute since the last command issued, the system just freeze. 1 minute without any command issued and the system is gone .. no errors, no messages, no logs, nothing. Just doesn't accept anymore commands .. even the echo on the tty port is gone. About the 1 minute value, I did some tests to figure out the timing and is more or less 1 minute. Up to 30-45 secs. and the system still react, after (50-70 secs) the system freeze. If you continue to issue commands the system doesn't freeze .. but it do it as long as you stop to issue commands. I tried to load also the default kernel image for that board .. same result. It seems a kind of watch dog or timer .. but I don't understand why all is frozen ! Any idea ? Thanks in advance C'ya Steve ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
