[ECOS] DP83816

["Giri" <giri at jntu dot net>]

Hai Nick,
    as you suggested for the Kevin i tried creating the new package for
DP83816. and one .cdl and one .inl for making it support for the
i386-PC target.
    Still i am not able to initialize the network properly. i am facing
the following problem
1. after starting the redboot it will go and initialize all the NIC's
2. while initializing our NIC it is not finding the base address of the
NIC so it is returning with no device found.
       in the code i found the place where it is failing.
        that is in if_dp83816.c
            dp83816_init()
            {
                    .....
                    ........
                    if (!base) return false;  // No device found

            }
4. for other microcontrollers like i82559 this base address is assigned as
follows
            cyg_pci_configure_device(&dev_info);
            p_i82559->io_address = dev_info.base_map[1];


        here io_address is the base adderss.
3. my doubght is how we are managing this problem in the PPC version

thanks regards
giri

"Kevin S. Martin" <ksmartin@fnal.gov> writes:

> Hey,
>
> I'm trying to get redboot (and eCos) to run on a x86 PC (Diamond
> System's Hercules EBX). It uses a dp83815 ethernet controller. I see
> that there is some support for the dp83816. But this seems to be for
> use in a different architecture (PPC?).
>
> What needs to be changes for it to work under i386?
>
> I can build a redboot.bin using the i386 template redboot package. I
> can boot the system(using a floppy disk) with this binary but of
> course it doesn't find a NIC because the default NIC is a i82559. I
> then remove the default ethernet controller (i82559) packages and add
> the dp83816 package:
>
> [root@bdeelinux packages]# ecosconfig --config=redboot.ecc check
> Target: pc
> Template: redboot
> Added:
>  CYGPKG_IO_ETH_DRIVERS
>  CYGPKG_DEVS_ETH_NS_DP83816
> Removed:
>  CYGPKG_DEVS_ETH_INTEL_I82559
>  CYGPKG_DEVS_ETH_I386_PC_I82559
> No conflicts
>
> After doing this, redboot still doesn't find a NIC. Has anyone else
> used a dp83816 or dp83815 on PC?
>

You need to create a new package to customize the generic DP83816
driver to the hardware. Take the MOAB package, copy it, rename it, and
adapt it to the PC. Since it is a PCI device, you probably dont need
to do very much. Now add that package to the configuration.



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