OSELAS.BSP mini2440

I am stuck on the last process, that of uploading the images via tftp to
the mini2440.

I am quite sure that the tftp server is running correctly on my Ubuntu
10.04LTS host.  However, on running <update -t barebox -d nand> I get:

tftp failed: No such file or directory

I can ping the server from the mini2440, but I can't ping the mini2440 from
the server end.  Is this normal?

Another issue that might surface later, when I can upload files to the
mini2440 is . . . on the top of page 22 it says to:

$ cp platform-mini2440/images/barebox-image /tftpboot/barebox-mini2440

As the barebox image was already loaded via USB (page 20) I wonder if this
should really be:

$ cp platform-mini2440/images/barebox-default-environment
/tftpboot/barebox-mini2440

If not, what is this file for?
 
Dave

tftp failure: There are some tftp servers around expecting the full path
from the target. I'm using dnsmasq acting as tftp server.
Can you see in the logfiles at the server why it fails or what file your
target requests?

The bootloader does only support polling. So, ping-ing your target won't
wake it, to send an answer.

Loading barebox via USB only loads it into the RAM. The next step loading
it again via net is to make it persistent.

"barebox-default-environment" is for convenience only. It contains the
evnironment, barebox should use, and can be stored directly into the flash.
But when you set up your target the very first time, it is not required (it
contains the same info as the default environment). The really
"barebox-image" is needed to be downloaded via net in this step.

Hope it helps.

Juergen,

Thank you for the quick response.  

The issue with <tftpd-hpa> on my platform was traced when doing:

cat /etc/default/tftpd-hpa

It was expecting to find the tftpboot files in /var/lib so I changed
TFTP_DIRECTORY="/tftpboot" and the files uploaded.  That was after a long
search!

Also, on waking this morning I realised that uploading barebox into nand
was necessary, but thanks for correcting my doubt.

Now, for the next problem!

When I set the unit back to NAND and re-power all I get is a white screen
immediately and no communication takes place on minicom. 

The barebox image is 149788
the root.jffs2 image is 4771060
the linuximage is 1600848

I reflashed the images and the same thing happens.

Appreciate your suggestions.

Would you prefer this dialogue takes place on your mailing list?

Regards,
Dave

Did you check your NAND configuration (64 MiB versus non 64 MiB) and build
the coresponding config?

> Would you prefer this dialogue takes place on your mailing list?

Yes, on the mailing list would be easier, as I read this forum only once a
day.

jbe

Continued the discussion at:

http://permalink.gmane.org/gmane.comp.embedded.ptxdist.oselas.community/1

Reporting back:

A useful test has been suggested just after loading barebox into RAM.

mini2440:/ nand_boot_test 0x31000000 0x40000
mini2440:/ go 0x31000000

Hit any key to stop autoboot:

If you got this far you have probably got a good barebox image in RAM.

I re-installed <tftpd> on my Ubuntu 10.04LTS host, which MAY have had
something to do with things now working.  I'll never know!

The support on this issue has been exceptional.

Dave

Hi ,
  Is it possible to load the kernel and the root fs image built by
OSELAS.BSP  via u-boot instead of barebox?

Currently i'am using 
'bootargs console=ttySAC0,115200 init=/linuxrc noinitrd  root=/dev/nfs
rw,tcp nfsroot=192.168.1.3:/fs/qt463 ip=dhcp'
to boot linux 

My question is what parameters I need to pass to bootargs so the kernel
boots and mounts the root filesystem. 

thanks
--amit

Starting at section 2.2.4 in
OSELAS.BSP-Pengutronix-Mini2440-Quickstart.pdf:

<ptxdist setup> from memory just does some initial setup, not sure if you
can change the bootloaders from here.

Then try <ptxdist menuconfig> and tick u-boot.

Here is my NFS commandline for barebox, maybe it gives a few clues:

nfsroot=192.168.1.7:/home/davef/Pengutronix/OSELAS.BSP-Pengutronix-Mini2440-2011
.05.0/platform-mini2440/root,v3,tcp
noinitrd ip=192.168.1.147::192.168.1.254:255.255.255.0::: 
mtdparts=nand:512k(barebox),384k(bareboxenv),2048k(kernel),-(root)
arch_number: 1999

Currently, working with Juergen trying to get this to work.
http://blog.gmane.org/gmane.comp.embedded.ptxdist.oselas.community

Good luck.

fatbrain,

no problem. My BSP creates the kernel and the rootfs, and they do not
depend on any bootloader. So, you can also use u-boot to load and run the
components created by this BSP.

You should adapt your kernel command line. Remove the "init=/linuxrc", as
the kernel tries to run "/bin/init" and it will work with the root fs from
the BSP. And adapt the nfsroot as Dave already stated. Nothing magically.