plaform builder error with deployment
Hi All,
I have used an .rtf file describing how to use the ce device emulator. It was useful, however I am still experiencing some problems. When I attempt to connect to the device emulator, I get a dialog box that displays the errros listed below;
The Kernel Debugger is waiting to connect with target.
The Kernel Debugger has been disconnected successfully.
The Kernel Debugger is waiting to connect with target.
Your virtual machine may not have enough RAM allocated. Try increasing the RAM allocation (if you are using Platform Builder open the Configure Remote Services dialog, choose the Emulator Download service, and click the configure button).
I don't know how to fix it. After building the OS and the SDK and installing the SDK, I get the device emulator to be recognised in the active target device drop down box. It was suggested that I could use the /memsize command on the command line, however I can't seem to get the command line window (from Target => CE Target Control) either. The control is disabled.
Does anyone know how to fix the problem (marked in red)?
Does anyone know, why would the CE Target Control be disabled? Also how can I enable it?
Thanks,
Rachad
[1323 byte] By [
Rachad] at [2007-12-25]
Hi Rachad
You have propably set the Download and Transport options to 'Emulator' in the 'Target Device Connectivity Opions' and ar trying to run a ARM image designed for the new Device Emulator.
Platform Builder 5.0 does only support its own x86 based emulator. The new ARM Device Emulator (shipped with VS2005) is not supported for OS level (kernel) debugging.
If you download an ARM image to the x86 emulator - it won't boot at all and does not start any of the kernel debugging services.
To get this working:
Add the BSP 'Emulator: x86' to your OS design and build the release configuration.
Now, the 'Attach Device' command sould download the newly created x86 OS file to the x86 emulator.
Hope this helps.
Michael
Hi Michael,
I am also facing simillary problem as Richard when I try to download ARM device emulator image for my custom WinCE 5.0 OS built using platform builder.
As you suggested, I can create custom image for WinCE 5.0 for x86. Also I can successfully download it when I select "Attach Device" option.
My question is that I installed Device Emulator BSP (http://www.microsoft.com/downloads/details.aspx?FamilyID=474B03A6-E87D-455D-BC16-B8CF18EF39B4&displaylang=en) which is meant for develoment for WinCE 5.0 using VS 2005, then why it is not working. Is there any work around for that? Or We can't connect to WinCE 5.0 emulator created using platform builder with Visual Studio 2005?
Here pain is that I can create WinCE 5.0 emulator for x86 but we can't target it using VS 2005. It simply fails to load application project if we install SDK built by Platform builder for the WinCE 5.0 image created by US. While In case of ARM device emulator we can install SDK built by platform builder and target it from Visual Studio 2005 but we emulator fails to launch saying Not sufficiety RAM (the same problem mentioned by Richard).
Please guide me how can I develop/debug my application for WinCE 5.0 without having physical WinCE 5.0 device?
Thanks & Regards,
Naynesh
Hi Naynesh
Yes, the 'Device Emulator BSP' you installed is the BSP required to build OS design for the new ARM based emulator shipped in VS 2005.
The document 'Using the CE DeviceEmulator.rtf' found in '<WINCEROOT>\PLATFORM\Deviceemulator' describes step by step how to create an OS for the VS 2005 Device Emulator.
This sould enable you to do normal app development with Visual Studio 2005. Just be aware that you won't be able to debug the OS (no kernel debugger).
Hope this helps
Michael
Hello Michael,
Thank you very much for your help.
I followed the document and now I can successfully target device emulator from Visual Studio 2005 and run my applications.
Here one thing to note that I could not launch device emulator from PB using "Attach Device" option. I guess it may be the limitation of PB.
Also my project is in .NET and I can debug my code too. I guess I could not debug my EVC++ code!!!
Thanks & Regards,
Naynesh
Vicky,
I am not clear as to what exactly it is that you are asking but I will try to answer it the best I can. When you create an OS image using PB, you need to create an SDK for the OS image on the emulator (or device). The creation of the SDK is explained in 'Using the CE DeviceEmulator.rtf' mentioned by Michael. So after you build the SDK from PB 5, by clicking on Platform -> SDK -> New SDK then Build SDK, this should create you an SDK for the device with the OS image that you built. The SDK that you create by following these steps is found in c:\WINCE500\PBWorkspaces\<project name>\SDK. All you need to do is get the msi and install it on the machine containing VS2005. This part is described in 'Using the CE DeviceEmulator.rtf' in steps 9 - 19. Once this SDK is installed you will be able to select the device name that was given to your device in step 14 in VS2005 when wanting to deploy your application. Now, to be able to create an OS image for the ARMV4I device emulator, you will need to install the BSP, which has been listed by Naynesh (above). Once this is installed you will have the device emulator as a selection when choosing the targeted device.Hope this is what you were looking for.
Rachad
