This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LX51 + Debugging Triscend TE5

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

  • Are you sure that the debug info didn't accidentally get turned off when you switched to LX51?

    I have heard it said that taking an existing BL51 project and just checking the 'Use LX51' box may not correctly retain all the other required options.
    http://www.keil.com/forum/docs/thread1481.asp
    Have you tried creating the Project again from scratch, using only LX51 from the outset?

    Did you change anything else at the same time - FastChip? the te5uv2.dll?

  • "It looks like the debugger does not know anymore that the c-file was the original source of the code"

    Another thought:
    You haven't changed to using the SRC directive?

    BTW: The project.uv2 and project.opt files are just plain, unformatted ASCII text - so you can use your favourite text-comparison utility to spot any differences.

  • Andrew,

    No, debug info was not switched off. I checked it. Further I know for sure that nothing else changed at the same time.

    The strange this is that when simulating the LX51 linked version of my SW everything works OK. Only on the real target uVision looses track of the C-source.

    This behaviour is not observed when using the BL51 linker.

    I'll try to generate a new project later today. I'll inform this forum about the results.

    Cor

  • Adrew,

    No I did not switch to the SRC directive. I even wonder why I should possibly want that.


    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.