This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Neponset + CF on Redboot
- From: todd dot kallam at acterna dot com
- To: srijon at innvo dot com
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 2 Jan 2002 10:55:32 -0500
- Subject: Re: [ECOS] Neponset + CF on Redboot
Hi,
I have an Assabet/Neponset running with Redboot.
The Socket CF card only seems to work when inserted
in the CF slot on the Assabet, not in the PCMCIA
slots on the Neponset. I have phase 5 hardware.
After I boot Linux, I use the ethernet chip set on
the Neponset board because Linux does not seem to
support the Socket CF card. I don't think that
Ecos supports the ethernet chip set on the Neponset.
You also need to make sure that you added the following
lines to redboot_ROM.ecm or other configuration if you
are using the Neponset:
cdl_option CYGSEM_HAL_ARM_SA11X0_ASSABET_NEPONSET_TIMINGS {
user_value 1
};
I hope this helps.
Todd
> Gary Thomas wrote:
> > > Yes, but it's only been tested with certain makes of card. We've tested
> > > with the Socket CF LPE+, and someone else confirmed the PRETEC CompactLAN
> > > card worked.
> >
> > A couple of questions:
> > * Do you actually have the Neponset board (SA1111)? I'm not sure we've
> > tested it much with that in place.
> > * Does this 'won't go ready' happen all the time? I've seen it happen
> > with some cards, but only after they've been initialized once (after
> > a reset)
> >
> > You could try adding some messages in the CF ethernet driver code to try
> > and figure out what's happening and why it might be failing. Of
> > interest might be the CIS data which gets read by that driver.
>
> Srijon Biswas wrote:
>
> Hi, sorry for the late reply.
>
> The card is Socket CF-LPE. I do have the Neponset attached, and the CF
> card goes into the PCMCIA with a common CF to PCMCIA converter.
>
> If it has not really been tested much (as opposed to it not working due
> to some stupidity on my part :) ),
> then I'll maybe try out adding messages to the driver code and testing.
>
> Thanks,
> Srijon