Debugging should work with debug ROMs (that's what I use here). Besides the
error alert (which has been fixed internally) I usually have little trouble
connecting. However, you may want to wait until POSE is finished resetting,
and then delete the old .prc before trying to debug the new project. I may
be missing something here as well (perhaps a step or two) so let me know if
that's the case.
Jun-Kiat Lam
Metrowerks Technical Support
----- Original Message -----
From: "Gordon, Douglas" <[EMAIL PROTECTED]>
To: "'Palm Developers'" <[EMAIL PROTECTED]>
Sent: Monday, January 17, 2000 7:50 AM
Subject: Using debug ROMS with CW R6
> Is it generally an OK idea to use the debug ROMs in POSE at the same time
> that you are debugging from CW R6 for Windows? I have been doing this with
> mixed success. When the debugger initially downloads the app, you get a
> debug ROM error alert about a memory chunk in DataMgr.c, which is
apparently
> an artifact of the CW-POSE interaction. After that, debugging appears to
> work OK, and you can find errors detected by the debug ROM logic while
also
> using CW debug features.
>
> However, after going to CW R6 (full release), I now have trouble if I
> terminate a debug session (i.e., press the "halt" icon), change my app,
and
> then try to do another debug. What often happens is that POSE seems to
hang
> after the app is dowloaded, showing just a blank screen. The only recourse
> is to exit from both POSE and CW and start them up again. I'm using the
> latest POSE from the developer site -- the one that was released to go
along
> with OS 3.5.
>
> Doug Gordon
>
