Holger
Tue Jun 20 02:08:25 CDT 2006
> I don't know who "they" are that say this, but it's not true.
Hmm, in a live chat a microsoft employee said that PXA255 BSP isn't anymore
in the CE 5.0 product because you cannot buy the hardware for it (Intel
Lubbock) anymore.
See
http://msdn.microsoft.com/chats/transcripts/mobileembedded/embedded_102804.aspx
"JayLoney_MSFT (Expert):
Q: CE5.0 has no pxa255 BSP, but does include CSP. What is the future
of pxa255 support under CE?
A: Support for the Lubbock BSP which contained 255 was deprecated in
CE 5.0. The CSP drivers were left for people still using the chip,
however the reference board is no longer available in hardware."
Also,
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcehardware5/html/wce50conbspanddrivermigration.asp
says:
"The following BSPs are not supported in Windows CE 5.0:
...
Intel XScale DBPAX250 (Lubbock) Development Platform
If your Windows CE 5.0 OS design requires the Lubbock hardware and
BSP, you can use the BSP for the Intel Mainstone II Development Platform,
which is included in Windows CE 5.0, or a BSP from a third-party vendor.
Windows CE 5.0 provides chip support package (CSP) drivers for the Intel
DBPAX250. These drivers are located in
the %_WINCEROOT%\Public\Common\Oak\CSP\ARM directory."
So, yes, some chip components of the PXA255 are still supported, but no
device which uses this chip. And now, If I, as a total newbie, want to have
an example of how to tie all those CSPs together, then I'm out in the cold.
On the other side, they say that an existing, working BSP for a PXA255
device for CE 4.2 continues to work in CE 5.0. But hey, the BSP for the
Lubbock *IS* an existing, working BSP, so it should still work, when I copy
it to the right places.
And therefore my question, if somewhere a demo or trial software package is
downloadable where I can have a view at this BSP.
BTW, the device for which I'm aiming has a nice working Linux 2.6 support on
it, written by myself. Here I like the fact that no updates suddenly remove
working drivers ... if if they would, I can get very easily my hands on the
old code to have a reference ...