yes, I grabbed a Hi-Link HLK-W806-Kit-V1.0 board from Ali Express a week ago as it looked just like it's sister board the HLK-W800-Kit-1.0 and I wanted to see if OBK had any chance on it. I didn't really look at the spec when I bought it, but it doesn't have wifi/BT and it only has 1mb flash!
Without any research I tried flashing the W800 OBK but this unsuccessful, failing with this error
There were some failures because of size. This I think was the size that built
but then it would fail with
which I can't find mention of yet. Assuming this related to size I then set about trying to exclude bits to reduce flash total bytes, but you can see from subsequent runs this has not been successful yet. I've been commenting-out bits in the SDK relating to the demo, BT etc, but nothing I've tried has reduced size.
Even with a working OBK the 1mb flash probably makes it very limiting driver-wise, but still, it would be another supported chip to add to the list. Suggestions welcome!
How do you know that NAK error means that flash is too big?
I don't. Just a stab in the dark. But maybe it's related to NACK and it's that the flasher didn't receive an acknowledgement after Packets: 57/957? I've tried different uart speeds.
p.kaczmarek2 wrote:
What is the current flash size?
1mb!
p.kaczmarek2 wrote:
I can add some #define for you to for example allow turning off features like Tasmota JSON emulation
well that would be cool, but I am also happy to just keep playing myself if you've no time/other priorities. W806 was just a little adventure with no stakes.
I don't think it's exactly 1MB, what is the current size of build files?
p.kaczmarek2 wrote:
Can we get somehow some other binary for testing W806?
I did wonder about that. Will try to find something. The board didn't seem to come with anything from factory. I can't yet post on the WM forums because I need more reputation points 🙄
p.kaczmarek2 wrote:
I can try to help, I have linux vm, maybe we can build/compile something else together..
I can try to add more size build reduction within 3 to 6 hours from now so you can test more.
well sure! that'd be awesome.
Added after 1 [hours] 19 [minutes]:
I'm trying to find evidence the W806 really does have wifi/bt cores. unsure yet
i'm probably doing something wrong. I'm commenting out/undefining but that doesn't seem to be making a difference. I'm making the changes to my OpenW800 submodule then pushing to my fork then pushing to remote main. it's triggering the workflow with the open PR so I guess my changes are making it up to the right place...
I believe so. that's what I spent the first half the evening fixing. I started again with everything since the night before.
.gitmodules has
Code: Text
Log in, to see the code
Summary of My Setup:
Forks and Clones:
I forked the repositories OpenBK7231T_App and OpenW800 from the original repositories.
I cloned my forks to my local machine:
OpenBK7231T_App: C:\Users\divad\Documents\GitHub\OpenBK7231T_App
OpenW800: C:\Users\divad\Documents\GitHub\OpenW800
Submodule Configuration:
The OpenBK7231T_App repository includes the OpenW800 submodule.
I verified that the submodule URL in my OpenBK7231T_App repository points to my fork of OpenW800.
that commit showing the file changes I made in my submodule are making their way to the main app PR is evidence all is OK?
Hey, what's the state of W806 flash attempt? How much size reduction is needed? Maybe it will be possible once we merge:
Testing OBK Config for Smaller Builds on OpenBK7231T - Feedback Needed With new features, it's possible to even disable MQTT in the build and it gives a very good flash size reduction.
maybe it could be made to run with no wifi - but then you'd just get to watch the uart logs? or you'd have to somehow script all settings. Maybe OpenW806 Core Edition - without GUI
Added after 1 [minutes]:
Maybe I'll try flash to see if anything is different with latest smaller build
Added after 26 [minutes]:
not seeing sizetest2 builds that much smaller for W800. 950kb smallest I've seen I think.
Log output is present on main release:
Oops I managed to somehow break config and it's now in brand new AP state. Probably I reseted it (on main release) while it was saving flash and it has corrupted. But still...
Back on berry:
I can confirm there is no log output on your "berry " build...
The discussion compares the OpenBeken W800 and W806 boards, focusing on hardware differences, firmware compatibility, and OTA update methods. The W806 board, specifically the Hi-Link HLK-W806-Kit-V1.0, differs from the W800/W801 by lacking Wi-Fi and Bluetooth functionality and having only 1MB flash memory, which complicates flashing OpenBeken firmware designed for W800. Attempts to flash W800 firmware on W806 fail due to flash size and missing factory calibration data for Wi-Fi, making Wi-Fi enablement on W806 impractical. A minimal LED blink demo for W806 was successfully flashed, but full OpenBeken builds exceed the flash size. Efforts to reduce firmware size by disabling features like Tasmota API showed limited success. The W800 supports HTTP server-based OTA updates, but the Web App OTA is missing. Newer SDK versions for W800 introduce features like EasyFlash for flash variable storage, Berry shell, and LFS support, but also cause Wi-Fi signal degradation and slower OTA performance. Toolchain updates and SDK porting challenges were discussed, including GCC versions and libc implementations. Backup methods for W800 firmware are limited, with no known XT804 backup method. The W806 is considered more suitable for non-Wi-Fi applications or UART logging due to hardware limitations. The community is exploring SDK updates, flash size optimization, and configuration storage improvements, including potential EasyFlash integration and dynamic config sizing. Overall, W800 remains the preferred platform for Wi-Fi-enabled OpenBeken applications, while W806 is limited by hardware constraints. Summary generated by the language model.