Web App Flash Tab: Inconsistent Status Messages for Tuya GPIO and Custom Dump Buttons

divadiow 504 30

#31 21827572 03 Feb 2026 07:01

divadiow divadiow

Level 37

Topic author Helpful post? (0)

Post #31
21827572 03 Feb 2026 07:01
ADVERTISEMENT
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Topic summary

The discussion addresses inconsistencies in the status messages displayed on the Flash tab of a web application related to firmware dumping functions. Specifically, when selecting "Download Tuya GPIO Config," the app incorrectly shows "reading full dump...." followed by "Full dump ready!" which is misleading. Additionally, the "Download Custom" button lacks a completion message similar to the other buttons. Modifications to the flash.vue component were proposed and tested to improve user feedback by adjusting the status messages: changing "reading..." to "downloading..." for download buttons and ensuring all buttons provide a clear completion log. A related pull request (PR #249) on the OpenBekenIOT/webapp GitHub repository implements these improvements, enhancing clarity and consistency in the UI during firmware dump operations.
Summary generated by the language model.

FAQ

TL;DR: The Web App’s Flash tab now distinguishes “downloading…” vs “reading…”, and the full dump is 2 MB. “Way better, I will merge it now.” [Elektroda, p.kaczmarek2, post #21801475] Why it matters: It prevents misflashes and helps users back up RF data correctly on BK7-series chips.

Full flash dump size is 2 MB (2,097,152 bytes); sample call uses start=0, size=2097152, mode="QIO". [Elektroda, p.kaczmarek2, post #21801475]
Tuya GPIO and Custom buttons now show “downloading…”; read buttons keep “reading…”. [Elektroda, divadiow, post #21800096]
Shared function renamed to startDumpJob with unified parameters to avoid duplication. [Elektroda, p.kaczmarek2, post #21801475]
BK7238 TLV/RF data can be overwritten by flash vars after conversion. [Elektroda, insmod, post #21802415]
BK7-only RF tools are UI-gated; controls grey out on non-“bk7” chipsets. [Elektroda, divadiow, post #21802297]

Quick Facts

What exactly changed in the Flash tab status messages?

Download actions now log “downloading…” instead of “reading…”, while read actions continue to log “reading…”. This fixes the earlier mismatch where the Tuya GPIO and Custom downloads could show read-style messages and Custom lacked a final ready log. The Full Dump already confirmed completion correctly. [Elektroda, divadiow, post #21800096]

How do I trigger a proper full dump from the Web App?

Use the Full 2MB dump action. Internally it calls startDumpJob with parameters like name, job type “FullDump”, start=0, size=2097152, mode="QIO". Expect a completion message when the dump finishes. This maps to a 2,097,152‑byte image suitable for full backup. [Elektroda, p.kaczmarek2, post #21801475]

What is startDumpJob and why was it introduced?

startDumpJob centralizes dump setup to remove duplicated logic. It takes arguments for label, job type, start offset, size, and flash mode, then starts the dump. This refactor improves maintainability and ensures consistent status messaging across Full, Tuya GPIO, and Custom operations. [Elektroda, divadiow, post #21801456]

Is flash reading limited to Beken (BK7) devices?

The workflow is currently BK7‑centric. The UI now greys out certain RF/TLV tools when the detected chipset does not start with “bk7”, signaling features are scoped to BK7. Broader platform read support remains an open consideration. [Elektroda, divadiow, post #21802297]

Why might BK7238 TLV scanning fail after converting to OBK?

After conversion, the TLV block can be gone, so a scan returns nothing. Screenshots in the thread show a converted BK7238 image with TLV missing, implying the original factory TLV was overwritten during the process. [Elektroda, divadiow, post #21802340]

What overwrites the TLV/RF area on BK7238 during conversion?

Flash vars overwrite it. An expert confirmed, “Flash vars” are the component responsible for overwriting, which explains missing TLV post‑conversion and failed TLV detection. [Elektroda, insmod, post #21802415]

How can I avoid losing RF data when converting BK7238 devices?

Back up the entire flash before conversion. Users often reassemble devices only to realize they need RF, and Easy Flasher does not require a full backup by default. Do a full 2 MB dump first to preserve RF data. [Elektroda, divadiow, post #21802348]

Is the fix for inconsistent messages merged?

Yes. The maintainer reviewed the improvements and stated, “Way better, I will merge it now,” referring to the startDumpJob refactor and parameterization shown with a Full 2MB example. [Elektroda, p.kaczmarek2, post #21801475]

What is Tuya in this context?

Here, “Tuya” refers to the Tuya GPIO configuration dump/download option in the Flash tab. The change ensures its button shows “downloading…” while read actions retain “reading…”, aligning logs with the operation. [Elektroda, divadiow, post #21800096]

What is OpenBeken (OBK) in this thread?

OpenBeken is the project whose Web App received PRs that fixed messaging and added BK7‑specific tooling. The maintainer discussed merge and future string cleanup around startDumpJob, indicating active development. [Elektroda, p.kaczmarek2, post #21801475]

Why is chunk size important when scanning for TLV headers?

The scan reads 0x1000‑byte (4096‑byte) chunks. A TLV header crossing chunk boundaries can be missed if you only check within each chunk. Use overlapping or carry‑over buffers to avoid boundary misses. “You won’t find it that way.” [Elektroda, p.kaczmarek2, post #21802316]

Can we move flash vars to protect RF/TLV regions?

Yes. The maintainer noted flash vars are not critical and can be moved globally elsewhere. Even if some updates break minor things, the trade‑off favors preserving RF data integrity across updates. [Elektroda, p.kaczmarek2, post #21802420]

How do I perform a clean Full 2MB dump (three steps)?

Open Flash tab and select the Full 2MB dump action.
Confirm it runs startDumpJob with start=0, size=2097152, mode="QIO".
Wait for the completion message, then save the file. [Elektroda, p.kaczmarek2, post #21801475]

Does the Custom download now show a completion message?

Custom previously lacked a final “ready!” log. With the update, downloads show “downloading…”, bringing parity with other buttons. The Full Dump already indicated completion correctly, so user feedback is now consistent. [Elektroda, divadiow, post #21800096]

Will string names for dump modes be simplified later?

Yes, the maintainer suggested possibly removing one string name in the future, since all three may not be required. That would further streamline startDumpJob usage and UI text. [Elektroda, p.kaczmarek2, post #21801475]

What’s a safe default if I’m unsure about my platform support?

If the UI greys out BK7‑specific tools, avoid those steps and do a standard full dump first. That preserves data while you verify hardware support and tool compatibility. Then proceed with targeted operations. [Elektroda, divadiow, post #21802297]