Problem:
�
I am unable to download/debug an application program I am developing in
CodeWarrior using USB to my Palm or Handspring PDA. I get an alert in CW
saying "Connection attempt failed. Please try again."
�
�
Background:
�
I am using Windows 2K 5.0.0.2195 Service Pack 2 on a 1.8 GHz Pentium
with 256 MB RAM.
�
I have CodeWarrior updated to version 8.2, and have applied both the 4.0
SDK update 1 and new PalmRezPostLinker (and rebuilt the Palm Runtime
Library). The IDE version is 4.2.6.832.
�
USBPort.dll is in CodeWarrior's bin directory. It is 28,672 bytes with a
creation date of 2/15/02 and modification date of 9/20/01 (huh?). It
shows File version 4.1.0.0 and Product Version 4,0,0,0.
�
I have Palm Desktop (from Palm) installed and updated to version 4.0.1.
Its version of USBPort.dll is 28,672 bytes with a creation date of
5/22/02 and modification date of 7/03/01 (huh?). It shows File version
4.1.0.0 and Product Version 4.0.1.
�
I tried swapping the version of USBPort.dll in the CW bin directory with
the one from Palm Desktop, but with no luck.

I did make sure to select a connection type of "USB" for Target "Palm OS
Device" in the PalmDebugger Settings panel in the IDE Preferences
window.

I do not have HotSync running.
�
I do not have Constructor open.
�
I do not have the PalmOS Emulator running or any application running
which uses USBPort.dll.
�
My application program does not have corrupt resources or segments
greater than 65,505 bytes.
�
I have tried this with both a Palm m505 with PalmOS 4.0 and Handspring
Visor with PalmOS 3.5.2H3.0 (both PDAs via USB cradle).
�
Restarting CodeWarrior did not help. Restarting the PC did not help.
�
I am able to download this application via my m505's serial cradle or
cable and also to POSE 3.5.
�
I searched my archives of news.falch.net and news.palmos.com for any
ideas. I tried them to no avail. I did notice one message from Ben
Combee on 7/27/01 " Re: Handspring USB HotSync in Win2k" which mentioned
something about not updating to later versions of Palm Desktop, but it
did not elaborate. To be fair, I did try USB debugging while Palm
Desktop 4.0 was installed, and when I noticed the version discrepancies,
tried updating Palm Desktop to 4.0.1.
�
I reread the "Debugging" and "Troubleshooting" chapters of _Targeting
the PalmOS Platform_ in case I missed anything in the documentation.
�

Request:
�
Can someone tell me what I am missing here? What do I need to do in
order to debug via USB? It sounds like it works for other people, so I
must be missing something.
�
Thanks.
�
-Dave

--
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to