This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: JFFS2 no space left on device error


Hello,

Thanks for the hints, Andrew.
One more thing I didn't specified, I have taken the mkfs.jffs2 from the CVS.


$ mkfs.jffs2 --version
mkfs.jffs2: revision 1.43

I did as you told me, as follows...

You actually called it JFFS2 in FIS, not jffs2. I'm not sure if this
matters.....


RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0x01000000  0x01000000  0x00020000  0x00000000
appl              0x01020000  0x01020000  0x00030000  0x20007000
jffs2             0x010B0000  0x010B0000  0x00040000  0x20007000
FIS directory     0x013F0000  0x013F0000  0x0000F000  0x00000000
RedBoot config    0x013FF000  0x013FF000  0x00001000  0x00000000

I have changed the name of the jffs FIS image, but if the application can mount the JFFS2 file system, I am not sure it matters. Anyway, I am consistent with the ecos.ecc file.



Err, actually yes it could be. To read the FIS directory is calls into
Redboot. If you have stomped over redboot im supprised the test even
runs. Looking at your FIS directory you have 0x01020000 - 0x10AFFFF
free. Try linking jffs2_1 to run at that address and put Redboot back
at 0x01000000.


Did that, in the fis list command results above, you can see the appl image that contains the binary image of jffs2_1 test (made binary with arm-elf-objcopy ./jffs2_1 ./jffs2_1.bin -O binary and uploaded with RedBoot). I have stared the test with go 0x1020000 commmand in redboot, unfortunatly the same result.

This does not seem right. There should be other entries. Try

jffs2dump -content ./jffs2.img

and see if etc, passwd etc is in the image.



It is not right, indeed...

$ ./jffs2dump --content /tftpboot/jffs2.img
Dirent node at 0x0000000c, totlen 0x0000002b, #pino 1, version 0, #ino 2, nsize 3, name CVS
Inode node at 0x00000038, totlen 0x00000044, #ino 2, version 1, isize 0, csize 0, dsize 0, offset 0
Dirent node at 0x0000007c, totlen 0x0000002d, #pino 1, version 1, #ino 3, nsize 5, name group
Inode node at 0x000000ac, totlen 0x0000013b, #ino 3, version 1, isize 445, csize 247, dsize 445, offset 0
Dirent node at 0x000001e8, totlen 0x0000002e, #pino 1, version 2, #ino 4, nsize 6, name passwd
Inode node at 0x00000218, totlen 0x0000019d, #ino 4, version 1, isize 658, csize 345, dsize 658, offset 0
Dirent node at 0x000003b8, totlen 0x0000002f, #pino 2, version 3, #ino 5, nsize 7, name Entries
Inode node at 0x000003e8, totlen 0x00000086, #ino 5, version 1, isize 85, csize 66, dsize 85, offset 0
Dirent node at 0x00000470, totlen 0x00000032, #pino 2, version 4, #ino 6, nsize 10, name Repository
Inode node at 0x000004a4, totlen 0x00000075, #ino 6, version 1, isize 49, csize 49, dsize 49, offset 0
Dirent node at 0x0000051c, totlen 0x0000002c, #pino 2, version 5, #ino 7, nsize 4, name Root
Inode node at 0x00000548, totlen 0x00000073, #ino 7, version 1, isize 47, csize 47, dsize 47, offset 0


Thanks for your patience,
Edgar

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]