* RE: [ECOS] jffs2_1 test case error
@ 2006-10-26 12:56 Chris Zimman
2008-03-26 15:38 ` Jürgen Lambrecht
0 siblings, 1 reply; 9+ messages in thread
From: Chris Zimman @ 2006-10-26 12:56 UTC (permalink / raw)
To: Andrew Lunn, Srinivas rao; +Cc: ecos
Just for what it's worth -- unless you are using the new eCosCentric V2
flash drivers, make sure you have interrupts disabled during JFFS2
access. eCosCentric did a lot of work on JFFS2 to make it stable under
eCos. I have no idea how well the stock JFFS2 code works.
--Chris
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: 26 October 2006 12:35
To: Srinivas rao
Cc: ecos
Subject: Re: [ECOS] jffs2_1 test case error
On Thu, Oct 26, 2006 at 11:33:41AM +0100, Srinivas rao wrote:
> Hi All,
>
> Iam running jffs2 test cases on my board. After
> reading the directories getting error like below.
> Pls give me the solution.
Sorry, but we don't give solutions. We try to help you find the
solution to your problem.
>
> <INFO>: reading directory /
> <INFO>: entry . [mode 016f0001 ino
> 00000001 nlink 1 size 0]
> <INFO>: entry .. [mode 016f0001 ino
> 00000001 nlink 1 size 0]
> <INFO>: entry etc [mode 017f0001 ino
> 00000004 nlink 1 size 0]
> <INFO>: entry dev<FAIL>: stat() returned -1
> No such entity
>
> <INFO>: entry bin [mode 017f0001 ino
> 00000002 nlink 1 size 0]
> <INFO>: entry lib [mode 017f0001 ino
> 00000005 nlink 1 size 0]
> <INFO>: entry mnt [mode 017f0001 ino
> 00000006 nlink 1 size 0]
> <INFO>: entry var [mode 017f0001 ino
> 000000f6 nlink 1 size 0]
> <INFO>: entry tmp [mode 017f0001 ino
> 000000fb nlink 1 size 0]
> <INFO>: entry sbin [mode 017f0001 ino
> 00000007 nlink 1 size 0]
> <INFO>: create file /foo size 202
> <5>Write of 68 bytes at 0x003e3144 failed. returned
> -5, retlen 68
Well if you look in packages/error/current/include/codes.h you will
find that 5 is EIO. So you probably need to single step this write
call and find out where and why it returns EIO.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ECOS] jffs2_1 test case error
2006-10-26 12:56 [ECOS] jffs2_1 test case error Chris Zimman
@ 2008-03-26 15:38 ` Jürgen Lambrecht
2008-03-26 15:51 ` Chris Zimman
2008-03-27 9:04 ` Jürgen Lambrecht
0 siblings, 2 replies; 9+ messages in thread
From: Jürgen Lambrecht @ 2008-03-26 15:38 UTC (permalink / raw)
To: Chris Zimman; +Cc: Andrew Lunn, Srinivas rao, ecos
Chris Zimman wrote:
>Just for what it's worth -- unless you are using the new eCosCentric V2
>flash drivers, make sure you have interrupts disabled during JFFS2
>
>
JFFS2 accesses take so long that I cannot allow to disable interrupts
>access. eCosCentric did a lot of work on JFFS2 to make it stable under
>eCos. I have no idea how well the stock JFFS2 code works.
>
>
Would it be a good idea to use the flash_v2 branch?
I don't know if all eCosCentric code is already commited there?
Kind regards,
Jürgen
>--Chris
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: [ECOS] jffs2_1 test case error
2008-03-26 15:38 ` Jürgen Lambrecht
@ 2008-03-26 15:51 ` Chris Zimman
2008-03-27 9:04 ` Jürgen Lambrecht
1 sibling, 0 replies; 9+ messages in thread
From: Chris Zimman @ 2008-03-26 15:51 UTC (permalink / raw)
To: Jürgen Lambrecht; +Cc: ecos
> JFFS2 accesses take so long that I cannot allow to disable interrupts
If you're using V1 flash drivers, you're out of luck. They are not interrupt
safe and you will crash at some point.
> Would it be a good idea to use the flash_v2 branch?
> I don't know if all eCosCentric code is already commited there?
I don't know if it's in there or not.
--Chris
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ECOS] jffs2_1 test case error
2008-03-26 15:38 ` Jürgen Lambrecht
2008-03-26 15:51 ` Chris Zimman
@ 2008-03-27 9:04 ` Jürgen Lambrecht
2008-03-27 9:58 ` Chris Zimman
1 sibling, 1 reply; 9+ messages in thread
From: Jürgen Lambrecht @ 2008-03-27 9:04 UTC (permalink / raw)
To: Jürgen Lambrecht; +Cc: Chris Zimman, Andrew Lunn, Srinivas rao, ecos
Jürgen Lambrecht wrote:
> Chris Zimman wrote:
>
>> Just for what it's worth -- unless you are using the new eCosCentric V2
>> flash drivers, make sure you have interrupts disabled during JFFS2
>
The manual states it is only necessary to disable interrupts during
flash accesses if your code also resides in flash (ROM image)
(http://ecos.sourceware.org/docs-latest/ref/ecos-flash-library.html).
Jürgen
>>
> JFFS2 accesses take so long that I cannot allow to disable interrupts
>
>> access. eCosCentric did a lot of work on JFFS2 to make it stable under
>> eCos. I have no idea how well the stock JFFS2 code works.
>>
>>
> Would it be a good idea to use the flash_v2 branch?
> I don't know if all eCosCentric code is already commited there?
> Kind regards,
> Jürgen
>
>> --Chris
>>
>>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 9+ messages in thread
* [ECOS] jffs2_1 test case error
@ 2006-10-26 10:33 Srinivas rao
2006-10-26 11:34 ` Andrew Lunn
0 siblings, 1 reply; 9+ messages in thread
From: Srinivas rao @ 2006-10-26 10:33 UTC (permalink / raw)
To: ecos
Hi All,
Iam running jffs2 test cases on my board. After
reading the directories getting error like below.
Pls give me the solution.
<INFO>: reading directory /
<INFO>: entry . [mode 016f0001 ino
00000001 nlink 1 size 0]
<INFO>: entry .. [mode 016f0001 ino
00000001 nlink 1 size 0]
<INFO>: entry etc [mode 017f0001 ino
00000004 nlink 1 size 0]
<INFO>: entry dev<FAIL>: stat() returned -1
No such entity
<INFO>: entry bin [mode 017f0001 ino
00000002 nlink 1 size 0]
<INFO>: entry lib [mode 017f0001 ino
00000005 nlink 1 size 0]
<INFO>: entry mnt [mode 017f0001 ino
00000006 nlink 1 size 0]
<INFO>: entry var [mode 017f0001 ino
000000f6 nlink 1 size 0]
<INFO>: entry tmp [mode 017f0001 ino
000000fb nlink 1 size 0]
<INFO>: entry sbin [mode 017f0001 ino
00000007 nlink 1 size 0]
<INFO>: create file /foo size 202
<5>Write of 68 bytes at 0x003e3144 failed. returned
-5, retlen 68
<5>Write of 68 bytes at 0x003e3188 failed. returned
-5, retlen 68
<FAIL>: open() returned -1 I/O error
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
Thanks & Regards
Srinivas rao
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ECOS] jffs2_1 test case error
2006-10-26 10:33 Srinivas rao
@ 2006-10-26 11:34 ` Andrew Lunn
0 siblings, 0 replies; 9+ messages in thread
From: Andrew Lunn @ 2006-10-26 11:34 UTC (permalink / raw)
To: Srinivas rao; +Cc: ecos
On Thu, Oct 26, 2006 at 11:33:41AM +0100, Srinivas rao wrote:
> Hi All,
>
> Iam running jffs2 test cases on my board. After
> reading the directories getting error like below.
> Pls give me the solution.
Sorry, but we don't give solutions. We try to help you find the
solution to your problem.
>
> <INFO>: reading directory /
> <INFO>: entry . [mode 016f0001 ino
> 00000001 nlink 1 size 0]
> <INFO>: entry .. [mode 016f0001 ino
> 00000001 nlink 1 size 0]
> <INFO>: entry etc [mode 017f0001 ino
> 00000004 nlink 1 size 0]
> <INFO>: entry dev<FAIL>: stat() returned -1
> No such entity
>
> <INFO>: entry bin [mode 017f0001 ino
> 00000002 nlink 1 size 0]
> <INFO>: entry lib [mode 017f0001 ino
> 00000005 nlink 1 size 0]
> <INFO>: entry mnt [mode 017f0001 ino
> 00000006 nlink 1 size 0]
> <INFO>: entry var [mode 017f0001 ino
> 000000f6 nlink 1 size 0]
> <INFO>: entry tmp [mode 017f0001 ino
> 000000fb nlink 1 size 0]
> <INFO>: entry sbin [mode 017f0001 ino
> 00000007 nlink 1 size 0]
> <INFO>: create file /foo size 202
> <5>Write of 68 bytes at 0x003e3144 failed. returned
> -5, retlen 68
Well if you look in packages/error/current/include/codes.h you will
find that 5 is EIO. So you probably need to single step this write
call and find out where and why it returns EIO.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-03-28 15:24 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-26 12:56 [ECOS] jffs2_1 test case error Chris Zimman
2008-03-26 15:38 ` Jürgen Lambrecht
2008-03-26 15:51 ` Chris Zimman
2008-03-27 9:04 ` Jürgen Lambrecht
2008-03-27 9:58 ` Chris Zimman
2008-03-28 15:24 ` Jürgen Lambrecht
2008-03-29 8:35 ` Chris Zimman
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 10:33 Srinivas rao
2006-10-26 11:34 ` Andrew Lunn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).