Differences

This shows you the differences between two versions of the page.

--- en:dev [2024/03/16 19:22] – [Dev Fiesta] darkgrue
+++ en:dev [2024/06/28 15:54] (current) – [Current TailCoNTROL Release] darkgrue
@@ Line 2: / Line 2: @@
 ====== Dev Fiesta ======
-Resources for developers and hackers! Also don't forget about resources like the [[en:manuals:service-notes-for-mitail|Service Notes for MiTail]] in the [[en:manuals|Guides, Patterns, and Safety Info]] section!
+Resources for developers and hackers! Also don't forget about resources like the [[en:manuals:service-notes-for-mitail|Service Notes for MiTail]] in the [[en:man_overview|Guides, Patterns, and Safety Info]] section!
-==== Command Protocols ====
+===== Current TailCoNTROL Release =====
-  * [[en:dev:digitail-command-protocol|DIGITAiL Command Protocol]]\\
+The initial release of the new unified firmware, TailCoNTROL is out! MiTail, MiTail Mini, and FlutterWings products can be updated by the CRUMPET app.
-  * [[en:dev:tailcontrol-command-protocol|TailCoNTROL Command Protocol]]\\
-  * [[en:dev:eargear-v1-protocol|v1 Ear Command Protocol]]\\
+  * The current version of TailCoNTROL is **v5.0.9**
-  * [[en:dev:eargear-v2-protocol|v2 Ear Command Protocol]]\\
+  * [[en:dev:tailcontrol-release-notes|TailCoNTROL Release Notes]]
+  * [[en:dev:tailcontrol-command-protocol|TailCoNTROL Command Protocol]]
+  * [[en:dev:tailcontrol-breaking-changes|TailCoNTROL Breaking Changes]] (for app developers)
+==== Legacy Product Command Protocols ====
+  * [[en:dev:digitail-command-protocol|DIGITAiL Command Protocol]]
+  * [[en:dev:eargear-v1-protocol|v1 Ear Command Protocol]]
+  * [[en:dev:eargear-v2-protocol|v2 Ear Command Protocol]]
@@ Line 20: / Line 31: @@
 ==== Using OTA ====
-If you need to test an experimental firmware or update outside the official CRUMPET app, there is a [[en:dev:ota|facility to update over BLE]].
+If you need to test an experimental firmware or update outside the official CRUMPET app, there is a facility to update over BLE.
+  * [[en:dev:ota|BLE_OTA_Python script]]
+  * [[https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/ota.html|API Reference: Over The Air Updates (OTA)]]
 **Note:** flashing test firmware or the incorrect firmware for your product can make it impossible to recover without a hardware flash, which may require return for service. You should only perform this operation **at your own risk**, and only if you are comfortable with all the steps and components used to perform it. You also need to have a recovery plan and be prepared to hardware flash if something goes wrong.
+==== Hardware Flash ====
+Hardware flash can be performed with a 3.3 V USB to TTL interface that provides RXD, TXD, RTS (Ready to Send), and DTR (Data Terminal Ready) signals (i.e., a 6-pin connector with the appropriate signals). Numerous inexpensive USB to TTL cables and interfaces are not capable of doing this, check carefully before investing in a tool to perform this.
+The [[https://1bitsquared.com/products/tigard|Tigard Protocol Tool]] works very nicely, though it is massively overkill in that it has many more capabilities than are required.
+The interface pinout on the board is below. Pins are numbered counting from Pin 1, closest to the servo connector, on the component side of the controller board.
+{{ :en:esp32_uart0_connections.jpg?direct&400 |ESP32 UART0 Connections}}
+**Note:** USB to TTL interfaces are available with 5 V, 3.3 V, or selectable voltage. The ESP32 //must// be used with 3.3 V interfaces //only//! Ensure that your cable or device is configured for 3.3 V before connecting it to the controller board, or your ESP32 may be permanently damaged.