Re: [Ltib] Advanced target image generation

[Stuart Hughes]

Hi Andrea,

It's hard to comment without a specific example.  However as you say
rolling up a complete image is quite target specific.

IMHO normally it's best to keep the management of different Flash
partitions independent of each other, this makes replacing one of them
easier.  Of course you can always combine them into a single image, so
long as you pad (as you mention).  I suspect the best thing is to have a
separate script you run outside of LTIB.

BTW: depending on your usage, you may want to check out using jffs2 as
your root filesystem image type rather than the ext2 ramdisk.

Regards, Stuart

On Tue, 2007-04-03 at 11:27 +0200, Andrea Galbusera wrote:
> Hi ltib folks,
> Since I'm getting more and more comfortable in using such a powerful
> tool, I'd like to push it a step forward and make it manage the process
> of generating a full flash image of my system, ready for deploy.
> 
> Just to make a spot of the scene: I have managed to make ltib generate
> the following components of my target system:
> * u-boot in-flash image
> * rootfs ext2 ramdisk image
> * kernel image
> 
> Apart from this basic components my system requires a couple more
> filesystem images (one is empty and one has some files in it) to be
> generated. My goal is to exploit ltib power and make it run the required
> scripts to generate, eventually pad to the correct size and append one
> another all this pieces to build a single flash image ready for chip
> programming. IMO this sounds like an extension of the Target Image
> Generation Options menu but it's also highly platform specific, so I
> have to figure out where to implement this. Could you suggest a
> preferred way to integrate this improved flash image generation
> processes into ltib?
> 
> Regards,
>