Sigh, this platform is *so* frustrating to program for... :-((( OK, using just debug messages I can't figure out why the program crashes when it tries to respond to a sysNotifyVolumeMountedEvent notification, so I decided that I have to debug it on the device to see at least exactly at which point it is crashing.
Well, how do I do that?! I've read the following documentation: http://www.palmos.com/dev/support/docs/dev_suite/PalmOSDebugger/DbgTool_Connecting.html Let's see... "When debugging with Palm OS Garnet devices, the Palm OS Debugger's ARM Palm OS 5 Debug Nub plug-in communicates through the serial connection with the ARM Debugger Nub for Palm OS Garnet on the device." My device is Tungsten E. It does not *have* a craddle with a serial cable. It connects to the PC with a USB cable. But earlier, the documentation says "Palm OS Debugger supports the following communications plug-ins: * Serial, used primarily to connect to a Palm OS device that supports a serial connection. * USB, used primarily to connect to a Palm OS device that supports a USB connection." implying that such a connection ought to be sufficient. Fine. Then it says "For palmOne devices Tungsten C, Tungsten E, Tungsten T, Tungsten T2, Tungsten T3, Tungsten T5, Zire 71, and Zire 72: These debugger nubs are available from the PluggedIn program at http://pluggedin.palmone.com"; Well, no, they aren't! I could find debugger nubs only for Tungsten C and Tungsten T3 there. And their description says "The debugger nub is the device-side code that the POD (Palm OS Debugger) uses to debug ARM code. The POD communicates with the debugger nub using the serial connection. The debugger nub helps the POD to set breakpoints, read/write memory/registers, single step, etc., in the ARM code." I don't want to debug the ARM code! My application is a 68K application, that's the level at which I want to debug. It's not a PNO; I'm not using any ARM-specific code. Then again the PalmOS documentation says to type some special shortcut on the device: "NOTE: To draw the debugging shortcut, follow these steps: 1. Draw the lowercase, cursive "L" character. 2. Tap the stylus twice, to generate a dot (a period). 3. Draw the number 2." Well, that doesn't make sense, either! First, in order to enter a lowercase L from the graffiti area, I draw a vertial line - nothing like the symbol that is shown in the documentation. Second, in order to enter a dot (period), I tap the stylus once - not twice. It seems that this documentation was written with the original Graffiti in mind - but Tungsten E uses Graffiti 2. OK, I draw the symbol shown on the picture, enter a dot and a 2, and hear three short beeps - but nothing more happens. The debugger doesn't connect to the device, either. So, could anybody please explain me how to do it? Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
