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.
I run into a strange problem in Keil 7.01 When I link my program using the BL51 linker everything is OK and I can debug my application both in simulation and on the real target. 'Run till main' works OK in both modes. When I link the same program with LX51 I can only debug in simulation mode but not on the actual hardware. With the actual hardware 'Run till main' does not break at main. Debugging in assembly window is possible, including single stepping. But setting breakpoints in one of the C-files does not work. uVision does not allow me to set any breakpoint anywhere within the C-file. The instructions executed when single stepping on the real hardware are properly executed. (My LEDs get turned on). It looks like the debugger does not know anymore that the c-file was the original source of the code running in the Triscend device. Anybody any ideas? Best regards, Cor
Back on-site, I've just checked my Projects and I am using LX51 and the target debugging works fine for me. However, that's with uVision v2.23 and C51 v6.23a FastChip version 2.3.0; te5uv2.dll version 2.3.0.0. On Win-NT4.