[Avila] How to write on the "RedBoot config" partition

[David Acker]

Andrea Tassi wrote:
> Hi guys,
> 
> my task is to edit the "RedBoot config" partition from a booted system 
> in the Avila board (GW2348-4) flash memory. For the first thing I unlock 
> the "RedBoot config" partition from the RedBoot shell.
> 
> Performing a "cat /proc/mtd" from the booted system I can see the mtd 
> devices correctly initialized:
> dev:   size          erasesize   name
> ...
> mtd5: 00001000 00020000 "RedBoot config"
> ...
> 
> then I perfom:
> mknod /dev/mtd5 c 90 10
> mknod /dev/mtdblock5 b 31 5
> 
> At this point I can read both devices that point to the "RedBoot config" 
> partition. My problem is that I can't write on /dev/mtd5 or on 
> /dev/mtdblock5 (in this device I can write but the changes are not 
> saved!) nevertheless I'm using a kernel capable to write on RedBoot 
> partitions. I have also tried to apply the following patch to force a 
> read and write access to RedBoot config partition (because the RedBoot 
> config partiton doesen't start and stop on an erase block boundary) with 
> no effects:
Instead, you could try the following:
http://lists.gateworks.com/avila/2006-November/000589.html
http://lists.gateworks.com/avila/2006-November/000592.html


This will set you up with fconfig to the do the reading and writing in a nicer way and redboot patches to setup the 
partitions properly.  This works great for us.  Note, these patches are for the previous bsp's redboot, not the current 
one. I have not checked how well they apply to the current bsp's redboot, but they are pretty simple to manually apply.
-Ack