Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dev [2024/05/03 21:07] – [Current TailCoNTROL Release] darkgrue | en: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: | Resources for developers and hackers! Also don't forget about resources like the [[en: | ||
- | ===== Current | + | ===== Current |
- | The initial release of the new unified firmware, | + | The initial release of the new unified firmware, |
- | * The current version of TailCoNTROL | + | * The current version of TailControl |
- | * [[Release | + | * [[en: |
+ | * [[en: | ||
+ | * [[en: | ||
- | ==== Command Protocols ==== | ||
- | * [[en: | + | ==== Legacy Product |
- | * [[en: | + | |
- | **Legacy Products** | + | |
- | | + | * [[en: |
- | * [[en: | + | * [[en: |
Line 31: | 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: | + | If you need to test an experimental firmware or update outside the official CRUMPET app, there is a facility to update over BLE. |
+ | |||
+ | * [[en: | ||
+ | * [[https:// | ||
**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 38: | 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 | ||
The [[https:// | The [[https:// | ||
Line 48: | 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:// | ||
==== Chat With the Tail Co Development Team Community ==== | ==== Chat With the Tail Co Development Team Community ==== | ||
- | MiTail, EarGear 2, FlutterWings, | + | MiTail, EarGear 2, FlutterWings, |