Communication with the specific device is too device-specific for us to be
of any more help.  I would *not* change development environments, at this
point, until you have consulted with the device OEM about how to communicate
with it via Platform Manager and eVC (PM is the piece that eVC uses, along
with the remote tools).

If it were me, I'd first create a new project in eVC, now that you have the
right SDK installed.  Make sure that you select the correct processor family
that matches what your target device has in the new project wizard.  Once
the program creation is done, there should be a drop-down listbox in the
toolbar for eVC that shows devices that you may choose to target.  One of
them should say "My Device Type", or whatever your device is called.  MAKE
SURE THAT IT DOES NOT SAY ANYTHING ABOUT THE STANDARD SDK.  If you have the
Standard SDK installed and install another, specific device SDK, you'll get
entries like My Device Type - Standard SDK.  THAT IS NOT WHAT YOU WANT.
Once you have selected the right SDK, there is another drop-down list in the
toolbar that should allow you to choose the actual processor for which to
compile and whether to do a debug or non-debug build.  Make sure that you
choose Debug, of course, but also the real processor in the device.  For
example, if one of our devices includes a custom emulator for the device, we
might see x86 Emulator, *AND* x86 in the list.  You have to choose the right
one or your code will not run.  Finally, there should be a third drop-down
list in the eVC toolbar which indicates the actual target device on which to
run the code.  This might include My Device Type Device and My Device Type
Emulator, if your device SDK has an emulator for the device.  Make sure to
choose My Device Type Device to select the real device.

Beyond that, again, it's device-specific.  Our devices tell how to talk to
them from eVC and Visual Studio in the manual; I'd assume that most devices
do the same...

Paul T.