Re: Download Problems CW6

[Adam Barna]

I also actually had a similar problem which disturbs be because the fix was illogical. My main segment was nearing 32k, and all of a sudden everytime I did a hotsync I would have to hard reset the device and delete the user on the desktop for me to be able to sync again. I thoguht that breaking up my program into multiple segments would help, but it didn't. After going back to previous versions and bringing in the changes line by line I found out that this happened when my myPalmMain() (which is simply called by PilotMain() and handles the launch command) had certain lines of code. This code was not special in any way, but when it was in, sychronization would crash, and when out it wouldn't. The strange thing is that my program has grown massively since I moved that code to another function, but I haven't had any problems with code outside of myPalmMain(). Is the problem positively that the code tries to access something too far away? My segment was not that large so I don't see why this would happen.

I'm using CodeWarrior 8.3 on windows xp with the latest pose 3.5

On a side note... does anyone know a way to make the CodeWarrior debugger faster? I've used it on two machines (winxp and win2k), and with both of them, for the debugger to go to the next line of code when i break can take forever. Sometimes it just never goes to the next line of code, and I have to restart debugging, but even if it does it takes a very long time.

thanks
-adam

Ben Combee wrote:

At 09:30 2002-11-6 -0800, you wrote:

all segments, AS LOADED (emphasis added), must be a bit smaller than 65,535 bytes. Note that Codewarrior reports inaccurate values for segment sizes and that the linker doesn't fatal error on segments too large. You only see the errror on download.

This is only true in CW for Palm OS R6 or earlier -- V7 added a check that tells you when a segment grows too large, but its only enabled if you have linker warnings enabled. The segment sizes in the project window are inaccurate, but the sizes reported in the map file are correct. This is because the project sizes are based on the compiler, not on what actually gets linked into each segment, which can be smaller after unused code removal.

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