We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Level 10: Rearrange Code; Level 11: Reuse of Common Exit Code. Does anyone have any experience of these higher optimisation levels, relying on the LX51 Linker? This thread reported some bugs, and expressed some misgivings about the advantages: http://www.keil.com/forum/docs/thread2094.asp That was v7.02; now we're at v7.07a: Can anyone confirm that the bugs are really fixed now? Does it do any better now? Any other plaudits, Gotchas! or concerns?
Yes, i have the same problem, debuggging a packed program make some problem to follow the right progression in the source code... But, to debug on the target the better thing is to disable packing (optimize 9), and after the debug session then just re-enable it, and check that all is good with it ( i never had a surprise... ) Christophe. (For me the debugger is keil debbugger with Triscend TE5UV2.DLL).
Out of interest, which debugger do you use? Seehau (the one that comes with the Nohau ICE). I also got some mileage out of uVision for some of the modules that aren't hardware-specific. Oh, and printf(), of course ;) Unfortunately, I can't turn off optimization for debugging, because the project would cease to fit! It's actually interesting at times single-stepping through the code and seeing what the optimizer chose to do. I learned a few 8051 coding tricks that way.