make flash-local?

Rod Whitby rod at
Fri Aug 3 17:36:00 CEST 2007

Jim McDonald wrote:
>  Rod Whitby wrote:
>> The reason why a "flash-neo-local" target does not exist is mainly
>> because there is no simple way for the makefile to know the filename of
>> your latest locally-built kernel and rootfs.
>> If there were well-known names (e.g. symlinks put in place by the OE
>> build recipes) for these things, then the Makefile could easily run
>> dfu-util for you.
> Couldn't you get it from a shell command, e.g.
> jgm at desktop:~/openmoko$ ls -t build/tmp/deploy/images/*.jffs2 | head -1
> build/tmp/deploy/images/openmoko-devel-image-fic-gta01-20070803114526.rootfs.jffs2
> jgm at desktop:~/openmoko$ ls -t build/tmp/deploy/images/uImage-2.6.21.*.bin | head -1
> build/tmp/deploy/images/uImage-

I've implemented Jim's suggestion.  Whilst it might not be guaranteed to
choose the correct image, you know that you're flashing something with
this command, so you can always fix any mistake that it makes :-)

'flash-neo-official' and 'flash-neo-local' targets added to MokoMakefile

-- Rod

More information about the openmoko-devel mailing list