Archive for August, 2007

VS 2005 Remote Debugging: Updated

August 13, 2007

I revisted this issue yesterday.
I was trying to debug from Vista to XP (VS managed code).
This wouldn’t work.  See my postings on MS Forums:
When I reversed things it worked!  (dev on Vista, target on XP).
I have added some snapshots of the Project.Debug panels here.


Aug 07

I spent some time today and yesterday tring to get Remote debugging in Visual Studio 2005 (Managed Code) going.  I don’t think that the documentation is that good.
I got itgoing today, as a VB.NET console app running on an XP Embedded system remotely with breakpoint and stepping etc.

I took a snapshot of the project-debug settings.:


Project.Debug for 30/11

Previous Project


USB Serial and CE 6 (2) Silicon Labs

August 7, 2007
See entry "USB Serial and CE 6  (1) The Problem" for background on this issue.
The story continues …
 I have been working with a USB-Serial solution for CE 6 from Silicon Labs.
Thanks for the Platform Builder NG reply that pointed me to this.
Silicom Labs provide a chip that presents a serial USART on one end and USB on the other, a bit like the FTDI chips.
They have a VCP driver for various OS ‘s as well as an API approach like the D2XX driver.
I used the CP2102 USB-Serial device.
(Haven’t worked out the difference btw this and the 2103)
Silicon Labs call the API USBXpress.
There is no VCP driver for CE 6 (although there is for XP , Linux etc)
(Download the USBXpress Development Kit from the 2nd link above and you get various documents)
I ordered 2 development kits and had them shipped to Australia (in about 3 days!) for about $US100.
This comes with both the USB and serial cables.
No power supplied needed.
The dev kit board is a USB device on one end and RS232 on the other end.
Alternatively the serial end can be interfaced directly from a microcontroller at TTL levels simplifying exposing a microcontroller as USB
(USB plugs into USB host on PC integrating the micro’s functionality onto the desktop)
For XP use you install the USB low level driver then the VCP.
This as usual makes use of the Vendor ID and Device ID.
There is an app that change these.
Indeed for CE you need to change the device ID.  Whne you do so, on XP only the low level USB driver gets loaded.
The USBExpress API then takes over from there.
The development kit comes with drivers and sample code.
For CE where the host connection is plugged into the CE box, you don’t get a serial API to the device but get a stream driver API.
(Shouldn’t be too hard to build a VCP on top of this API for CE though.)
I have been testing it on an ICOP 2300 box with some success.
See next blog

USB Serial and CE 6 (1) The Problem

August 7, 2007
I have been chasing USB-Serial on CE 6 for some time. 
ie Plug into USB on CE 6 and get RS232 on the other end of the cable.
Its available for desktop. 
Indeed such cables are mandatory for laptops these days because they lack RS232 ports.
Its driver is available for FTDI cables/chips for CE 4.2/5.
– D2XX drivers allow direct access to the USB device through a DLL. 
Application software can access the USB device through a series of DLL function calls. 
– Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. 
Application software can access the USB device in the same way as it would access a standard COM port
eg. With a USB-Serial cable using FTDI chip
I previously used FTDI USB-serial cables with CE 5.
Also an earlier version of the USB245 in embedded applications such as one of my presentation at MEDC last year.
Parallax carries many FTDI items.
FTDI doesn’t seem to be in hurry to bring out CE 6 drivers for their chips.
They said that the CE 5 drivers  wouldn’t work on CE 6, which is understandable given the architectual changes in CE 6.