Linux on Toradex Colibri PXA320
marek.vasut at gmail.com
Thu Nov 19 07:03:09 EST 2009
Dne Čt 19. listopadu 2009 12:38:26 Daniel Mack napsal(a):
> On Thu, Nov 19, 2009 at 02:33:49PM +0300, Dennis Semakin wrote:
> > 19.11.09, 10:08, "Daniel Mack" <daniel at caiaq.de>:
> > > Hmm, ok, Marek was right - you _do_ face a problem with your MAC
> > > address.
> > >
> > > The kernel logic first tries to use the serial number boot tag which
> > > seems not to be present on your board. If that fails, the MAC is read
> > > back from the Ethernet device. But that MAC is indeed bogus, too.
> > >
> > > For both cases, the problem is related to your bootloader. It should
> > > either provide a valid serial number (which is how the way Toradex
> > > actually wanted it to be) or leave the MAC address stored in the
> > > device (iow, not reset the device before booting into Linux).
> > >
> > > Daniel
> > Hi
> > I changed MAC address with
> > '#ifconfig eth0 down'
> > '#ifconfig eth0 hw ether 00:14:2D:21:CD:FF'
> > '#ifconfig eth0 up'
> > It has not brought desirable results :(
> > May be I did something wrong?
> No, I don't think you did anything wrong. That seems to be a bug in the
> Toradex loader. I never used their bootloader but replaced it with
> U-Boot, so I can't check. However, I was told that Toradex supplies the
> MAC address as system serial number, and the code that went to the
> kernel was successfully tested by people using their loader.
> The only thing I can think of is that they changed that, either on
> purpose or accidentionally. Maybe ask their support channel helps.
> Or replace the loader with U-Boot.
openpxa.sf.net if you want to play around ... there are patches for mainline
uboot for colibri/pxa320 as well as an GPLed IPL. Just be sure you can jtag in
case you screwed up.
Btw. you can't always jtag a binary that's bigger than 128kb (bug in the colibri
loader app), so if you screw up, disable NAND support in uboot, recompile and
the result should be smaller than 128kb ... you can flash that in. Then compile
it with nand support, boot into linux and flash the whole thing again (this time
with nand support).
One more thing -- you can't compile uboot with gcc4.3 and newer -- they have
bugs which cause uboot to hang so use 4.2. This gcc bug causes problems with
NAND too so you can't write into NAND from uboot yet (this is work-in-progress).
More information about the linux-arm