Re: [ECOS] networking on redboot

[Atilay Yilmaz <atiyil@gmail.com>]

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