Search Results
Search results 1-5 of 5.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Monitor mode debugging does not fit the application. The intention is to have a failsafe way independent of software to toggle an I/O pin from a host when the chip being debugged is halted. We have given it some more thought, and based on the fact that debugging on Cortex M devices is based on polling the CPU from the debug probe, "timing can't be guaranteed". However, there is more to that story, and I think it also feeds in to how the JLINK debug mechanism is implemented. Here is my investigat…
-
This may be possible or information available elsewhere, but I don't want to go sifting through the gobs of posts and would rather just ask directly. I have performed a rudimentary search already. Our company has a use case where we are debugging an MCU using JLINK and we would like to manipulate GPIO pins of the debugger port when the JLINK halts the MCU or exits halt and goes into run. Looking at the scripting interface, something like OnBeforeHalt, OnAfterHalt, OnBeforeExitHalt, OnAfterExitHa…
-
So we finally got the macro file working with jlink GDB using eclipse and were able to specify the search ranges. We really want to make usage of the RTT viewer though. The RTT viewer as it is now takes no command line parameters. If this program was able to run from the command line that might be an easier alternative. Basically on the command line you could specify the CPU, jlink connection, memory address search range, etc.. Everything that requires user input via the popup on the UI when you…
-
Having multiple banks searched would be very useful. If we manually have to set the address range, this becomes a requirement on our end user to put in the custom command while debugging. This is not ideal, so we would appreciate the ability for the entire RAM memory to be searched based on the selected MCU.
-
Hello: Our company has just started to use the RTT functionality of the JLink for terminal output. I have two issues that hopefully have answers and are not super hard to solve. We have tried fiddling with RTT for the past day or so. First question: We are using an STM32L476 with 128K RAM. There are two RAM banks: one starts at 0x10000000 (32K) the other starts at 0x20000000 (96K). When the JLink server starts up and we click the RTT tab and start it, the GDB server runs its scan process to try …