You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# Open Flash loader template (OFL)
2
-
Flash loader template without the need for a Keil/Segger DSK license. OFL uses Cmake and arm-none-eabi to build. OFL uses parts of [klib](https://github.com/itzandroidtab/klib/)
2
+
Flash loader template without the need for a Keil/Segger DSK license. OFL uses cmake and arm-none-eabi to build. OFL uses parts of [klib](https://github.com/itzandroidtab/klib/)
3
3
4
4
## Create a Flash loader executable
5
5
To create a OFL executable you need the following:
@@ -11,7 +11,7 @@ To create a OFL executable you need the following:
11
11
Note: When using the flash loader no startup code will run. Make sure to initialize any (non const) static and global variables at runtime as they will not be initialized when loading the flash loader.
12
12
13
13
## Stack usage
14
-
In the previous documentation Segger reserved 256 bytes of stack for Open flash loaders. In newer versions the documentation mentions 512 bytes of stack with a fallback to 256 bytes for devices with low amounts of memory (for testing, the linkerscript configures 256 bytes of stack).
14
+
In the previous documentation Segger mensioned they reserve 256 bytes of stack for Open flash loaders. In newer versions the documentation mentions 512 bytes of stack with a fallback to 256 bytes for devices with low amounts of memory (for testing, the linkerscript configures 256 bytes of stack).
15
15
16
16
## Create a flash loader xml file
17
17
SEGGER J-Link uses xml files to add support for external loaders. The xml file configures the follwing:
0 commit comments