On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <[email protected]> wrote: > Please don't top-post :-( > > ATILAY YILMAZ wrote: >> Thanks for quick reply:) it is an ertec400 board. it has 4 ethernet >> ports and it looks functional since the LEDs are on. however, there is >> another ethernet controller which is SMSC91C111 as a debug port. this >> one doesn't work, no LED action, no link up. the ethernet driver for >> SMSC91C111 is included in ecos packages, I can see that in ecc file. >> however, I am not sure it is also being used by redboot binary. how >> can I make sure of that? > > Check the CDL? > Look in the build directory to see if the driver for that device actually > was built? > > Note: because of the way 'fconfig' works, once you succeed in getting > this driver to build, you'll want to run 'fconfig -i' to reinitialize > the database. Only then will the options to set the ESA be present. > The driver should work with a fallback ESA until then though. > >> On Thu, Mar 5, 2009 at 2:15 PM, Gary Thomas <[email protected]> wrote: >>> ATILAY YILMAZ wrote: >>>> does anybody help me about starting networking on redboot? I use an arm9 >>>> cpu >>>> I guess I need to set MAC address, but it doesn't appear on fconfig >>>> >>>> here is my current config on redboot: >>>> RedBoot> fis list >>>> Name FLASH addr Mem addr Length Entry point >>>> RedBoot 0x30000000 0x30000000 0x00040000 0x00000000 >>>> FIS directory 0x303F0000 0x303F0000 0x0000F000 0x00000000 >>>> RedBoot config 0x303FF000 0x303FF000 0x00001000 0x00000000 >>>> RedBoot> fconfig >>>> Run script at boot: false >>>> Use BOOTP for network configuration: false >>>> Gateway IP address: >>>> Local IP address: 192.168.3.17 >>>> Local IP address mask: 255.255.255.0 >>>> Default server IP address: 192.168.3.18 >>>> DNS domain name: <Not a string: 0x23FEF2F5> >>>> DNS server IP address: >>>> GDB connection port: 9000 >>>> Force console for special debug messages: false >>>> Network debug at boot time: true >>>> RedBoot> >>> Whether or not the ESA shows up in 'fconfig' depends on the driver. >>> >>> What's the platform? network driver? > > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------------------------------------ >
well, cdl for driver (CYGPKG_DEVS_ETH_ARM_ERTEC) is \ecos\packages\devs\eth\arm\ertec\current\cdl\ertec_eth_drivers.cdl and also CYGPKG_DEVS_ETH_ARM_ERTEC exists in ecos.db. the c file is under \ecos\packages\devs\eth\arm\ertec\current\src. however, it is not built under \ECOS\EB400_build\devs\eth\arm\ertec\current\ (this is my location for eclipse project). what may be the reason for that? thanks, -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
