Re: [ECOS] problem with network initialization

[Andrew Lunn <andrew at lunn dot ch>]

> For the application image, we built the 'Default' template with the
> following packages:

template net would be a better choice.

> Andrew asked us to initialize the network interfaces through the
> init_all_network_interfaces() routine. But we're only using FCC1 for
> Ethernet, and that, I believe, is being configured in the 'Basic Networking
> Framework' package, through the option "Initialization options for 'eth1'".
> Do we need to initialize it elsewhere?

This is just providing the information needed by the
initialization. It does not perform the initialization.

> So as we can see, it is again initializing FCC1 & FCC2 from the application
> code. Is this correct? Or should we leave out the 'Common Ethernet' package
> in one of the two images (Redboot and application)?

Use the redboot template when building redboot. Use the net template
when building applications that need networking. For the moment i
advice you not to remove packages. Thats for users who know what they
are doing.
 
> Not only this, during the second initialization, both FCC1 & FCC2 are
> configured as '100Mb/Full Duplex', which is not the case during the first
> setup. This is incorrect too, since we're not using FCC1 at all.

Have you told it you are not using it or do you expect eCos to read
your mind? Does it even matter?

> And, as I mentioned above, the system doesn't respond to pings once the
> application image is run, though all the MPC8260 FCC registers show the
> correct values, and even the FCC2 event register never shows a buffer
> overflow.

Do you know what the difference is between a network device and a
network interface? Probably not, which is what is causing you
problems. I suggest you do a little research.

        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