I'd guess that the file you're trying to flash is a binary dump of the loader. You'll have to recompile blob if you want and elf or srec file.

I've posted a version of BLOB for the LPD7a400 with sources as well as an elf binary. You should be able to flash it with LOLO, but note that it isn't compatible with the Metrowerks Linux kernel.

http://www.buici.com/projects/arm/lpd7a400

What is the LPD7A400 Marc is referring to on his site?

The product code for the card engine seems to be LH7A400-10 for the card engine and the development kit is referred to as SDK-LH7A400-10-6416.

Thanks

There's only one CardEngine with the 7a400, it is called the LH7A400-10
and is included with the SDK. This is probably what he is referring to.

More technically, it may refer to all combinations of hardware supported
by the ARM Linux hardware code 'LPD7A400' (see http://www.arm.linux.org.uk/developer/machines)

btw, Marc's site has moved to http://projects.buici.com/arm/kev7a400/

Does the document about the KEV7A400 compatible with the LDP7A400?:
http://projects.buici.com/arm/kev7a400/

Or should I use this one (which was updated recently and makes references to the kernel 2.6.8 I'd like to use)?
http://projects.buici.com/arm/lpd7a400/

Which one should I use for the lpd7a400, the BLOB or U-BOOT?

I made a attempt at building the BLOB form my LPD7A400. Below is the output after few corrections in the configure script. What worries me (i don't have access to a JTAG for now) is the fact that the resulting wblob.bin has only 13.1KB compared to the one from Sharp's BDK which has approx 80KB. I also can't find instructions on how to create the param file for Sharp's BLOB. Thanks much.


Configuration
------------------------------------------------------------------------
Target board LogicPD LPD7A40x-10 CardEngines
Target CPU lh7a400
C compiler arm-9tdmi-linux-gnu-gcc
C flags -Os -I/usr/src/linux/include -Wall -march=armv4 -mtune=arm9tdmi -gdwarf-2 -mapcs-32 -fno-builtin -nostdinc
Linker flags -static -nostdlib
Objcopy tool arm-9tdmi-linux-gnu-objcopy
Objcopy flags -O binary -R .note -R .comment -S
Clock scaling support no
Memory test support no
Debugging commands support no
LCD support no
MD5 support no
IDE support no
Networking support no
Run-time debug information no

I'd guess that using the LPD-related stuff would be better
if you're using one of our CardEngines. I was able to build
blob to live in flash alongside lolo, and be burned by lolo,
by using the generated elf32-* files (I dont remember
exactly which at the moment - look at the Makefile to see
which is generated to boot from flash and live in flash).

Ok.
Once you got the BLOB in the flash, did you get the param file, the param file and the file system in the flash so linux loads?

In this case my flash would look like the following? :
BOLO 0x00000000 (256KB)
LOLO 0x00040000 (256KB)
BLOB 0x00080000 (256KB)
BLOB param 0x000C0000 (256KB)
Kernel 0x00100000 (1.5MB)
FS...

Is it possible to flash this out without a JTAG? How can I achieve this?
Thanks again.

Actually, I haven't gotten that far, some higher priority
work came up and I haven't had a chance to get back to
it. You can use lolo to burn blob, and I assume that you
can use blob to burn the param file. Your memory map
looks like what I'd expect, though if you will never use
lolo, you could just stick blob at 0x40000 without losing
the safety of having bolo around in case something goes
wrong.