[uClinux-dev] MCF5275EVB & UC Linux

[Mike Cruse]

Sorry forgot to attach the fec.c file.

Is it bad karma for attach files on mail destined for the list?

Hope not.

As a reminder this version of fec.c detects both PHY's but little more
than pinging works on eth1.

Mike Cruse
Definium Technologies Inc

On Mon, 2007-01-15 at 16:54 +1000, Greg Ungerer wrote:
> Hi Mike,
> 
> Mike Cruse wrote:
> > I am doing some work with the 5274 (5275 without crypto).
> > 
> > I have the 2.6 kernel up and running reasonably well.
> 
> Which version 2.6 kernel?
> 
> 
> > I found the config process quite fragile in that while I essentially
> > could build and run out of the box, once I started to make kernel or
> > userland config changes I started to get these messages on boot
> > 
> > Warning: unable to open an initial console.
> > Kernel panic - not syncing: Attempted to kill init!
> 
> I have used this configuration system for years, and it is
> in no way fragile. It does exactly what you tell it to.
> 
> 
> > I am no stranger to Linux and understand some of the things that cause
> > these problems. However I did not understand why turning on ext3,
> > enabling the second FEC and building an extra userland program would
> > cause this to happen. 
> 
> It is possibly a bug.
> 
> But I had no problems enabling those options and still loading
> and running on the M5275EVB board (I used uClinux-dist-test-20070108,
> with 2.6.19-uc1 kernel).
> 
> If you post your full kernel boot trace and kernel configuration
> we might be able to help.
> 
> The most common cause of this type of problem is the romfs generation,
> double check that the device nodes are being created correctly in
> the romfs.
> 
> 
> > Once the problem occurs I have to blow away the source tree and start
> > again as I can't seem to reverse the problem. 
> > 
> > Any clues on this?
> > 
> > Serial ports seem to work well. At least the console does.
> > Haven't used USB or QSPI.
> > 
> > Ethernet seems flakey. Especially when trying to use the second FEC.
> > That code just does not seem complete and PHY detection just would not
> > work without changes.
> > 
> > Beyond getting both PHY's going things were still broken. eth0 would
> > work most of the time but while you could ping a configured eth1, a TCP
> > connection could not be established. Inbound or outbound. 
> 
> I just tried with 2.6.19-uc1 and I could telnet into and out of
> eth0 on the M5275EVB with no problems at all.
> 
> 
> > Using Wireshark it appeared that received packets were just ignored.
> > 
> > I could use some help here. Has anybody gotten both FEC's up and running
> > on the 5274/5? If so how? I am using National DP83848 PHY's.
> 
> 2.6.19-uc1 is not detecting the PHY on eth1, so there does look to be
> a problem there. I can't get any data on eth1 either. I'll look into
> that when I get a minute.
> 
> 
> > That is about as much as I have played with so far.
> > 
> > My setup is as follows:
> > 
> > Toolchain:  m68k-uclinux-tools-20060615
> > uClinux:    uClinux-dist-20060803
> > Bootloader: colilo
> > 
> > On the subject of bootloaders... All the bootloader links on uclinux.org
> > are broken. It does seem that uboot is the way to go anyway but it seems
> > many people have problems compiling it. 
> > 
> > Can someone tell me what toolchain to use to compile uboot?
> > 
> > Thanks for any help in advance!
> 
> Regards
> Greg
> 
> 
> ------------------------------------------------------------------------
> Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg at snapgear.com
> SnapGear -- a Secure Computing Company      PHONE:       +61 7 3435 2888
> 825 Stanley St,                             FAX:         +61 7 3891 3630
> Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com
> _______________________________________________
> uClinux-dev mailing list
> uClinux-dev at uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev at uclinux.org
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fec.c
Type: text/x-csrc
Size: 69874 bytes
Desc: not available
Url : http://mailman.uclinux.org/pipermail/uclinux-dev/attachments/20070115/6b4fef07/fec.bin