Trace:

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:dev [2024/05/12 20:26] – [Command Protocols] darkgrueen:dev [2025/02/11 23:28] (current) – [Chat With the Tail Co Development Team Community] darkgrue
Line 4: Line 4:
 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! 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!
  
-===== Current TailCoNTROL Release =====+===== Current TailControl Release =====
  
-The initial release of the new unified firmware, TailCoNTROL is out! MiTail, MiTail Mini, and FlutterWings products can be updated by the CRUMPET app. +The initial release of the new unified firmware, TailControl is out! MiTail, MiTail Mini, and FlutterWings products can be updated by the CRUMPET app.  
 + 
 +  * The current version of TailControl is **v5.0.9** 
 +  * [[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)
  
-  * The current version of TailCoNTROL is v5.0.8. 
-  * [[Release notes for v5.0.8]]. 
  
  
Line 15: Line 18:
 ==== Legacy Product Command Protocols ==== ==== Legacy Product Command Protocols ====
  
-  * [[en:dev:eargear-v2-protocol|v2 Ear Command Protocol]]\\ +  * [[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]]
-  * [[en:dev:digitail-command-protocol|DIGITAiL Command Protocol]]\\  +
-  * [[en:dev:eargear-v1-protocol|v1 Ear Command Protocol]]\\+
  
  
Line 30: Line 31:
 ==== Using OTA ==== ==== 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. **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.
Line 37: Line 41:
 ==== Hardware Flash ==== ==== 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.+=== Tail-series Boards === 
 + 
 +Hardware flash for the MiTail, MiTail Mini, and FlutterWings 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 [[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.
Line 47: Line 53:
 **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. **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.
  
 +=== EarGear Boards ===
  
 +EarGear 2 can be hardware flashed using the USB-C port on the ears and a PC running Chrome or Edge using the [[https://www.gue-tech.org/esp-web-tools/|TailControl ESP Web Tools]].
 ==== Chat With the Tail Co Development Team Community ==== ==== Chat With the Tail Co Development Team Community ====
  
-MiTail, EarGear 2, FlutterWings, and MiTail Mini all have updatable firmware! For details, come and talk to us on our Telegram [[https://t.me/+5XsaunrTpIc4OWI8|Tail Co Dev Chat]]!+MiTail, EarGear 2, FlutterWings, and MiTail Mini all have updatable firmware! For details, come and talk to us on our Telegram [[https://t.me/+5XsaunrTpIc4OWI8|Tail Co Gear Dev Chat]]!
Back to top