Skip to content

Update debugger tutorial for Arduino IDE >=2.0.3 #709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Dec 7, 2022
Merged

Update debugger tutorial for Arduino IDE >=2.0.3 #709

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
1065764
Update "J-Link GDB Server" path in IDE 2.x debugger tutorial
per1234 Dec 5, 2022
ded6025
Clean up formatting of example `debug_custom.json` file in IDE 2.x de…
per1234 Dec 5, 2022
154c713
Use command line version of "J-Link GDB Server" in example configurat…
per1234 Dec 5, 2022
90d1203
Provide filename of "J-Link GDB Server" for each OS in IDE 2.x debugg…
per1234 Dec 5, 2022
c99daed
Correct line numbers referenced in breakpoint section of IDE 2.x debu…
per1234 Dec 5, 2022
c9ede0e
Update breakpoints section of IDE 2.x debugger tutorial to reflect ne…
per1234 Dec 5, 2022
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Correct line numbers referenced in breakpoint section of IDE 2.x debu… 
…gger tutorial The screenshots included with the tutorial show breakpoints were placed at lines 33 and 35, yet the text is written as though the second breakpoint is at line 36. Since it is easier to update the text, and since line 35 is a more logical place for the breakpoint, the text is corrected.
  • Loading branch information
@per1234
per1234 committed Dec 5, 2022
commit c99daedfeb51acaf0fe4aec22af8de59918b7208
4 changes: 2 additions & 2 deletions content/software/ide-v2/tutorials/ide-v2-debugger/ide-v2-debugger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,14 +102,14 @@ Once your program has been uploaded, we can start using the debugger.

Let's begin by creating something called a **breakpoint**. Breakpoints are used to stop the program execution at a specific line (or when a specific condition is verified). We can use multiple of these in a program (the number is variable depending on the processor).

In this example, we are going to set a breakpoint for **line 33** and **line 36**. These are set by clicking to the left of the line numbering in the editor.
In this example, we are going to set a breakpoint for **line 33** and **line 35**. These are set by clicking to the left of the line numbering in the editor.

![Navigating the Debugger.](assets/debugger-img03.png)

We can now go through our code, step by step.
The first (automatic) stop will be triggered by the **Debugger** itself, and it will be a standard entry-point, ignore that for now.

Let's continue, by clicking on the **Play/pause** button (**Continue**). The program will now run to the first breakpoint, line 33. If we click it again, it will jump to line 36 (the lines 34 and 35 will still be executed but we won't see that). Clicking the **Play/pause** button again will continue running the program which will pause at its next breakpoint, line 33. We're in the main loop, after all.
Let's continue, by clicking on the **Play/pause** button (**Continue**). The program will now run to the first breakpoint, line 33. If we click it again, it will jump to line 35 (line 34 will still be executed but we won't see that). Clicking the **Play/pause** button again will continue running the program which will pause at its next breakpoint, line 33. We're in the main loop, after all.

![Going between breakpoints.](assets/playpause.gif)

Expand Down