We are using a PowerPC 8250 board and the BSP we are using is based on the
standard example-BSP for 8260ads.
We are now upgrading from 6.1.0 to 6.2.1B and we plan to use the new flash
filesystem (F3S_VER=3) so I have made the changes according to the document
‘Migrating to the new flash filesystem’
The flash image that is built by the standard example 8260ads BSP is just
8MB in the following way:
2MB config word+boot image
5MB flash file system
1MB Reset code + IPL
= 8MB
On our board we have 16MB flash so I have changed the make_flash_img to
produce a flash image that looks like:
2MB config word+boot image
13MB (new) flash file system
1MB Reset code + IPL
= 16MB
and this works perfectly well under 6.1.0. During boot-up when devf-xxx is
started it creates
/dev/fs0, /dev/fs0p0, /dev/fs0p1 and /dev/fs0p2 where /dev/fs0p1 is the 13MB
flash file system which is auto-mounted at /.
Now in 6.2.1B I build the 16MB flash image in the same way. I have added
‘-tffs3’ to mkefs in make_flash_img to generate a version 3 flash file
system (which seems to be default anyway). The system boots correctly and
the files in the boot image (the files that are present in the build script)
are visible but when the new devf-xxx is started it doesnt seem to find the
13MB flash file system. The only things that come up under /dev is now fs0
and fs0p0 and none of them are mountable.
I tried to erase and format /dev/fs0p0 with
‘flashctl -p/dev/fs0p0 -o2M -l13M -e -f’ and then restart the def-xxx and
that works well but then ofcourse all the files that mkefs had put in the
13MB flash file system are gone.
Are there any special tricks to make the new devf-xxx find the flash file
system when using version 3? Shall the flash image be generated in a
different way? I compared you original make_flash_img from 6.1.0 and 6.2.1B
and they seem to do the same thing!
You must mean 6.2.1B/Supplemental - that’s the one that has FFSv3.
It has shipped with broken mkefs/mkxfs. They silently ignore +bigendian
attribute, making images unusable on PPC and other bigendian targets.
We are using a PowerPC 8250 board and the BSP we are using is based on the
standard example-BSP for 8260ads.
We are now upgrading from 6.1.0 to 6.2.1B and we plan to use the new flash
filesystem (F3S_VER=3) so I have made the changes according to the
document
‘Migrating to the new flash filesystem’
The flash image that is built by the standard example 8260ads BSP is just
8MB in the following way:
2MB config word+boot image
5MB flash file system
1MB Reset code + IPL
= 8MB
On our board we have 16MB flash so I have changed the make_flash_img to
produce a flash image that looks like:
2MB config word+boot image
13MB (new) flash file system
1MB Reset code + IPL
= 16MB
and this works perfectly well under 6.1.0. During boot-up when devf-xxx is
started it creates
/dev/fs0, /dev/fs0p0, /dev/fs0p1 and /dev/fs0p2 where /dev/fs0p1 is the
13MB
flash file system which is auto-mounted at /.
Now in 6.2.1B I build the 16MB flash image in the same way. I have added
‘-tffs3’ to mkefs in make_flash_img to generate a version 3 flash file
system (which seems to be default anyway). The system boots correctly and
the files in the boot image (the files that are present in the build
script)
are visible but when the new devf-xxx is started it doesnt seem to find
the
13MB flash file system. The only things that come up under /dev is now fs0
and fs0p0 and none of them are mountable.
I tried to erase and format /dev/fs0p0 with
‘flashctl -p/dev/fs0p0 -o2M -l13M -e -f’ and then restart the def-xxx and
that works well but then ofcourse all the files that mkefs had put in the
13MB flash file system are gone.
Are there any special tricks to make the new devf-xxx find the flash file
system when using version 3? Shall the flash image be generated in a
different way? I compared you original make_flash_img from 6.1.0 and
6.2.1B
and they seem to do the same thing!
Very nice indeed to hear that mkefs was wrong!!! I thought for a while I was
the only one with this problem meaning that I probably did something wrong
in the image build process.
You must mean 6.2.1B/Supplemental - that’s the one that has FFSv3.
It has shipped with broken mkefs/mkxfs. They silently ignore +bigendian
attribute, making images unusable on PPC and other bigendian targets.
They have fixed mkxfs, talk to your support rep.
– igor
“Mats B” <> mats@singularity.se> > wrote in message
news:bu43n9$b6t$> 1@inn.qnx.com> …
We are using a PowerPC 8250 board and the BSP we are using is based on
the
standard example-BSP for 8260ads.
We are now upgrading from 6.1.0 to 6.2.1B and we plan to use the new
flash
filesystem (F3S_VER=3) so I have made the changes according to the
document
‘Migrating to the new flash filesystem’
The flash image that is built by the standard example 8260ads BSP is
just
8MB in the following way:
2MB config word+boot image
5MB flash file system
1MB Reset code + IPL
= 8MB
On our board we have 16MB flash so I have changed the make_flash_img to
produce a flash image that looks like:
2MB config word+boot image
13MB (new) flash file system
1MB Reset code + IPL
= 16MB
and this works perfectly well under 6.1.0. During boot-up when devf-xxx
is
started it creates
/dev/fs0, /dev/fs0p0, /dev/fs0p1 and /dev/fs0p2 where /dev/fs0p1 is the
13MB
flash file system which is auto-mounted at /.
Now in 6.2.1B I build the 16MB flash image in the same way. I have added
‘-tffs3’ to mkefs in make_flash_img to generate a version 3 flash file
system (which seems to be default anyway). The system boots correctly
and
the files in the boot image (the files that are present in the build
script)
are visible but when the new devf-xxx is started it doesnt seem to find
the
13MB flash file system. The only things that come up under /dev is now
fs0
and fs0p0 and none of them are mountable.
I tried to erase and format /dev/fs0p0 with
‘flashctl -p/dev/fs0p0 -o2M -l13M -e -f’ and then restart the def-xxx
and
that works well but then ofcourse all the files that mkefs had put in
the
13MB flash file system are gone.
Are there any special tricks to make the new devf-xxx find the flash
file
system when using version 3? Shall the flash image be generated in a
different way? I compared you original make_flash_img from 6.1.0 and
6.2.1B
and they seem to do the same thing!
