MouettE wrote:It works, wooo ! Thanks a lot I was nowhere near that. Now I can start writing the howto.
Hi MouettE,
Are you the one that wrote the Wiki "Install_Bubba_on_RAID-1_volumes"?
First of all: great job you've done, really helpfull and clear from start to bottom!
I received my B3 last week, and wanted to set it to full raid, just like you did with your B2. However, as you predicted, at the u-boot part I'm stuck with bad CRC. The cat /proc/mtd outputs just like in the starting post from madx. However I have no clue in how to correlate this towards the config file.
Can you point in the right direction?
Madx, did you had any results since your starting post?
EDIT:
Been reading some more info today on the net. And I'm getting somewhere but not completely (yet)
The line in the /etc/fw_env.config should read something like:
Code: Select all
#MTD device name Device offset Env. size Flash sector size
/dev/mtd0 0x0c0000 0x002000 0x010000
Came to this conclusion by:
Code: Select all
root@b3:/mnt/b3# cat /proc/mtd
dev: size erasesize name
mtd0: 000c0000 00010000 "u-boot"
mtd1: 00020000 00010000 "env"
mtd2: 00120000 00010000 "data"
Since then:
Code: Select all
root@b3:/# fw_printenv
Read error on /dev/mtd0: Success
Not completely what the result should be, but no longer the bad CRC.
I'm aware that the env.size and Flash sector size have wrong values. Now the env. size is a value that I should find somewhere in a header file, if I follow Google. Now on the git repository I found b2.h which indead had these parameters, but it's for B2 board obviously. I can't seem to find the same file for b3... Does anyone know where to find that one?