Re: Can i access the barebox env from linux

[Alexander Aring <alex.aring@gmail.com>]

On Wed, Mar 26, 2014 at 04:44:30PM +0530, Ashutosh Singh wrote:
> Thanks Alex,
> 
> The script is quite helpful.
> But since i am saving my barebox.env in nand and want to mount, modify
> and write it back to nand.
> Do you have a safer solution so that complete env data won't corrupted.

1. You need to save the bareboxenv as image, the right place would be
   /tmp which is tmpfs and this uses ram for storing data. You need inotify
   support in kernel and I am sure tmpfs also supports inotify. You also need
   the inotify userspace utilities.

2. The image should write via nandwrite from mtd-utils [1]. Look for
   the nandwrite manpage. nandwrite should write the tmp-image from bbenv
   to your nand mtd device.



I know the nandwrite will make a better badblock handling... but if you
set your bbenv size exactly the eraseblock size so it doesn't matter...
because after badblock marking that eraseblock you don't have any bbenv
partition anymore :/

nandwrite uses the mtd api to write and I suppose they do something more
than only badblock handling, ECC calculation.... Nevertheless you should
ever use nandwrite to write images to your nand /dev/*.nand partition.

I don't have any time now to change the script for nandwrite and extract
to /tmp/bbenv/, etc..., sorry. We should do it right and implement a C
solution for that. :-) I don't have time to do that also, maybe at weekend.

I don't have also no nand device here, I need to use the nandsim module.
This will take some time to setup.


Sorry, but try to change the script yourself and then share it with us. I
will take a look and review it.

- Alex

[1] http://git.infradead.org/mtd-utils.git

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox