[ECOS] JFFS2 - readme.txt

[ECOS] JFFS2 - readme.txt

[Alok Singh]

Hi,
I'm trying to use jffs2 on my box. Readme.txt under doc says that
minor modifications are necessary to eCos flash drivers(flash.c and
flash_program_buf.c for intel chip) and that these are supplied in
"jffs2/current/src" folder. 

But I was not able to find these files under jffs2/current/src. 


regards,
Alok


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

Re: [ECOS] JFFS2 - readme.txt

[Andrew Lunn]

On Thu, May 31, 2007 at 12:32:19AM +0530, Alok Singh wrote:
> Hi,
> I'm trying to use jffs2 on my box. Readme.txt under doc says that
> minor modifications are necessary to eCos flash drivers(flash.c and
> flash_program_buf.c for intel chip) and that these are supplied in
> "jffs2/current/src" folder. 

That is an old document. Ignore it. The current Intel flash drivers
should work.

       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

RE: [ECOS] JFFS2 - readme.txt

[Alok Singh]

Andrew,
I'm using v2_0 jffs2.  I'm running the test fileio1.c under jffs2/tests
folder.  I'm getting errors in creating the file "foo". Any pointers
here.
Device being mounted is -
 cdl_component CYGDAT_IO_FLASH_BLOCK_DEVICE_NAME_1 {
    # Flavor: data
    user_value "\"/dev/flash1\""
    # value_source user
    # Default value: "\"/dev/flash1\""
};
cdl_option CYGNUM_IO_FLASH_BLOCK_OFFSET_1 {
    # Flavor: data
    user_value 0x000A0000     /* 0xbc0A0000*/
    # value_source user
    # Default value: 0x00100000
};
cdl_option CYGNUM_IO_FLASH_BLOCK_LENGTH_1 {
    # Flavor: data
    user_value 0x800000   /* 8 MB */
    # value_source user
    # Default value: 0x00100000
}
****************************************************

INFO>: reading directory /
<INFO>: entry              . [mode 00016f01 ino 80184530 nlink 1 size 0]
<INFO>: entry             .. [mode 00016f01 ino 80184530 nlink 1 size 0]
<INFO>: create file /foo size 202
<FAIL>: access() returned 286326803
<4>Write error in obliterating obsoleted node at 0x007c0000: 1
<5>Write of %zd bytes at 0x00000044 failed. returned 8126476, retlen %z
d
<5>Write of %zd bytes at 0x0000002b failed. returned 8126544, retlen %z
d


regards,
Alok

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: Thursday, May 31, 2007 12:48 AM
To: Alok Singh
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] JFFS2 - readme.txt

On Thu, May 31, 2007 at 12:32:19AM +0530, Alok Singh wrote:
> Hi,
> I'm trying to use jffs2 on my box. Readme.txt under doc says that
> minor modifications are necessary to eCos flash drivers(flash.c and
> flash_program_buf.c for intel chip) and that these are supplied in
> "jffs2/current/src" folder. 

That is an old document. Ignore it. The current Intel flash drivers
should work.

       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

Re: [ECOS] JFFS2 - readme.txt

[Andrew Lunn]

On Thu, May 31, 2007 at 02:30:27AM +0530, Alok Singh wrote:
> Andrew,
> I'm using v2_0 jffs2.

Old, very old, 4 years and 10 days old. I would suggest you update to
anoncvs.

  I'm running the test fileio1.c under jffs2/tests
> folder.  I'm getting errors in creating the file "foo". Any pointers
> here.

Do you put the test filesystem into the flash? 

   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

RE: [ECOS] JFFS2 - readme.txt

[Alok Singh]

Andrew,
I'll use current CVS version now. The ecos reference manual says that -
No file system needs to be created in advance for JFFS2. A new file
system image will be instantiated if JFFS2 is pointed at an erased Flash
area. Similarly if JFFS2 is pointed at a non-erased Flash area that does
not contain valid JFFS2 markers, it will refuse to mount it to prevent
destruction of data. 
I erased the flash before running the test program.
I think jffs2 file system was created, as seen from the logs-
INFO>: reading directory /
<INFO>: entry              . [mode 00016f01 ino 80184530 nlink 1 size 0]
<INFO>: entry             .. [mode 00016f01 ino 80184530 nlink 1 size 0]

Plz let me know if my understanding is correct or do I need to create a
test file system..

regards,
Alok

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: Thursday, May 31, 2007 2:37 AM
To: Alok Singh
Cc: Andrew Lunn; ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] JFFS2 - readme.txt

On Thu, May 31, 2007 at 02:30:27AM +0530, Alok Singh wrote:
> Andrew,
> I'm using v2_0 jffs2.

Old, very old, 4 years and 10 days old. I would suggest you update to
anoncvs.

  I'm running the test fileio1.c under jffs2/tests
> folder.  I'm getting errors in creating the file "foo". Any pointers
> here.

Do you put the test filesystem into the flash? 

   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

Re: [ECOS] JFFS2 - readme.txt

[Andrew Lunn]

On Thu, May 31, 2007 at 03:11:39AM +0530, Alok Singh wrote:
> Andrew,
> I'll use current CVS version now. The ecos reference manual says that -
> No file system needs to be created in advance for JFFS2. A new file
> system image will be instantiated if JFFS2 is pointed at an erased Flash
> area. Similarly if JFFS2 is pointed at a non-erased Flash area that does
> not contain valid JFFS2 markers, it will refuse to mount it to prevent
> destruction of data. 
> I erased the flash before running the test program.
> I think jffs2 file system was created, as seen from the logs-
> INFO>: reading directory /
> <INFO>: entry              . [mode 00016f01 ino 80184530 nlink 1 size 0]
> <INFO>: entry             .. [mode 00016f01 ino 80184530 nlink 1 size 0]
> 
> Plz let me know if my understanding is correct or do I need to create a
> test file system..

I always use the test image when running the tests. I don't know if it
works without the test image.

      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

[ECOS] routines to dump ARP and Route table in ecos

[Madan Mohan Goud]

Hi all,
	   Could any of you let me know if there are any routines to
print/dump ARP Table and Route Table maintained by FreeBSD stack of
ECOS?

I would like to see the contents of these tables.

Thanks,
Madan

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

RE: [ECOS] routines to dump ARP and Route table in ecos

[Lars Povlsen]

I use the sysctl interface. You can probably find example code in the
SNMP for the standard Mib-II.

---Lars

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Madan Mohan
Goud
Sent: 31. maj 2007 16:29
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] routines to dump ARP and Route table in ecos

Hi all,
	   Could any of you let me know if there are any routines to
print/dump ARP Table and Route Table maintained by FreeBSD stack of
ECOS?

I would like to see the contents of these tables.

Thanks,
Madan

-- 
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

Re: [ECOS] routines to dump ARP and Route table in ecos

[Andrew Lunn]

On Thu, May 31, 2007 at 07:59:19PM +0530, Madan Mohan Goud wrote:
> Hi all,
> 	   Could any of you let me know if there are any routines to
> print/dump ARP Table and Route Table maintained by FreeBSD stack of
> ECOS?

show_network_tables() will give you the routing table. I don't think
there is an equivelent for the ARP table, but you could add one.

      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

RE: [ECOS] routines to dump ARP and Route table in ecos

[Madan Mohan Goud]

Andrew and all,
			I am getting a crash if I am calling the API
show_network_tables. Not sure why this is happening. 

I am invoking the API as show_network_tables(printf);

Thanks,
Madan

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: Thursday, May 31, 2007 8:52 PM
To: Madan Mohan Goud
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] routines to dump ARP and Route table in ecos

On Thu, May 31, 2007 at 07:59:19PM +0530, Madan Mohan Goud wrote:
> Hi all,
> 	   Could any of you let me know if there are any routines to
> print/dump ARP Table and Route Table maintained by FreeBSD stack of
> ECOS?

show_network_tables() will give you the routing table. I don't think
there is an equivelent for the ARP table, but you could add one.

      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

RE: [ECOS] routines to dump ARP and Route table in ecos

[Madan Mohan Goud]

This problem is resolved. The problem was with my code only.

Thanks,
Madan

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Madan Mohan
Goud
Sent: Friday, June 01, 2007 10:42 AM
To: Andrew Lunn
Cc: ecos-discuss@ecos.sourceware.org
Subject: RE: [ECOS] routines to dump ARP and Route table in ecos

Andrew and all,
			I am getting a crash if I am calling the API
show_network_tables. Not sure why this is happening. 

I am invoking the API as show_network_tables(printf);

Thanks,
Madan

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: Thursday, May 31, 2007 8:52 PM
To: Madan Mohan Goud
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] routines to dump ARP and Route table in ecos

On Thu, May 31, 2007 at 07:59:19PM +0530, Madan Mohan Goud wrote:
> Hi all,
> 	   Could any of you let me know if there are any routines to
> print/dump ARP Table and Route Table maintained by FreeBSD stack of
> ECOS?

show_network_tables() will give you the routing table. I don't think
there is an equivelent for the ARP table, but you could add one.

      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

RE: [ECOS] routines to dump ARP and Route table in ecos -

[Alok Singh]

For dumping ARP table(llinfo) - db_show_arptab() is present in open BSD
code in if_ether.c file.  This works fine on net BSD too. 

regards,
Alok

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: Thursday, May 31, 2007 8:52 PM
To: Madan Mohan Goud
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] routines to dump ARP and Route table in ecos

On Thu, May 31, 2007 at 07:59:19PM +0530, Madan Mohan Goud wrote:
> Hi all,
> 	   Could any of you let me know if there are any routines to
> print/dump ARP Table and Route Table maintained by FreeBSD stack of
> ECOS?

show_network_tables() will give you the routing table. I don't think
there is an equivelent for the ARP table, but you could add one.

      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