Skip to content

Commit 6afe72f

Browse files
authored
Merge branch 'main' into patch-5
2 parents 88b1bef + 65ec747 commit 6afe72f

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

docs/configure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,7 +208,7 @@ added to the `launch.json` file:
208208

209209
### Single-core (J-Link)
210210

211-
For a single-core device, the configuration template contains all the information that is requires to start debugging.
211+
For a single-core device, the configuration template contains all the information that is required to start debugging.
212212

213213
!!! Attention
214214
**Check if the above statement is true!**
@@ -278,4 +278,4 @@ For this example, the content of the `JLinkDevices.xml` file is as follows:
278278
<ChipInfo Vendor="AlifSemiconductor" Name="AE722F80F55D5_HE" Aliases="AE722F80F55D5LS_M55_HE; AE722F80F55D5AS_M55_HE" />
279279
</Device>
280280
</DataBase>
281-
```
281+
```

docs/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ create the debug environment and is shipped with [pyOCD](https://pyocd.io/) and
66

77
The following extensions are included in this extension pack:
88

9-
- [CDT™ GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode), an Eclipse CDT.cloud extension that supports debugging using GDB and any other debuggers that supports the MI protocol.
9+
- [CDT™ GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode), an Eclipse CDT.cloud extension that supports debugging using GDB and any other debuggers that support the MI protocol.
1010

1111
- [Memory Inspector](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.memory-inspector), an Eclipse CDT.cloud extension that provides a powerful and configurable memory viewer that works with debug adapters.
1212

docs/setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ To be able to use the GNU Debugger under the hood, you need to make sure that th
5050
binary files in the correct formats. Thus, you need to amend your project's `*.csolution.yml` and `*.cproject.yml` files.
5151

5252
- Make sure that the [ELF](https://developer.arm.com/documentation/dui0101/latest/) file is written using the
53-
[DWARF Verion 5](https://dwarfstd.org/dwarf5std.html) format. For example, when generated with the
53+
[DWARF Version 5](https://dwarfstd.org/dwarf5std.html) format. For example, when generated with the
5454
[Arm Compiler for Embedded](https://developer.arm.com/Tools%20and%20Software/Arm%20Compiler%20for%20Embedded), add the
5555
following to your `*.csolution.yml` file (before the `projects:` section for example):
5656

@@ -66,7 +66,7 @@ binary files in the correct formats. Thus, you need to amend your project's `*.c
6666
```
6767
6868
!!! Note
69-
For other toolchians, please consult the reference manual on how to generate DWARF Version 5 formatted ELF files.
69+
For other toolchains, please consult the reference manual on how to generate DWARF Version 5 formatted ELF files.
7070
7171
- In addition to generating an ELF file, you also need to create a [HEX](https://developer.arm.com/documentation/ka003292/latest/)
7272
file that will be used to flash the firmware image. Add the following to any of your `*.cproject.yml` files (at the end of

0 commit comments

Comments
 (0)