Re: Concept fussing~

From: Bruce Eitman \(eMVP\) (beitmannospam_at_nospam.neo.rr.com)
Date: 05/28/04 

Date: Fri, 28 May 2004 10:35:31 -0400

I think that you must port the entire BSP. You can try to copy the drivers
out, but I don't know of a way to do that since they are in ROM. Don't
think that you can do it.

It was suggested in your other thread that you contact Intel. Have you done
that?

Another solution that would be a good one, is get a different board that
comes with a source or binary BSP. This could save you man months on your
project and would be money well spent. Sometimes when you get started on a
project and find that the decisions that you have made weren't so good, it
pays to make new decisions. 

-- 
   Bruce Eitman (eMVP)
   Senior Engineer

Relevant Pages

  • Re: ce5 BSP in ce6
    ... The ce6 BSP will be comming in few months. ... the CE6 CEPC BSP and the just port the BSP drivers to CE6. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Some broad questions
    ... Some drivers are provided by microsoft and some are by intel. ... SDK - Generated using Platform builder after the BSP and the OS design are ...
    (microsoft.public.windowsce.embedded)
  • Re: Development environment best practices?
    ... >>> OS's interface to the hardware (the OAL is part of the BSP, ... Do most developers create a BSP based on one provided ... >>> dev board and include proprietary drivers in the BSP? ... >>> the associated SDK is generated, how often will that SDK change? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: New Hardware Design
    ... You'll also need to port the drivers and OAL... ... As I have mentioned the new PXA270 hardware ... is to use the Mainstone bsp as a starting point and pull your changes in, ... BSP structure and apply it to the pxa270 hardware. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ipAttach error - not an End device. PMC ethernet slots
    ... Scanning device on PCI-32 Bus ... ... If you don't have source for the drivers, ... This failure could occur simply because the BSP isn't looking for the ... Yes I did check with the board vendor, they assured me it is an END ...
    (comp.os.vxworks)