Skip to content

Commit 78ff718

Browse files
authored
General improvements (#56)
1 parent f05b2a4 commit 78ff718

File tree

261 files changed

+52794
-124
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

261 files changed

+52794
-124
lines changed

README.md

Lines changed: 26 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ It makes use of several 3rd party tools:
1616
You can find the esptool and licensing information on the repository [here](http://github.com/espressif/esptool).
1717
- QMKDfuSe
1818
Tool based on STM DfusSe tool. You can find the source, licensing information and documentation [here](https://github.com/qmk/qmk_dfuse).
19-
- ST-LINK Utility
20-
You can find the source, licensing information and documentation [here](https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/stsw-link004.html).
19+
- STM32 Cube Programmer
20+
You can find the source, licensing information and documentation [here](https://www.st.com/en/development-tools/stm32cubeprog.html).
2121
- Texas Instruments Uniflash
2222
You can find the Uniflash tool and licensing information [here](http://www.ti.com/tool/download/UNIFLASH).
2323

@@ -29,17 +29,11 @@ Perform a one-time install of the .NET **nanoFramework** Firmware Flasher tool u
2929
dotnet tool install -g nanoff
3030
```
3131

32-
In case you're installing a pre-release version of the tool you have to specify the version number and the .NET **nanoFramework** Azure DevOps NuGet feed as the source. Like this:
33-
34-
```console
35-
dotnet tool install -g nanoff --version 9.9.9-preview.100
36-
```
37-
3832
After a successful installation a message is displayed showing the command that's to be used to call the tool along with the version installed. Similar to the following example:
3933

4034
```console
4135
You can invoke the tool using the following command: nanoff
42-
Tool 'nanoff' (version '9.9.9-preview.100') was successfully installed.
36+
Tool 'nanoff' (version '9.9.9') was successfully installed.
4337
```
4438

4539
## Update .NET **nanoFramework** Firmware Flasher
@@ -94,10 +88,10 @@ nanoff --update --target ESP32_WROOM_32 --serialport COM31 --deployment "c:\eps3
9488

9589
### Update the firmware of a specific STM32 target
9690

97-
To update the firmware of the NETDUINO3_WIFI target to the latest available stable version.
91+
To update the firmware of the ST_STM32F769I_DISCOVERY target to the latest available stable version using the JTAG connection.
9892

9993
```console
100-
nanoff --update --target NETDUINO3_WIFI --stable
94+
nanoff --update --target ST_STM32F769I_DISCOVERY --jtag
10195
```
10296

10397
### Deploy a managed application to a ST_STM32F769I_DISCOVERY target
@@ -112,12 +106,12 @@ nanoff --target ST_STM32F769I_DISCOVERY --deploy --image "E:\GitHub\nf-Samples\s
112106

113107
### Update the firmware of a ST_STM32F769I_DISCOVERY along with a managed application
114108

115-
To update the firmware of the ST_STM32F769I_DISCOVERY target to the latest available preview version along with a managed application.
109+
To update the firmware of the ST_STM32F769I_DISCOVERY target to the latest available preview version, using a JTAG connection, along with a managed application.
116110
You have to specify the path to the managed application.
117111
This example uses the binary format file that is generated by Visual Studio when building any nanoFramework C# application. Because it's a binary file you have to specify too the flash address of the deployment region (here 0x08000000, mind the hexadecimal format).
118112

119113
```console
120-
nanoff --update --target ST_STM32F769I_DISCOVERY --binfile "c:\dev\my awesome app\bin\debug\my_awesome_app.bin" --address 0x08000000
114+
nanoff --update --target ST_STM32F769I_DISCOVERY --preview --jtag --binfile "c:\dev\my awesome app\bin\debug\my_awesome_app.bin" --address 0x08000000
121115
```
122116

123117
### List all STM32 devices available with JTAG connection
@@ -136,20 +130,36 @@ This useful to list all STM32 devices that are connected through DFU.
136130
nanoff --listdfu
137131
```
138132

133+
### Install STM32 JTAG drivers
134+
135+
To install the drivers for STM32 JTAG connected targets.
136+
137+
```console
138+
nanoff --installjtagdrivers
139+
```
140+
141+
### Install STM32 DFU drivers
142+
143+
To install the drivers for STM32 DFU connected targets.
144+
145+
```console
146+
nanoff --installdfudrivers
147+
```
148+
139149
### Update the firmware of a specific TI CC13x2 target
140150

141-
To update the firmware of the TI_CC1352R1_LAUNCHXL target to the latest available stable version.
151+
To update the firmware of the TI_CC1352R1_LAUNCHXL target to the latest preview version.
142152

143153
```console
144-
nanoff --update --target TI_CC1352R1_LAUNCHXL --stable
154+
nanoff --update --target TI_CC1352R1_LAUNCHXL --preview
145155
```
146156

147157
### Install the XDS110 USB drivers required by TI LaunchPad targets
148158

149159
To install the XDS110 USB drivers.
150160

151161
```console
152-
nanoff --platform cc13x2 --installdrivers
162+
nanoff --installxdsdrivers
153163
```
154164

155165
### Tool output verbosity
14.9 KB
Binary file not shown.

0 commit comments

Comments
 (0)