Merge branch 'main' into develop

selfcustody · Jan 17, 2025 · db97db0 · db97db0
2 parents 824e8ee + 782a1d2
commit db97db0
Show file tree

Hide file tree

Showing 7 changed files with 35 additions and 17 deletions.
diff --git a/docs/getting-started/features/tools.en.md b/docs/getting-started/features/tools.en.md
@@ -27,40 +27,37 @@ Enter text to create, print or transcribe a QR code that can later be used as an
 
 <div style="clear: both"></div>
 
-### Descriptor Addresses
+### Descriptor Addresses (Wallet Sans Key)
+<img src="../../../img/maixpy_m5stickv/descriptor-addresses-125.png" align="right">
+<img src="../../../img/maixpy_amigo/descriptor-addresses-150.png" align="right">
 
 Verify if an address or list of addresses belong to a wallet without needing to load private keys. Simply load a trusted wallet descriptor from a QR code or SD card.
 
 <div style="clear: both"></div>
 
 ### Flash Tools
-Tools to inspect the content of device's flash memory and clear user's area
-
 <img src="../../../img/maixpy_m5stickv/flash-tools-125.png" align="right">
 <img src="../../../img/maixpy_amigo/flash-tools-150.png" align="right">
 
+Tools to inspect the content of device's flash memory and clear user's area.
+
 <div style="clear: both"></div>
 
 #### Flash Map
+<img src="../../../img/maixpy_m5stickv/flash-map-125.png" align="right">
+<img src="../../../img/maixpy_amigo/flash-map-150.png" align="right">
+
 Flash map indicates which memory blocks (4086 Bytes each) are empty. Memory is separated in two regions: Firmware and User's Data. White or colored blocks contain data, while grey blocks are empty.
 
 This is an interesting tool to visualize the effects of filling the memory with ramdom entropy, what is done during the setup of a new `TC Code`, used with `TC Flash Hash` tool, described below.
 
-<img src="../../../img/maixpy_m5stickv/flash-map-125.png" align="right">
-<img src="../../../img/maixpy_amigo/flash-map-150.png" align="right">
-
 <div style="clear: both"></div>
 
 #### TC Flash Hash
-*Tamper Check Flash Hash* is a tamper detection mechanism that enables you to verify if the flash memory content has been altered. To use it first, need to create a `TC Code` on `Settings -> Security -> Tamper Check Code`.
-*TC Flash Hash* will hash this code, K210 chip's unique ID and the content of the whole flash memory together and produce an image.
-The tool generates a unique image and four tamper detection words based on a hash of your *TC Code*, the device's UID, and the flash content. The flash memory is divided into two regions:
-
-- **Firmware Region:** Generates the image and the first two words.
+*Tamper Check (TC) Flash Hash* is a tamper detection mechanism that enables you to verify if the flash memory content has been altered. To use it first, need to create a *Tamper Check (TC) Code* on `Settings -> Security -> Tamper Check Code`.
+*TC Flash Hash* will hash *TC Code*, K210 chip's unique ID and the content of the whole internal flash creating a tamper indicator that is unique to each device, represented by a memorable image and two sets of two words.
 
-- **User's Region:** Generates the last two words.
-
-Learn more about *Tamper Check Flash Hash* on [Tamper Detection](tamper-detection.md)
+More information on [Tamper Detection page](tamper-detection.md).
 
 #### Erase User's Data
 <img src="../../../img/maixpy_m5stickv/erase-data-125.png" align="right">
@@ -70,7 +67,6 @@ This option permanently removes all stored encrypted mnemonics, settings and `TC
 
 <div style="clear: both"></div>
 
-
 ### Remove Mnemonic
 <img src="../../../img/maixpy_m5stickv/load-mnemonic-storage-options-125.png" align="right">
 <img src="../../../img/maixpy_amigo/load-mnemonic-storage-options-150.png" align="right">
@@ -80,3 +76,5 @@ This option allows you to remove any stored encrypted mnemonic from the device's
 When mnemonics are removed from the device's flash memory, Krux will no longer be able to access them. However, as with most operating systems, the data may still be recoverable using specialized tools. If you stored any important keys with a [weak encryption key](https://www.hivesystems.com/blog/are-your-passwords-in-the-green), it is recommended to use the "Wipe Device" feature below to ensure that the data is irrecoverable.
 
 When mnemonics are removed from an SD card, Krux will overwrite the region where the encrypted mnemonic was stored with empty data. This makes it more secure to delete mnemonics from SD cards using Krux rather than a PC or another device. However, Krux does not have a "Wipe" feature for SD cards; you can find this feature in third-party applications.
+
+<div style="clear: both"></div>
diff --git a/docs/getting-started/usage/video-tutorials.en.md b/docs/getting-started/usage/video-tutorials.en.md
@@ -67,11 +67,15 @@ Faça sua hardware wallet em casa com a KRUX! - por Caiovski
 
 ### Korean
 
-Krux 월렛 설치 및 검증 방법
+#### 비트코인 지갑 만들기(셀프커스터디 AtoZ)
+[![비트코인 지갑 만들기(셀프커스터디 AtoZ)](https://img.youtube.com/vi/NTsZCHbQXgc/0.jpg)](https://www.youtube.com/playlist?list=PLetYvN5q3ZS9m1sf7_MJ1It-t8O87xEeB)
+
+
+#### Krux 월렛 설치 및 검증 방법
 
 [![Krux 월렛 설치 및 검증 방법](https://img.youtube.com/vi/7H1bI0A2y0w/0.jpg)](https://www.youtube.com/watch?v=7H1bI0A2y0w)
 
 
-안사면 손해? 세상에서 가장 투명한 비트코인 전용 지갑
+#### 안사면 손해? 세상에서 가장 투명한 비트코인 전용 지갑
 
 [![안사면 손해? 세상에서 가장 투명한 비트코인 전용 지갑](https://img.youtube.com/vi/1_JSJ1uzPzQ/0.jpg)](https://www.youtube.com/watch?v=1_JSJ1uzPzQ)
diff --git a/docs/img/maixpy_amigo/descriptor-addresses-150.en.png b/docs/img/maixpy_amigo/descriptor-addresses-150.en.png
diff --git a/docs/img/maixpy_m5stickv/descriptor-addresses-125.en.png b/docs/img/maixpy_m5stickv/descriptor-addresses-125.en.png
diff --git a/docs/troubleshooting.en.md b/docs/troubleshooting.en.md
@@ -30,6 +30,10 @@ Your device should charge and turn on when connected to a USB-A port, even if it
 
 **USB-C:**
 
+#### WonderMV
+- WonderMV devices will not be detected or powered on when connected directly to USB-C output ports on computers or chargers. Please use a USB hub or a USB‑C–to–USB‑A adapter for proper detection and powering.
+
+#### Maix Amigo, Cube
 - If the device is turned off and connected to a USB-C port, it should turn on and start charging. You can turn it off again, and it will continue to charge.
 
 - If the device is already turned on and connected to a USB-C port, it may not charge or be recognized by the computer. In this case, turn off the device to initiate recognition and charging. Once turned off and reconnected, the device should restart, be recognized by the computer, and charging should be triggered by USB-C hosts.

diff --git a/simulator/generate-device-screenshots.sh b/simulator/generate-device-screenshots.sh
@@ -68,6 +68,7 @@ poetry run poe simulator --sequence sequences/tools-check-sd.txt  --sd --device
 poetry run poe simulator --sequence sequences/tools-create-QR.txt  --sd --device $device
 poetry run poe simulator --sequence sequences/tools-mnemonic.txt  --sd --device $device
 poetry run poe simulator --sequence sequences/tools-print-test-qr.txt  --sd --device $device
+poetry run poe simulator --sequence sequences/tools-descriptor-addresses.txt --sd --device $device
 poetry run poe simulator --sequence sequences/tools-flash.txt  --sd --device $device
 
 # Settings

diff --git a/simulator/sequences/tools-descriptor-addresses.txt b/simulator/sequences/tools-descriptor-addresses.txt
@@ -0,0 +1,11 @@
+include _wait-for-logo.txt
+
+# Navigate to Tools
+x3 press BUTTON_B
+press BUTTON_A
+
+# Descriptor Addresses
+x3 press BUTTON_B
+press BUTTON_A
+
+screenshot descriptor-addresses.png