tool to check efs image ?

QNX Newsgroups (Archives) qnx.rtos
1

Hi, I’m having the problem that the images I build somehow
seem to be corrupt.
A while ago I built a filesystem image (build file → mkefs → mkrec)
which works fine.
Now when I rebuild it, it seems that the flash driver does not recognise
and mount ist. Using the old version still works.

Is there a tool to verify the image on the host prior to downloading it ?

Thanks,
Stefan

2

Stefan Bittner wrote:

Hi, I’m having the problem that the images I build somehow
seem to be corrupt.
A while ago I built a filesystem image (build file → mkefs → mkrec)
which works fine.
Now when I rebuild it, it seems that the flash driver does not recognise
and mount ist. Using the old version still works.

Is there a tool to verify the image on the host prior to downloading it ?

Thanks,
Stefan
I’ve found it: dumpefs.

But ist seems that mkefs in 6.2.1B produces corrupt images
A dumpefs ouput of the image built prior to upgrading to 6.2.1B:


H[00] L[01] P[00]
.status=FD3E (WRITE|NO_NEXT|NO_SUPER|NO_SPLIT|ALLOC|NO_LAST|SYS|BASIC)
.reserve=FF
.text_offset_hi=00
.text_offset_lo=0000
(text_offset=00000000)
.text_size=0014
unit
.status=FF83 (READY|LOGI|NO_ZERO)
.struct_size=0014
.endian=‘L’
.age=00
.logi=0001
.unit_pow2=0012
.reserve=FFFF
.erase_count=00000000
.boot
…logi_unit=0001 …index=0001

H[01] L[01] P[00]
.status=FD3E (WRITE|NO_NEXT|NO_SUPER|NO_SPLIT|ALLOC|NO_LAST|SYS|BASIC)
.reserve=FF
.text_offset_hi=00
.text_offset_lo=0005
(text_offset=00000014)
.text_size=001C
boot
.status=FFFE (INDEX)
.struct_size=001C
.sig=“QSSL_F3S”
.rev_major=02
.rev_minor=01
.unit_index=0000
.unit_total=0024
.unit_spare=0001
.align_pow2=0002
.xip_pow2=000C
.root
…logi_unit=0001 …index=0002


The same for the image built with 6.2.1B:

H[00] L[FFFF] P[00]
.status=0000 (WRITE|NEXT|SUPER|SPLIT|BAD|NO_LAST|XIP|NO_BASIC)
.super
…logi_unit=4F45 …index=0859
unit
.status=0010 (|LOGI|ZERO)
.struct_size=FF4C
.endian=’?’
.unit_pow2=0000
.reserve=0000
.erase_count=00020001
.boot
…logi_unit=0018 …index=0001

H[01] L[FFFF] P[00]
.status=EE8E (WRITE|NO_NEXT|NO_SUPER|NO_SPLIT|BAD|LAST|DIR|BASIC)
.reserve=B2
.text_offset_hi=6C
.text_offset_lo=0018
(text_offset=01B00060)
.text_size=0003
dirent
.status=0200 (STAT)
.struct_size=0000
.first
…logi_unit=0002 …index=0000
.moves=BA
.namelen=00
.reserve=0073
name=“pþ?”
stat
.status=FE70 (COMP)
.struct_size=0006
.uid=0000000C
.gid=0006FE0C
.mtime=00402CE6 Wed Feb 18 17:16:38 1970
.ctime=00000003 Thu Jan 1 01:00:03 1970
.mode=FFFFFFFC ?rwsrwsr-T

There are some rather strange things here.
It may be a dumpefs problem, but the old image gets mounted on the box
the new one doesn’t.

Regards,
Stefan

3

Stefan Bittner wrote:

But ist seems that mkefs in 6.2.1B produces corrupt images
A dumpefs ouput of the image built prior to upgrading to 6.2.1B:

Which BSP & target?
I have a customer with a suspiciously similar sounding problem,
onthe Solutions Engine 7750R.

4

I think that patch B’s mkefs defaults to FFSv3 - try explicitly
specifying FFSv2?

Stefan Bittner wrote:

Stefan Bittner wrote:

Hi, I’m having the problem that the images I build somehow
seem to be corrupt.
A while ago I built a filesystem image (build file → mkefs → mkrec)
which works fine.
Now when I rebuild it, it seems that the flash driver does not recognise
and mount ist. Using the old version still works.

Is there a tool to verify the image on the host prior to downloading it ?

Thanks,
Stefan

I’ve found it: dumpefs.

But ist seems that mkefs in 6.2.1B produces corrupt images
A dumpefs ouput of the image built prior to upgrading to 6.2.1B:


H[00] L[01] P[00]
.status=FD3E (WRITE|NO_NEXT|NO_SUPER|NO_SPLIT|ALLOC|NO_LAST|SYS|BASIC)
.reserve=FF
.text_offset_hi=00
.text_offset_lo=0000
(text_offset=00000000)
.text_size=0014
unit
.status=FF83 (READY|LOGI|NO_ZERO)
.struct_size=0014
.endian=‘L’
.age=00
.logi=0001
.unit_pow2=0012
.reserve=FFFF
.erase_count=00000000
.boot
…logi_unit=0001 …index=0001

H[01] L[01] P[00]
.status=FD3E (WRITE|NO_NEXT|NO_SUPER|NO_SPLIT|ALLOC|NO_LAST|SYS|BASIC)
.reserve=FF
.text_offset_hi=00
.text_offset_lo=0005
(text_offset=00000014)
.text_size=001C
boot
.status=FFFE (INDEX)
.struct_size=001C
.sig=“QSSL_F3S”
.rev_major=02
.rev_minor=01
.unit_index=0000
.unit_total=0024
.unit_spare=0001
.align_pow2=0002
.xip_pow2=000C
.root
…logi_unit=0001 …index=0002


The same for the image built with 6.2.1B:

H[00] L[FFFF] P[00]
.status=0000 (WRITE|NEXT|SUPER|SPLIT|BAD|NO_LAST|XIP|NO_BASIC)
.super
…logi_unit=4F45 …index=0859
unit
.status=0010 (|LOGI|ZERO)
.struct_size=FF4C
.endian=’?’
.unit_pow2=0000
.reserve=0000
.erase_count=00020001
.boot
…logi_unit=0018 …index=0001

H[01] L[FFFF] P[00]
.status=EE8E (WRITE|NO_NEXT|NO_SUPER|NO_SPLIT|BAD|LAST|DIR|BASIC)
.reserve=B2
.text_offset_hi=6C
.text_offset_lo=0018
(text_offset=01B00060)
.text_size=0003
dirent
.status=0200 (STAT)
.struct_size=0000
.first
…logi_unit=0002 …index=0000
.moves=BA
.namelen=00
.reserve=0073
name=“pþ?”
stat
.status=FE70 (COMP)
.struct_size=0006
.uid=0000000C
.gid=0006FE0C
.mtime=00402CE6 Wed Feb 18 17:16:38 1970
.ctime=00000003 Thu Jan 1 01:00:03 1970
.mode=FFFFFFFC ?rwsrwsr-T



There are some rather strange things here.
It may be a dumpefs problem, but the old image gets mounted on the box
the new one doesn’t.

Regards,
Stefa
n

–
cburgess@qnx.com

5

acellarius@yahoo.com wrote:

Stefan Bittner wrote:

But ist seems that mkefs in 6.2.1B produces corrupt images
A dumpefs ouput of the image built prior to upgrading to 6.2.1B:



Which BSP & target?
I have a customer with a suspiciously similar sounding problem,
onthe Solutions Engine 7750R.
Total5200 , Ill check the hint provided by Colin,

Stefan