mirror of
https://github.com/meshcore-dev/MeshCore.git
synced 2026-08-28 11:34:40 +00:00
deploy: 0679dbeffc
This commit is contained in:
liamcottle
+25
-26
@@ -1193,7 +1193,7 @@
|
||||
<a href="#67-q-my-rakt1000-exiao_nrf52-device-seems-to-be-corrupted-how-do-i-wipe-it-clean-to-start-fresh" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
6.7. Q: My RAK/T1000-E/xiao_nRF52 device seems to be corrupted, how do I wipe it clean to start fresh?
|
||||
6.7. Q: My RAK/T1000-E/xiao_nRF52/... device seems to be corrupted, how do I wipe it clean to start fresh?
|
||||
|
||||
</span>
|
||||
</a>
|
||||
@@ -2388,7 +2388,7 @@
|
||||
<a href="#67-q-my-rakt1000-exiao_nrf52-device-seems-to-be-corrupted-how-do-i-wipe-it-clean-to-start-fresh" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
6.7. Q: My RAK/T1000-E/xiao_nRF52 device seems to be corrupted, how do I wipe it clean to start fresh?
|
||||
6.7. Q: My RAK/T1000-E/xiao_nRF52/... device seems to be corrupted, how do I wipe it clean to start fresh?
|
||||
|
||||
</span>
|
||||
</a>
|
||||
@@ -3120,34 +3120,33 @@ Below are the instructions to flash firmware onto a supported LoRa device using
|
||||
<p><strong>A:</strong> The default Bluetooth pairing code is <code>123456</code></p>
|
||||
<h3 id="66-q-my-heltec-v3-keeps-disconnecting-from-my-smartphone-it-cant-hold-a-solid-bluetooth-connection">6.6. Q: My Heltec V3 keeps disconnecting from my smartphone. It can't hold a solid Bluetooth connection.</h3>
|
||||
<p><strong>A:</strong> Heltec V3 has a very small coil antenna on its PCB for Wi-Fi and Bluetooth connectivity. It has a very short range, only a few feet. It is possible to remove the coil antenna and replace it with a 31mm wire. The BT range is much improved with the modification.</p>
|
||||
<h3 id="67-q-my-rakt1000-exiao_nrf52-device-seems-to-be-corrupted-how-do-i-wipe-it-clean-to-start-fresh">6.7. Q: My RAK/T1000-E/xiao_nRF52 device seems to be corrupted, how do I wipe it clean to start fresh?</h3>
|
||||
<p><strong>A:</strong></p>
|
||||
<ol>
|
||||
<li>Connect USB-C cable to your device, per your device's instruction, get it to flash mode:<ul>
|
||||
<li>For RAK, click the reset button <strong>TWICE</strong></li>
|
||||
<li>For T1000-e, quickly disconnect and reconnect the magnetic side of the cable from the device <strong>TWICE</strong></li>
|
||||
<li>For Heltec T114, click the reset button <strong>TWICE</strong> (the bottom button)</li>
|
||||
<li>For Xiao nRF52, click the reset button once. If that doesn't work, quickly double-click the reset button twice. If that doesn't work, disconnect the board from your PC and reconnect again (<a href="https://wiki.seeedstudio.com/XIAO_BLE/#access-the-swd-pins-for-debugging-and-reflashing-bootloader">seeed studio wiki</a>)</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>A new folder will appear on your computer's desktop</li>
|
||||
<li>Download the <code>flash_erase*.uf2</code> file for your device on <a href="https://flasher.meshcore.io">https://flasher.meshcore.io</a><ul>
|
||||
<li>RAK WisBlock and Heltec T114: <code>Flash_erase-nRF32_softdevice_v6.uf2</code></li>
|
||||
<li>Seeed Studio Xiao nRF52 WIO: <code>Flash_erase-nRF52_softdevice_v7.uf2</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>drag and drop the uf2 file for your device to the root of the new folder</li>
|
||||
<li>Wait for the copy to complete. You might get an error dialog, you can ignore it</li>
|
||||
<li>Go to <a href="https://flasher.meshcore.io">https://flasher.meshcore.io</a>, click <code>Console</code> and select the serial port for your connected device</li>
|
||||
<li>In the console, press enter. Your flash should now be erased</li>
|
||||
<li>You may now flash the latest MeshCore firmware onto your device</li>
|
||||
</ol>
|
||||
<h3 id="67-q-my-rakt1000-exiao_nrf52-device-seems-to-be-corrupted-how-do-i-wipe-it-clean-to-start-fresh">6.7. Q: My RAK/T1000-E/xiao_nRF52/... device seems to be corrupted, how do I wipe it clean to start fresh?</h3>
|
||||
<p><strong>A: If you're able to connect to the device from your MeshCore app</strong>
|
||||
1. Navigate to Gear icon(Settings) on the upper right corner
|
||||
2. Click on <code>Export Settings</code> button, choose <code>Select All</code> and Confirm. This will save your Node configuration
|
||||
3. Now choose <code>Factory Reset</code> option
|
||||
4. Confirm that you want to reset your device
|
||||
5. Go to Bluetooth System settings and remove pairing of the device, so you can connect again
|
||||
6. Connect your device in the app and enter the PIN
|
||||
7. Navigate to Gear icon(Settings) on the upper right corner
|
||||
8. Click on <code>Import Settings</code> and choose the file from 2., click on <code>Select All</code> and Confirm
|
||||
9. Find <code>Reboot</code> button on of the Settings list</p>
|
||||
<p><strong>B: You're not able to connect to the App</strong>
|
||||
1. Connect USB cable to your device
|
||||
2. Go to https://flasher.meshcore.io
|
||||
3. Search for your device in the list
|
||||
4. Choose <code>Companion Bluetooth</code>
|
||||
5. Press <code>Enter DFU mode</code> button, choose your USB device
|
||||
6. Press <code>Erase Flash</code> button, choose the device again and wait until it completes
|
||||
7. Press <code>Flash!</code> button and choose the USB device last time
|
||||
8. The device is erased and newest firmware is installed
|
||||
9. You might need to remove the pairing in Bluetooth System Settings in order to re-pair the app again.</p>
|
||||
<p>Separately, starting in firmware version 1.7.0, there is a CLI Rescue mode. If your device has a user button (e.g. some RAK, T114), you can activate the rescue mode by holding down the user button of the device within 8 seconds of boot. Then you can use the 'Console' on <a href="https://flasher.meshcore.io">https://flasher.meshcore.io</a></p>
|
||||
<h3 id="68-q-webflasher-fails-on-linux-with-failed-to-open">6.8. Q: WebFlasher fails on Linux with failed to open</h3>
|
||||
<p><strong>A:</strong> If the usb port doesn't have the right ownership for this task, the process fails with the following error:</p>
|
||||
<p><code>NetworkError: Failed to execute 'open' on 'SerialPort': Failed to open serial port.</code></p>
|
||||
<p>Allow the browser user on it:</p>
|
||||
<p><code># setfacl -m u:YOUR_USER_HERE:rw /dev/ttyUSB0</code></p>
|
||||
<p>Allow user access on your USB port:</p>
|
||||
<p><code>sudo setfacl -m u:$USER:rw /dev/ttyUSB0</code></p>
|
||||
<hr />
|
||||
<h2 id="7-other-questions">7. Other Questions:</h2>
|
||||
<h3 id="71-q-how-to-update-nrf-rak-t114-seeed-xiao-companion-repeater-and-room-server-firmware-over-the-air-using-the-new-simpler-dfu-app">7.1. Q: How to update nRF (RAK, T114, Seeed XIAO) companion, repeater and room server firmware over the air using the new simpler DFU app?</h3>
|
||||
|
||||
File diff suppressed because one or more lines are too long
+13
-13
@@ -2,54 +2,54 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/cli_commands/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/companion_protocol/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/docs/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/faq/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/kiss_modem_protocol/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/nrf52_power_management/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/number_allocations/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/packet_format/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/payloads/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/qr_codes/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/stats_binary_frames/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/terminal_chat_cli/</loc>
|
||||
<lastmod>2026-08-14</lastmod>
|
||||
<lastmod>2026-08-24</lastmod>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user