• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 21 subscribers
  • Views 4076 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
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

Problem using J-Link while debugging

Stefan Hartwig

Hi,
I have an AT91SAM9260 and use a segger J-Link for HW-debugging. The problem is, that debugging does only work on every second time.
That means, if I want to debug, I click onto start/stop debugging, wait for the debugger to load the code into external RAM and then the program counter is somewhere in the program but the main or I get an error "cannot stop arm device".
On the second try (after I switch off and on power of the device) debugging works fine.

Parents
  • 0 in reply to Thorsten de Buhr

    Hi,
    yes, we work with adaptive clocking. Otherwise we would have to use a very slow frequency for JTAG, because the device starts with some 100kHz and speeds up JTAG frequency afterwards.

    We had a device (same µC but different design), where the "adaptive clocking pin" was not connected to the JTAG-port... it took some minutes to load the firmware to SD-Ram and debugging was slow as a snail

Reply
  • 0 in reply to Thorsten de Buhr

    Hi,
    yes, we work with adaptive clocking. Otherwise we would have to use a very slow frequency for JTAG, because the device starts with some 100kHz and speeds up JTAG frequency afterwards.

    We had a device (same µC but different design), where the "adaptive clocking pin" was not connected to the JTAG-port... it took some minutes to load the firmware to SD-Ram and debugging was slow as a snail

Children