GUOXD V1 · FIRMWARE UPDATE
Your files.
Your next update.
Manage your Guoxd V1 files, verify transfers, and test the matched firmware candidate.
File management is available for user testing. The owner reports successful wired installation and normal Bluetooth file transfer on their device; this website and BLE firmware updates still need hardware acceptance. PCB revision is unknown.
01 / YOUR BROWSER
Ready to connect?
Bluetooth availability depends on your browser, operating system, adapter and permissions. Use HTTPS or localhost.
02 / YOUR PACKAGE
Look inside the update.
Choose a Nordic DFU ZIP to check its structure, image files and integrity. Processing stays in this browser.
No package selected.
- Package SHA-256
03 / DEVICE FILES
Your device, organized.
Open the HTTPS site directly in a browser with Web Bluetooth support.
Enter Bluetooth transfer on your device, then connect.
MTU is unknown. Downloads and large directories can require complete 247-byte notifications. A small successful transfer does not establish large-transfer compatibility. Uploads use conservative 15-byte chunks and are verified by downloading the device contents. Directory EOF cannot distinguish every storage error; compare large listings with your expected inventory.
Logs include file paths, metadata and the Bluetooth address. Review them before sharing.
Drop files here after opening a device folder, or use Upload.
| Select | Name | Size | Type | Remark |
|---|
No device commands have been sent.
04 / FIRMWARE TEST
A matched candidate. A deliberate test.
Guoxd_r1 · application only · display version 2.16.1-c1 · internal version 21601. This reinstalls the same application. Production approval: false. Wireless installation has not passed hardware acceptance.
Choose the original Guoxd_V1_Guoxd_r1_app_21601_BLE_DFU_TEST_CANDIDATE.zip from your engineering handoff. The Windows/SWD ZIP cannot be used here.
Candidate ZIP
No candidate verified.
Verify the candidate and confirm the sample test scope first.
The device is selected again after entering DFU. Only device-confirmed CRC progress is shown. A full bar, final disconnect or unchanged version does not prove successful installation. Reconnect in normal mode and complete the file and device regression checks.
Before you begin
What does the package check prove?
It checks ZIP integrity, the Nordic manifest, referenced image and initialization files, and SHA-256 hashes. It does not authenticate the publisher, verify the firmware signature or establish hardware compatibility. Only compare hashes with a trusted release source.
Where is my file stored?
The inspector reads it in browser memory. This app has no upload endpoint or analytics. Clear the file or close the page to discard the in-memory report. A downloaded report contains filenames and checksums, not firmware bytes.
What is the firmware test scope?
The exact Guoxd_r1 protocol and signed candidate have been reviewed offline. Ordinary file operations are available for user testing. Firmware installation is limited to the explicitly confirmed sample and exact allowlisted package; physical BLE DFU acceptance remains pending.
What if Bluetooth is unavailable?
Try a current Chrome or Edge browser on a supported system, enable your Bluetooth adapter, and use the secure site directly. Browser support alone does not guarantee that a device will appear. Package inspection can still work without Bluetooth.