> The second problem you describe is an old one. Again, since > the ethernet hardware is being shared, things can get confused, > especially during system startup. What's happening is that the > eCos application is reinitializing the network hardware, but at > the same time, trying to print messages using that same hardware. > This simply can't work. I put a change into the stack (years ago) > that side-steps this by forcing those initialization messages > to go to the raw serial console, rather than via the network. >
I think I found the config option that you speak of: CYGPKG_NET_FORCE_SERIAL_CONSOLE. Once I set this option, the 'default' and the 'net' templates behaved the same. Thank you! -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
