* [ECOS] Which packages are needed for networking?
@ 2001-02-16 9:09 Lewin A.R.W. Edwards
2001-02-16 10:01 ` Bart Veer
0 siblings, 1 reply; 6+ messages in thread
From: Lewin A.R.W. Edwards @ 2001-02-16 9:09 UTC (permalink / raw)
To: ecos-discuss
I'm a bit confused; somehow I've managed to break something that was
previously working. I am trying to compile a simple network test app
(with code borrowed from ftp_test.c) for the EDB7xxx platform. I
previously managed to build OK, but something - NO idea what! - has
broken; I haven't changed my build process that I can remember.
Could someone read over the below and tell me what I'm doing wrong?
Looks like a package needs to be added (probably something to do with
filesystems?), but it _used_ to work and I didn't add any other
packages.
Using CVS sources a week old,
ecosconfig new edb7xxx
ecosconfig add eth_drivers net
ecosconfig tree
make
then into my app's directory and make 2>&1 | tee make.out
arm-elf-gcc -c -o main.o -g -I. -I../ecos/install/include
-ffunction-sections -fdata-sections -mcpu=arm7tdmi -DDF57 main.c
In file included from ../ecos/install/include/network.h:63,
from main.c:14:
../ecos/install/include/sys/param.h:120:28: sys/simplelock.h: No such
file or directory
../ecos/install/include/sys/param.h:132:27: sys/syslimits.h: No such
file or directory
../ecos/install/include/sys/param.h:162:24: sys/signal.h: No such file
or directory
In file included from ../ecos/install/include/network.h:65,
from main.c:14:
../ecos/install/include/sys/ioctl.h:103:24: sys/ttycom.h: No such file
or directory
In file included from ../ecos/install/include/network.h:65,
from main.c:14:
../ecos/install/include/sys/ioctl.h:123:22: sys/dkio.h: No such file or
directory
../ecos/install/include/sys/ioctl.h:124:23: sys/filio.h: No such file or
directory
In file included from ../ecos/install/include/network.h:78,
from main.c:14:
../ecos/install/include/bootp.h:95:49: bptypes.h: No such file or
directory
In file included from ../ecos/install/include/network.h:78,
from main.c:14:
../ecos/install/include/bootp.h:316: warning: no semicolon at end of
struct or union
../ecos/install/include/bootp.h:316: parse error before "v_flags"
../ecos/install/include/bootp.h:326: parse error before "v_unused"
../ecos/install/include/bootp.h:326: warning: data definition has no
type or storage class
../ecos/install/include/bootp.h:328: parse error before '}' token
make: *** [main.o] Error 1
On a related note, is there a concise list of packages somewhere, other
than browsing through the cdl files? (That's why I love the graphical
config tool; it shows me everything :)
-- Lewin A.R.W. Edwards (Embedded Engineer) * Linux system
Work: http://www.digi-frame.com/
Personal: http://www.larwe.com/ and http://www.zws.com/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ECOS] Which packages are needed for networking?
2001-02-16 9:09 [ECOS] Which packages are needed for networking? Lewin A.R.W. Edwards
@ 2001-02-16 10:01 ` Bart Veer
2001-02-16 11:19 ` Lewin A.R.W. Edwards
2001-02-16 11:55 ` [ECOS] Still having problems getting networking up Lewin A.R.W. Edwards
0 siblings, 2 replies; 6+ messages in thread
From: Bart Veer @ 2001-02-16 10:01 UTC (permalink / raw)
To: larwe; +Cc: ecos-discuss
>>>>> "Lewin" == Lewin A R W Edwards <larwe@larwe.com> writes:
Lewin> I'm a bit confused; somehow I've managed to break something
Lewin> that was previously working. I am trying to compile a
Lewin> simple network test app (with code borrowed from
Lewin> ftp_test.c) for the EDB7xxx platform. I previously managed
Lewin> to build OK, but something - NO idea what! - has broken; I
Lewin> haven't changed my build process that I can remember.
Lewin> Could someone read over the below and tell me what I'm
Lewin> doing wrong? Looks like a package needs to be added
Lewin> (probably something to do with filesystems?), but it _used_
Lewin> to work and I didn't add any other packages.
Lewin> Using CVS sources a week old,
Lewin> ecosconfig new edb7xxx
Lewin> ecosconfig add eth_drivers net
You should be able to just do "ecosconfig new edb7xxx net" to combine
the above two steps, but that is not the problem here.
Lewin> ecosconfig tree
Lewin> make
Lewin> then into my app's directory and make 2>&1 | tee make.out
Lewin> arm-elf-gcc -c -o main.o -g -I. -I../ecos/install/include
Lewin> -ffunction-sections -fdata-sections -mcpu=arm7tdmi -DDF57 main.c
Lewin> In file included from ../ecos/install/include/network.h:63,
Lewin> from main.c:14:
Lewin> ../ecos/install/include/sys/param.h:120:28: sys/simplelock.h: No such
Lewin> file or directory
OK, let's take a look at sys/param.h at ~line 120 to see what the
problem might be:
#ifndef __ECOS
#include <sys/simplelock.h>
#endif
And quoting from the TCP/IP documentation at
http://sources.redhat.com/ecos/docs-latest/tcpip/tcpip.3.html#pgfId=1133601
"In general, using the networking code may require definition of two
symbols: _KERNEL and __ECOS. _KERNEL is not normally required; __ECOS
is normally required. So add this to your compile lines for files
which use the network stack:
-D__ECOS"
so that should solve the problem.
<snip>
Lewin> On a related note, is there a concise list of packages
Lewin> somewhere, other than browsing through the cdl files?
Lewin> (That's why I love the graphical config tool; it shows me
Lewin> everything :)
$ ecosconfig --help
Usage: ecosconfig [ qualifier ... ] [ command ]
commands are:
list : list repository contents
<snip>
That is as concise as it is going to get for now, given the number of
packages and targets in the current system. Alternatively you can look
at the ecos.db file in any text editor, since that is where the
information comes from.
Bart
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ECOS] Which packages are needed for networking?
2001-02-16 10:01 ` Bart Veer
@ 2001-02-16 11:19 ` Lewin A.R.W. Edwards
2001-02-16 11:55 ` [ECOS] Still having problems getting networking up Lewin A.R.W. Edwards
1 sibling, 0 replies; 6+ messages in thread
From: Lewin A.R.W. Edwards @ 2001-02-16 11:19 UTC (permalink / raw)
To: bartv; +Cc: ecos-discuss
Hi Bart,
> And quoting from the TCP/IP documentation at
> http://sources.redhat.com/ecos/docs-latest/tcpip/tcpip.3.html#pgfId=1133601
>
> "In general, using the networking code may require definition of two
> symbols: _KERNEL and __ECOS. _KERNEL is not normally required; __ECOS
Ouf. And I thought I had read the introductory portions of the documentation
carefully. Sorry about that, and thanks for the analysis :)
> Usage: ecosconfig [ qualifier ... ] [ command ]
> commands are:
> list : list repository contents
> <snip>
If you imagine the packages as being in a tree (like the tree control in the
graphical configtool) then ecosconfig list gives a "trunk" without dependency
descriptions or sub-options.
I guess what I'm really looking for boils down to "the graphical configuration
tool". I think I will run the graphical tool on my Windows desktop system here so I
can refer to things and know how to drive my Linux dev box. It gives me a better
idea of the relationship of the various packages.
> packages and targets in the current system. Alternatively you can look
> at the ecos.db file in any text editor, since that is where the
> information comes from.
Right, that is where I look now. I then need to go down into the sub-files in order
to extract some of the "implicitly adds xxx..." type info though.
-- Lewin A.R.W. Edwards (Embedded Engineer) * Linux system
Work: http://www.digi-frame.com/
Personal: http://www.larwe.com/ and http://www.zws.com/
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] Still having problems getting networking up
2001-02-16 10:01 ` Bart Veer
2001-02-16 11:19 ` Lewin A.R.W. Edwards
@ 2001-02-16 11:55 ` Lewin A.R.W. Edwards
2001-02-16 12:30 ` Gary Thomas
1 sibling, 1 reply; 6+ messages in thread
From: Lewin A.R.W. Edwards @ 2001-02-16 11:55 UTC (permalink / raw)
To: bartv; +Cc: ecos-discuss
> Lewin> ecosconfig new edb7xxx
> Lewin> ecosconfig add eth_drivers net
>
>You should be able to just do "ecosconfig new edb7xxx net" to combine
>the above two steps, but that is not the problem here.
Just FYI, it seems that template is currently broken, as eCos won't build
successfully with "ecosconfig new edb7xxx net". I'll redo it and send a
make.out if you want, but it should be easy to reproduce.
Anyway, I got everything built OK, but it seems that more configuration is
required. When my app starts, it hangs repeating "CS8900: Tx interrupt lost".
To gather a little more info, I set up a (different from previous) bogus
MAC address of 0x00:0x14:0x49:0x18:0x14:0x00 using fconfig, and I enabled
boot-time network debugging. Power up and I get several repetitions of this:
Ethernet send:
0x000029E4: FFFF FFFF FFFF 0014 4918 1400 0800 |........I..... |
0x0000C93C: 4500 0148 0002 0000 4011 79A4 0000 0000 |E..H....@.y.....|
0x0000C94C: FFFF FFFF 0044 0043 0134 0F6B 0101 0600 |.....D.C.4.k....|
0x0000C95C: 5555 3412 0000 0000 0000 0000 0000 0000 |UU4.............|
0x0000C96C: 0000 0000 0000 0000 0014 4918 1400 0000 |..........I.....|
0x0000C97C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C98C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C99C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C9AC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C9BC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C9CC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C9DC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C9EC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000C9FC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA0C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA1C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA2C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA3C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA4C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA5C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA6C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
0x0000CA7C: 0000 0000 0000 0000 |........ |
Tx event: 8
Can't get BOOTP info - network disabled!
RedBoot>
The link LED is on, everything should be working I think. Is there
something else I've forgotten?
One issue that I don't understand here is the following quote from
< http://sources.redhat.com/ecos/docs-latest/tcpip/tcpip.3.html#pgfId=1132625 >:
"This assumes that the MAC address is already defined in the serial EEPROM
or however the particular target implements this; there is no (tested)
support for setting the MAC address in this release." Does the networking
code in eCos [not redboot] read the MAC address set by fconfig and saved in
main flash store? If not, then how is it possible to bring up eth0 on the
Cirrus board?
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: [ECOS] Still having problems getting networking up
2001-02-16 11:55 ` [ECOS] Still having problems getting networking up Lewin A.R.W. Edwards
@ 2001-02-16 12:30 ` Gary Thomas
0 siblings, 0 replies; 6+ messages in thread
From: Gary Thomas @ 2001-02-16 12:30 UTC (permalink / raw)
To: Lewin A.R.W. Edwards; +Cc: ecos-discuss
On 16-Feb-2001 Lewin A.R.W. Edwards wrote:
>
>> Lewin> ecosconfig new edb7xxx
>> Lewin> ecosconfig add eth_drivers net
>>
>>You should be able to just do "ecosconfig new edb7xxx net" to combine
>>the above two steps, but that is not the problem here.
>
> Just FYI, it seems that template is currently broken, as eCos won't build
> successfully with "ecosconfig new edb7xxx net". I'll redo it and send a
> make.out if you want, but it should be easy to reproduce.
>
I tried this "six ways from Sunday" against the current [master] sources and
I could not reproduce your error.
> Anyway, I got everything built OK, but it seems that more configuration is
> required. When my app starts, it hangs repeating "CS8900: Tx interrupt lost".
>
If you have an EDB7212 board then you'll need to remove a resistor to get
interrupts to work. Remove R168 and all jumpers from JP45.
Alternatively, you can try enabling the #define INTS_DONT_WORK in the driver.
> To gather a little more info, I set up a (different from previous) bogus
> MAC address of 0x00:0x14:0x49:0x18:0x14:0x00 using fconfig, and I enabled
> boot-time network debugging. Power up and I get several repetitions of this:
>
> Ethernet send:
> 0x000029E4: FFFF FFFF FFFF 0014 4918 1400 0800 |........I..... |
> 0x0000C93C: 4500 0148 0002 0000 4011 79A4 0000 0000 |E..H....@.y.....|
> 0x0000C94C: FFFF FFFF 0044 0043 0134 0F6B 0101 0600 |.....D.C.4.k....|
> 0x0000C95C: 5555 3412 0000 0000 0000 0000 0000 0000 |UU4.............|
> 0x0000C96C: 0000 0000 0000 0000 0014 4918 1400 0000 |..........I.....|
> 0x0000C97C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C98C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C99C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C9AC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C9BC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C9CC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C9DC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C9EC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000C9FC: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA0C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA1C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA2C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA3C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA4C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA5C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA6C: 0000 0000 0000 0000 0000 0000 0000 0000 |................|
> 0x0000CA7C: 0000 0000 0000 0000 |........ |
> Tx event: 8
> Can't get BOOTP info - network disabled!
> RedBoot>
>
> The link LED is on, everything should be working I think. Is there
> something else I've forgotten?
>
> One issue that I don't understand here is the following quote from
> < http://sources.redhat.com/ecos/docs-latest/tcpip/tcpip.3.html#pgfId=1132625 >:
> "This assumes that the MAC address is already defined in the serial EEPROM
> or however the particular target implements this; there is no (tested)
> support for setting the MAC address in this release." Does the networking
> code in eCos [not redboot] read the MAC address set by fconfig and saved in
> main flash store? If not, then how is it possible to bring up eth0 on the
> Cirrus board?
>
Currently, if you run RedBoot and enable the network address (turn on networking
support in RedBoot) then eCos will just use that. Note: eCos does not get the
ESA from the FLASH, it assumes that RedBoot has set it up.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ECOS] Still having problems getting networking up
2001-02-19 6:33 ` Lewin A.R.W. Edwards
@ 2001-02-19 6:53 ` Bart Veer
0 siblings, 0 replies; 6+ messages in thread
From: Bart Veer @ 2001-02-19 6:53 UTC (permalink / raw)
To: larwe; +Cc: ecos-discuss
> On a related note, would it be possible for the list to be
> reconfigured so that the Reply-to: is the list address, rather than
> the poster's address?
This has been requested before and rejected. The authorative text on
the issue is http://www.unicom.com/pw/reply-to-harmful.html
Bart
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-02-19 6:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-02-16 9:09 [ECOS] Which packages are needed for networking? Lewin A.R.W. Edwards
2001-02-16 10:01 ` Bart Veer
2001-02-16 11:19 ` Lewin A.R.W. Edwards
2001-02-16 11:55 ` [ECOS] Still having problems getting networking up Lewin A.R.W. Edwards
2001-02-16 12:30 ` Gary Thomas
2001-02-17 21:54 [ECOS] new ecosconfig tool di yan
2001-02-19 6:33 ` Lewin A.R.W. Edwards
2001-02-19 6:53 ` [ECOS] Still having problems getting networking up Bart Veer
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).