diff --git a/Firmware/CoverUI/YardForce/README-MOD-YF-C500_RM-ECOW-V1.3.0.md b/Firmware/CoverUI/YardForce/README-MOD-YF-C500_RM-ECOW-V1.3.0.md index 006ad56..1294241 100644 --- a/Firmware/CoverUI/YardForce/README-MOD-YF-C500_RM-ECOW-V1.3.0.md +++ b/Firmware/CoverUI/YardForce/README-MOD-YF-C500_RM-ECOW-V1.3.0.md @@ -24,6 +24,10 @@ You might also simply bridge R34 and R42, but for me it was simpler to move them

(back to top)

+### ST-Link Headers (*mandatory*) +In case you do not have headers for ST-LINK connection, you should solder them also. + +[![Optional Rain Hardware Modification](images/IMG_Headers_500.png "Open in browser")](images/IMG_Headers_500.png) ### Rain Sensor (*optional*) diff --git a/Firmware/CoverUI/YardForce/README.md b/Firmware/CoverUI/YardForce/README.md index 027f3b4..eeb021b 100644 --- a/Firmware/CoverUI/YardForce/README.md +++ b/Firmware/CoverUI/YardForce/README.md @@ -83,12 +83,24 @@ You need an ST-Link programmer/debugger like this cheap *ST-Link (V2) clone*: My ST-Link (V2) clone + * Install stlink-tools (you need st-info to identify your board): e.g. `sudo apt install stlink-tools` + + * Unplug everything from you stock CoverUI PCB and connect your ST-Links GND, CLK, DIO and 3V3 to the same pins on the board. +Take special attention to hit the '3.3V' pin of your ST-Link!! + * Identify your board: Open a terminal/console, then: + + * `st-info --descr` should return either: + * `F0xx`, which identify your PCB's MCU as a 'STM32F030R8' (i.e. Classic 500) + * `F1xx Medium-density` or `STM32F1xx_MD` which identify a 'GD32F330R8' MCU (i.e. Classic 500) + * `F09X` identifies a 'STM32F030RC' MCU (i.e. SAxPRO Display) + + There're two generic ways to get the Firmware into your MCU.
Either you flash the binary directly, or you compile it by yourself with [PlatformIO](https://platformio.org/). -### Firmware binaries +### Firmware binaries -1. Goto [Releases](/releases) +1. Goto [Releases](/releases) // TODO links currently broken 2. Download `firmware-stock.zip` 3. Unpack it somewhere @@ -106,13 +118,7 @@ The file name syntax of the included firmware binaries is: `firmware__ +* simply:
`st-flash write firmware__[_, ...].bin 0x08000000` which should log at the end something like 'Flash written and verified! jolly good!' When done, re-plug your ST-Link and you should see a quick power-on animation. @@ -136,8 +142,11 @@ Now, try again flashing by: `st-flash write firmware__[_ - `Open Project` cloned repository branch -> CoverUI/Firmware/CoverUI (contains platformio.ini) - Wait till tools got loaded (bottom right status info) - In bottombar click `Switch PlatformIO Project Environment` and choose whatever MCU, MOD & programmer/debugger- probe you use +PlatformIO env - Wait till tools got loaded (bottom right status info) -- Finally press `PlatformIO: Upload` (right arrow symbol) in bottombar. After it compiled, linked and uploaded, it should reboot and do a short power-on LED animation. +- Finally press `PlatformIO: Upload` (right arrow symbol) in bottombar. +PlatformIO upload + When done, re-plug your ST-Link and you should see a quick power-on animation. - If you get an "Error: stm32x device protected", simply upload a second time. Look like I placed the "unlock" command some how to late. diff --git a/Firmware/CoverUI/YardForce/images/IMG_Headers_500.png b/Firmware/CoverUI/YardForce/images/IMG_Headers_500.png new file mode 100644 index 0000000..e69169d Binary files /dev/null and b/Firmware/CoverUI/YardForce/images/IMG_Headers_500.png differ diff --git a/Firmware/CoverUI/YardForce/images/PlatformIO_env.png b/Firmware/CoverUI/YardForce/images/PlatformIO_env.png new file mode 100644 index 0000000..d5203f2 Binary files /dev/null and b/Firmware/CoverUI/YardForce/images/PlatformIO_env.png differ diff --git a/Firmware/CoverUI/YardForce/images/PlatformIO_upload.png b/Firmware/CoverUI/YardForce/images/PlatformIO_upload.png new file mode 100644 index 0000000..b7ac92b Binary files /dev/null and b/Firmware/CoverUI/YardForce/images/PlatformIO_upload.png differ