OpenWrt Forum Archive

Topic: flash image layout and firmware upgrade file

The content of this topic has been archived on 3 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I'm working on a new board which I have running OpenWrt. However I'm looking for a clean layout of how the flash partition is best set and which FS best to use.
Here is what I have at the moment:

dev:    size   erasesize  name
mtd0: 00004200 00000420 "bootstrap"
mtd1: 00004200 00000420 "uboot_env"
mtd2: 00039c00 00000420 "loader"
mtd3: 0018c000 00000420 "linux"
mtd4: 00318000 00000420 "rootfs"
mtd5: 0035a000 00000420 "data"

I can still change my partitions and my flash mapping. The only part I would not like to move is my bootstrap (which loads my loader (u-boot)).

At the moment my system runs on JFFS2 FS. I have a separate kernel binary and a separate rootfs binary.

I'm also looking for a nice an easy way to make a one file update file. Is there an existing mechanism in OpenWrt for this and how would I need to generate my image file for it?

It would be great if someone can let me know what the most straight forward partitioning, spi data flash filesystem and image genaration would be.
I think it can be good to have this as a reference for new boards.

Any ideas and hints are welcome.

Regards
Bart

Is there no best practice to setup your flash partitions?
Is there no standard way to produce firmware files with a standard upgrade procedure?
Am I missing something?
Any hint would be welcome.

How to use SQUASHFS_MAGIC so I can create split FS?

Bart

The discussion might have continued from here.