[ECOS] networking on redboot

[ECOS] networking on redboot

[ATILAY YILMAZ]

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>

Regards,

--
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] networking on redboot

[Gary Thomas]

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

-- 
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] networking on redboot

[ATILAY YILMAZ]

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?

On Thu, Mar 5, 2009 at 2:15 PM, Gary Thomas <gary@mlbassoc.com> 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
> ------------------------------------------------------------
>

--
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] networking on redboot

[Gary Thomas]

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 <gary@mlbassoc.com> 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
------------------------------------------------------------

-- 
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] networking on redboot

[Atilay Yilmaz]

On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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

Re: [ECOS] networking on redboot

[Gary Thomas]

Atilay Yilmaz wrote:
> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?

Look in 'ecos.ecc' - it will tell you why


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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] networking on redboot

[Atilay Yilmaz]

On Thu, Mar 5, 2009 at 4:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> Atilay Yilmaz wrote:
>> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?
>
> Look in 'ecos.ecc' - it will tell you why
>
Thanks, I found the reason, it compiles now:)

--
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] networking on redboot

[Gary Thomas]

Atilay Yilmaz wrote:
> On Thu, Mar 5, 2009 at 4:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> Atilay Yilmaz wrote:
>>> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?
>> Look in 'ecos.ecc' - it will tell you why
>>
> Thanks, I found the reason, it compiles now:)
> 

Care to share - that way the mailing list archives may be able
to help the next person with a similar problem :-)


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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] networking on redboot

[Atilay Yilmaz]

On Wed, Mar 11, 2009 at 4:53 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> Atilay Yilmaz wrote:
>> On Thu, Mar 5, 2009 at 4:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>> Atilay Yilmaz wrote:
>>>> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?
>>> Look in 'ecos.ecc' - it will tell you why
>>>
>> Thanks, I found the reason, it compiles now:)
>>
>
> Care to share - that way the mailing list archives may be able
> to help the next person with a similar problem :-)
>
there is a option (CYGDAT_USE_LSA_ETHERNET) in ecc file and
CYGPKG_DEVS_ETH_ARM_ERTEC requires that option as false. After that,
the driver compiled but unfortunately it wasn't for SMSC91C111.
therefore I am still working on it:)

--
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] networking on redboot

[Atilay Yilmaz]

On Thu, Mar 12, 2009 at 5:03 PM, Atilay Yilmaz <atiyil@gmail.com> wrote:
> On Wed, Mar 11, 2009 at 4:53 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> Atilay Yilmaz wrote:
>>> On Thu, Mar 5, 2009 at 4:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> Atilay Yilmaz wrote:
>>>>> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?
>>>> Look in 'ecos.ecc' - it will tell you why
>>>>
>>> Thanks, I found the reason, it compiles now:)
>>>
>>
>> Care to share - that way the mailing list archives may be able
>> to help the next person with a similar problem :-)
>>
> there is a option (CYGDAT_USE_LSA_ETHERNET) in ecc file and
> CYGPKG_DEVS_ETH_ARM_ERTEC requires that option as false. After that,
> the driver compiled but unfortunately it wasn't for SMSC91C111.
> therefore I am still working on it:)
>
Hi again,
finally I compiled driver for SMSC91C111 successfully. I also modified
\ecos\packages\devs\eth\arm\ertec\current\include\devs_eth_arm_ertec.inl
and \ecos\packages\devs\eth\arm\ertec\current\cdl\ertec_eth_drivers.cdl
files to define SMSC91C111 definitions/functions for ertec board.
however, still I get:
smsc_lan91cxx_init: No 91Cxx signature found
No network interfaces found
When I run redboot.bin. what do you think the reason may be?

--
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] networking on redboot

[Gary Thomas]

Atilay Yilmaz wrote:
> On Thu, Mar 12, 2009 at 5:03 PM, Atilay Yilmaz <atiyil@gmail.com> wrote:
>> On Wed, Mar 11, 2009 at 4:53 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>> Atilay Yilmaz wrote:
>>>> On Thu, Mar 5, 2009 at 4:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>> Atilay Yilmaz wrote:
>>>>>> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?
>>>>> Look in 'ecos.ecc' - it will tell you why
>>>>>
>>>> Thanks, I found the reason, it compiles now:)
>>>>
>>> Care to share - that way the mailing list archives may be able
>>> to help the next person with a similar problem :-)
>>>
>> there is a option (CYGDAT_USE_LSA_ETHERNET) in ecc file and
>> CYGPKG_DEVS_ETH_ARM_ERTEC requires that option as false. After that,
>> the driver compiled but unfortunately it wasn't for SMSC91C111.
>> therefore I am still working on it:)
>>
> Hi again,
> finally I compiled driver for SMSC91C111 successfully. I also modified
> \ecos\packages\devs\eth\arm\ertec\current\include\devs_eth_arm_ertec.inl
> and \ecos\packages\devs\eth\arm\ertec\current\cdl\ertec_eth_drivers.cdl
> files to define SMSC91C111 definitions/functions for ertec board.
> however, still I get:
> smsc_lan91cxx_init: No 91Cxx signature found
> No network interfaces found
> When I run redboot.bin. what do you think the reason may be?

Go to the SMSC driver and print out what it found for the
signature.  The problem will probably be obvious from that.


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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] networking on redboot

[Andrew Lunn]

> Hi again,
> finally I compiled driver for SMSC91C111 successfully. I also modified
> \ecos\packages\devs\eth\arm\ertec\current\include\devs_eth_arm_ertec.inl
> and \ecos\packages\devs\eth\arm\ertec\current\cdl\ertec_eth_drivers.cdl
> files to define SMSC91C111 definitions/functions for ertec board.
> however, still I get:
> smsc_lan91cxx_init: No 91Cxx signature found
> No network interfaces found
> When I run redboot.bin. what do you think the reason may be?

    val = get_banksel(sc);
#if DEBUG & 9
    db_printf("LAN91CXX - supposed BankReg @ %x = %04x\n",
                cpd->base+LAN91CXX_BS, val );
#endif

    if ((0xff00 & val) !=  0x3300) {
        CYG_FAIL("No 91Cxx signature" );
        diag_printf("smsc_lan91cxx_init: No 91Cxx signature found\n");
        return false;
    }


You might want to look at get_banksel(). Do you need a special one for
your target?

     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] networking on redboot

[Atilay Yilmaz]

On Fri, Mar 13, 2009 at 2:31 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> Atilay Yilmaz wrote:
>> On Thu, Mar 12, 2009 at 5:03 PM, Atilay Yilmaz <atiyil@gmail.com> wrote:
>>> On Wed, Mar 11, 2009 at 4:53 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> Atilay Yilmaz wrote:
>>>>> On Thu, Mar 5, 2009 at 4:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>>> Atilay Yilmaz wrote:
>>>>>>> On Thu, Mar 5, 2009 at 2:34 PM, Gary Thomas <gary@mlbassoc.com> 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 <gary@mlbassoc.com> 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?
>>>>>> Look in 'ecos.ecc' - it will tell you why
>>>>>>
>>>>> Thanks, I found the reason, it compiles now:)
>>>>>
>>>> Care to share - that way the mailing list archives may be able
>>>> to help the next person with a similar problem :-)
>>>>
>>> there is a option (CYGDAT_USE_LSA_ETHERNET) in ecc file and
>>> CYGPKG_DEVS_ETH_ARM_ERTEC requires that option as false. After that,
>>> the driver compiled but unfortunately it wasn't for SMSC91C111.
>>> therefore I am still working on it:)
>>>
>> Hi again,
>> finally I compiled driver for SMSC91C111 successfully. I also modified
>> \ecos\packages\devs\eth\arm\ertec\current\include\devs_eth_arm_ertec.inl
>> and \ecos\packages\devs\eth\arm\ertec\current\cdl\ertec_eth_drivers.cdl
>> files to define SMSC91C111 definitions/functions for ertec board.
>> however, still I get:
>> smsc_lan91cxx_init: No 91Cxx signature found
>> No network interfaces found
>> When I run redboot.bin. what do you think the reason may be?
>
> Go to the SMSC driver and print out what it found for the
> signature.  The problem will probably be obvious from that.
>
I compiled it again to print 'val', Gary:
smsc_lan91cxx_init: No 91Cxx signature found e59f
No network interfaces found
what is e59f? actually, I don't much about these numbers

Hi Andrew, what do you mean by 'special one for your target'? I don't
know what this function is, in fact. the comments says it reads bank
register. the code is:
get_banksel(struct eth_drv_sc *sc)
{
    struct lan91cxx_priv_data *cpd =
        (struct lan91cxx_priv_data *)sc->driver_private;
    unsigned short val;

    HAL_READ_UINT16(cpd->base+(LAN91CXX_BS << cpd->addrsh), val);
    val = CYG_LE16_TO_CPU(val);
#if DEBUG & 2
    diag_printf("read bank val 0x%04x\n", val);
#endif
    return val;
}

--
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] networking on redboot

[Mark Salter]

On Fri, 2009-03-13 at 15:07 +0200, Atilay Yilmaz wrote:
> >
> I compiled it again to print 'val', Gary:
> smsc_lan91cxx_init: No 91Cxx signature found e59f

The e59f looks suspiciously like the upper 16 bits of an arm opcode.
Maybe check that the base address being used is correct.

--Mark



-- 
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] networking on redboot

[Andrew Lunn]

> Hi Andrew, what do you mean by 'special one for your target'? I don't
> know what this function is, in fact. the comments says it reads bank
> register. the code is:

Maybe it is time you started reading the data sheet for your hardware
and the ethernet chipset. 

    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] networking on redboot

[Atilay Yilmaz]

On Fri, Mar 13, 2009 at 3:28 PM, Mark Salter <msalter@redhat.com> wrote:
> On Fri, 2009-03-13 at 15:07 +0200, Atilay Yilmaz wrote:
>> >
>> I compiled it again to print 'val', Gary:
>> smsc_lan91cxx_init: No 91Cxx signature found e59f
>
> The e59f looks suspiciously like the upper 16 bits of an arm opcode.
> Maybe check that the base address being used is correct.
>
> --Mark
>
thanks, I will check it. somehow, the signature is 0xe5 instead of 0x33

-- 
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] networking on redboot

[Mark Salter]

On Fri, 2009-03-13 at 16:27 +0200, Atilay Yilmaz wrote:
> On Fri, Mar 13, 2009 at 3:28 PM, Mark Salter <msalter@redhat.com> wrote:
> > On Fri, 2009-03-13 at 15:07 +0200, Atilay Yilmaz wrote:
> >> >
> >> I compiled it again to print 'val', Gary:
> >> smsc_lan91cxx_init: No 91Cxx signature found e59f
> >
> > The e59f looks suspiciously like the upper 16 bits of an arm opcode.
> > Maybe check that the base address being used is correct.
> >
> > --Mark
> >
> thanks, I will check it. somehow, the signature is 0xe5 instead of 0x33

I suspect your base address is incorrectly set to 0 or maybe there is a
memory mapping problem. The e59f makes me think you are reading from
memory, not the lan chip.

--Mark



-- 
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] networking on redboot

[Atilay Yilmaz]

On Fri, Mar 13, 2009 at 4:49 PM, Mark Salter <msalter@redhat.com> wrote:
>
> On Fri, 2009-03-13 at 16:27 +0200, Atilay Yilmaz wrote:
>> On Fri, Mar 13, 2009 at 3:28 PM, Mark Salter <msalter@redhat.com> wrote:
>> > On Fri, 2009-03-13 at 15:07 +0200, Atilay Yilmaz wrote:
>> >> >
>> >> I compiled it again to print 'val', Gary:
>> >> smsc_lan91cxx_init: No 91Cxx signature found e59f
>> >
>> > The e59f looks suspiciously like the upper 16 bits of an arm opcode.
>> > Maybe check that the base address being used is correct.
>> >
>> > --Mark
>> >
>> thanks, I will check it. somehow, the signature is 0xe5 instead of 0x33
>
> I suspect your base address is incorrectly set to 0 or maybe there is a
> memory mapping problem. The e59f makes me think you are reading from
> memory, not the lan chip.
>
> --Mark
>
I've checked the board manual and entered the correct base address. As
you guessed correctly, it was zero before:)
However, still I got the same error:
smsc_lan91cxx_init: No 91Cxx signature found 0xffff
LAN91CXX - supposed BankReg @ 3340000e = ffff
No network interfaces found

Here is the data structure that I enter base address in inl file:

static lan91cxx_priv_data lan91cxx_eth0_priv_data =
{
  base : (unsigned short *) 0x33400000,

  #ifdef CYGSEM_DEVS_ETH_ARM_ERTEC_ETH0_SET_ESA
  enaddr : CYGDAT_DEVS_ETH_ARM_ERTEC_ETH0_ESA,
  hardwired_esa : true,
  #else
  hardwired_esa : false,
  provide_esa   : &_ertec_arm9_provide_eth0_esa,
  #endif
};

are there any other configuration files that I have to update except
cdl and inl?

the driver source code:
    // probe chip by reading the signature in BS register
    val = get_banksel(sc);

    if ((0xff00 & val) !=  0x3300) {
        CYG_FAIL("No 91Cxx signature" );
        diag_printf("smsc_lan91cxx_init: No 91Cxx signature found
0x%04x\n", val);
        diag_printf("LAN91CXX - supposed BankReg @ %04x =
%04x\n",cpd->base+LAN91CXX_BS, val);
        return false;
    }

and get_banksel() is defined in driver header:
// Read the bank register (this one is bank-independent)
#ifndef SMSC_PLATFORM_DEFINED_GET_BANKSEL
static __inline__ unsigned short
get_banksel(struct eth_drv_sc *sc)
{
    struct lan91cxx_priv_data *cpd =
        (struct lan91cxx_priv_data *)sc->driver_private;
    unsigned short val;

    HAL_READ_UINT16(cpd->base+(LAN91CXX_BS << cpd->addrsh), val);
    val = CYG_LE16_TO_CPU(val);
    return val;
}
#endif

do you think it reads 'val' from memory, not the lan chip? how can I test it?

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