Loading, please wait.
Windows CE build is quite a complex process.
It involves different tools to parse makefiles, build and link code, merge resouces, make the OS image etc. and if something fails during the build is not always easy to understand what's wrong.
It seems that PB (CE 6 in VS 2005) doesn’t like long path names.
I’ve come across this before.
It builds OK but then fails over in makeimage as above.
C:\WINCE600\OSDesigns\LPC3250-DK_BIN with solution file in this directory worked OK.
C:\WINCE600\3rdparty\PhyCore_LPC3250_BSP_EVAL_V1_0_3_Prerelease\OSDesigns\LPC3250-DK_BIN fails as above
I seem to remember that spaces can cause problems too.
It seems a path length issue here.
Thanks to Bruce Eitman:
http://geekswithblogs.net/BruceEitman/archive/2009/06/17/platform-builder-makeimg-fatal-error-out-of-buffer-space.aspx
... And Nicolas Besson seems to have blogged about the same problem jsut when I came accross it:
http://nicolasbesson.blogspot.com/2010/07/make-image-and-out-of-buffer-space.html
There are plenty of example sand how-to’s on how to build a Windows CE image, download and debug it on a target:
Sam’s Jumpstart Kit:
<CD>/Vortex86DX_SPARK_WINCE600_JumpStart_Rev2.5.pdf
<CD>/SampleCodes/OSDesign/MyWinCE_OSDesign_Project_VDX6326.zip
Where the CD is the “Solution of Fault Tolerance x86 System-on-chip” as supplied with the kit
MSDN Virtual Lab: Windows Embedded CE 6.0 Platform Builder Tools
Windows CE 6 Help (Local or at MSDN) Topics:
For a CEPC .. A PC as a CE device, but applies to the Spark Kit:
How to Set Up a CEPC
The major hardware issue is the network card.
It doesn’t need a hard drive
You need a boot floppy, or create a USB boot floppy(Search for HP disk key)
Or you can set up a bootable hard drive formatte ...