Forums

problem with PowerPC 8260

Started by ed71 March 24, 2008
hello all
 I am having this strange problem with powerpc 8260. we have a custom made
board with a powerpc 8260 processor. we are ruuning it on 265MHZ core speed
and 132Mhz CPM speed.
 it has SMC1 as console port and SCC2 as a 10BaseT ethernet port.
 
 we ported Linux 2.4.24 kernel to run on the board. When I put U-boot into
the board everything is OK and I can (tftp) any file I want to the SDRAM
without any problem. But when I start the kernel and try to use FTP or
SFTP to load files to shared memory /dev/shm ,I have the same board that
worked with U-boot fails when the Linux kernel is running...and simply no
error is dislayed and just the kernel crashes and everything stops and we
need to restart...and it seems nothing can cause it to crash other than
FTP through the SCC2 port...
 
 what my question in here is what is the difference between U-boot and
linux kernel in regards to ethernet , and if anyone have an idea what it
about it this problem I would love to hear them.. Thanks

  


> what my question in here is what is the difference between U-boot and > linux kernel in regards to ethernet , and if anyone have an idea what it > about it this problem I would love to hear them.. Thanks
That are two completely different worlds: Linux is an operating system providing a multitasking/multiuser environment. UBoot is a bootloader. So normally you need UBoot to run Linux; - What FTP/SFTP/FTPS server are you using? - How much memory (RAM) is available on the system and how much is the maximum /dev/shm might get? - Do you use a Linux distribution, such as ELDK from Denx? - ... -- Bernhard Schauer schauer_at_cruxy_dot_net
>> what my question in here is what is the difference between U-boot and >> linux kernel in regards to ethernet , and if anyone have an idea what
it
>> about it this problem I would love to hear them.. Thanks > >That are two completely different worlds: Linux is an operating system >providing a multitasking/multiuser environment. UBoot is a bootloader.
So
>normally you need UBoot to run Linux; > >- What FTP/SFTP/FTPS server are you using? >- How much memory (RAM) is available on the system and how much is the >maximum /dev/shm might get? >- Do you use a Linux distribution, such as ELDK from Denx? >- ... > >-- >Bernhard Schauer >schauer_at_cruxy_dot_net >
thanks for the reply ... the board have 128 Mbyte of SDRAM , Iam using 16Mhbyte for RAMDISK file system , then I have a tmpfs set up in dev/shm with about 63Mbyte ... Iam using linux kernel 2.4.24 downloaded from kernel.org and this is configured and compiled to work in our custom board. let us put my question in a different way...tftp in U-boot and Linux are using same hardware so why in U-boot it is working but when kernel is running it is failing ..I found in one website they are talking that tftp in U-boot is polling based but in linux kernel is Interrupt driven ... but I dont have an idea what might be going wrong .. Thanks
> let us put my question in a different way...tftp in U-boot and Linux are > using same hardware so why in U-boot it is working but when kernel is > running it is failing ..I found in one website they are talking that tftp > in U-boot is polling based but in linux kernel is Interrupt driven ... but > I dont have an idea what might be going wrong ..
Ok. Have you verified that your custom board is working? (from the hardware point of view) - is it sending and receiving network messages (single and simple messages)? If Linux's access to the network chip is interrupt driven, do you "see" interrupts in /proc/interrupts and/or with a scope? Btw. It depends on the driver if the access to your network chip is polling or interrupt based. -- Bernhard Schauer schauer_at_cruxy_dot_net
>Ok. Have you verified that your custom board is working? (from the
hardware
>point of view) - is it sending and receiving network messages (single
and
>simple messages)? >If Linux's access to the network chip is interrupt driven, do you "see" >interrupts in /proc/interrupts and/or with a scope? > >Btw. It depends on the driver if the access to your network chip is
polling
>or interrupt based. > >-- >Bernhard Schauer >schauer_at_cruxy_dot_net >
-from hardware point of view I would say the board is Ok. -yes there is network activities like when I ping the port even when the linux is running , it work just fine... it only fails in FTP or SFTP -my netwrok chip doesnt use external INT into the PowerPC , but what I mean bu INT is the internal CPM interrupt that is generated when a buffer discriptor is received , or an error is occured..
> -yes there is network activities like when I ping the port even when the > linux is running , it work just fine... it only fails in FTP or SFTP
Then it seems that also networking performs good - you could try to run a "flood ping" to target.
> -my netwrok chip doesnt use external INT into the PowerPC , but what I > mean bu INT is the internal CPM interrupt that is generated when a buffer > discriptor is received , or an error is occured..
Then some network capability is built into the powerpc and there is only a PHY outside. So you should also see some counting in /proc/interrupts. Now we are again at the point where the FTP software on PPC becomes interesting: which software do you use on PPC for FTP? -- Bernhard Schauer schauer_at_cruxy_dot_net
>> -yes there is network activities like when I ping the port even when
the
>> linux is running , it work just fine... it only fails in FTP or SFTP > >Then it seems that also networking performs good - you could try to run >a "flood ping" to target. > >> -my netwrok chip doesnt use external INT into the PowerPC , but what
I
>> mean bu INT is the internal CPM interrupt that is generated when a
buffer
>> discriptor is received , or an error is occured.. > >Then some network capability is built into the powerpc and there is only
a
>PHY outside. So you should also see some counting in /proc/interrupts. > >Now we are again at the point where the FTP software on PPC becomes >interesting: which software do you use on PPC for FTP? > >-- >Bernhard Schauer >schauer_at_cruxy_dot_net
I tried to flood ping the ethernet port with the command ping -c100 -s8192 -f Ipaddr and it worked just fine no errors then I used sftp root@Ipaddr when I tried to upload the a 1Mbye file failed again..and it doesnt just fail but all linux kernel crash ..and u cant recover unless u restart.. how do I check what type of FTP or SFTP iam running ... I know my file system is from BusyBox I think ... thanks
>
> I tried to flood ping the ethernet port with the command > ping -c100 -s8192 -f Ipaddr > and it worked just fine no errors > then I used sftp root@Ipaddr > when I tried to upload the a 1Mbye file failed again..and it doesnt just > fail but all linux kernel crash ..and u cant recover unless u restart.. > how do I check what type of FTP or SFTP iam running ... > I know my file system is from BusyBox I think ...
I don't think that busybox integrates a SFTP/FTP server. Busybox does not offer even a sftp utility. But at that point we should forward to comp.os.linux.embedded cause that is definitely a linux issue. -- Bernhard Schauer schauer_at_cruxy_dot_net