[OPL1000] Sonoff DW2 door/window opening sensor - teardown, firmware

p.kaczmarek2 8640 83

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Reply Cool? Ranking DIY | New topic

Notify about new articles

#31 21190823 14 Aug 2024 14:37

divadiow divadiow

Level 35

Helpful post? (0)

Post #31
21190823 14 Aug 2024 14:37

>>21190566

I've flashed the opl1000_at.bin from https://github.com/Opulinks-Tech/OPL1000A2-SDK/tree/master/FW_Binary

The Ali door sensor binary is outside of that SDK path but does reference A2 https://github.com/Opulinks-Tech/OPL1000A2-Door-Sensor-Ali-Cloud

I'm not sure if A3 SDK is a revision of the same SDK as well as a version of the OPL1000 chip, so we should use updated A3 SDK or if each SDK is specifically for each chip type only. I note our chips have A2 printed on them.

Added after 3 [minutes]:

these are identical however
https://github.com/Opulinks-Tech/OPL1000A3-SDK/blob/main/FW_Binary/opl1000_at.bin
https://github.com/Opulinks-Tech/OPL1000A2-SDK/blob/master/FW_Binary/opl1000_at.bin

Added after 1 [minutes]:

each SDK readme does make a point of saying "OPL1000A3-SDK is Opulinks official software development kit for OPL1000 A3 chip" which reads like each SDK is specific to each chip revision
ADVERTISEMENT
#32 21190897 14 Aug 2024 16:14

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Topic author Helpful post? (+1)

Post #32
21190897 14 Aug 2024 16:14

Quote:

use GNU arm GCC tool. "Makefile" is provided for each individual example under SDK\APS_PATCH\examples folder. User can use Make tool to compile and link own application. How to install GCC development environment under Windows system please refer chapter4 of "OPL1000-SDK-Development-guide.pdf" document.

but maybe it would be easier to:
Quote:

use Keil uVision 5 on Windows system. "opl1000_app_m3.uvprojx" project file is provided for each individual example under SDK\APS_PATCH\examples folder. User can open it by KeilC and add own function freely.

I tried first way.

In msys64 do, first update:
Code: text Expand Select all Copy to clipboard
pacman -Syu

then toolchain:
Code: text Expand Select all Copy to clipboard
pacman -S mingw-w64-x86_64-arm-none-eabi-gcc

then you should have:

Add to path:
Code: text Expand Select all Copy to clipboard
export PATH=$PATH:/mingw64/bin

Then try in path:

I added log:

Now I will try to compile:

This has been created:

It has elektroda in bin:

@divadiow can you try to retrace my steps and also get those binaries and then try flashing them?

Added after 9 [minutes]:

interesting:

source: https://github.com/Opulinks-Tech/OPL1000A3-SDK/tree/main/FW_Binary

Added after 4 [minutes]:

https://github.com/Opulinks-Tech/OPL1000A3-SDK/tree/main/FW_Pack

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#33 21190988 14 Aug 2024 17:41

divadiow divadiow

Level 35

Helpful post? (0)

Post #33
21190988 14 Aug 2024 17:41

Oh cool. Ok thanks! I'll replicate asap
#34 21191011 14 Aug 2024 18:05

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (+1)

Post #34
21191011 14 Aug 2024 18:05

The initial msys64 instalation was shown here:
https://www.elektroda.com/rtvforum/topic3889041.html

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#35 21191282 14 Aug 2024 22:03

divadiow divadiow

Level 35

Helpful post? (0)

Post #35
21191282 14 Aug 2024 22:03
#36 21191291 14 Aug 2024 22:11

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #36
21191291 14 Aug 2024 22:11

So it compiles but does not run?

Maybe we need to do: https://github.com/Opulinks-Tech/OPL1000A3-SDK/tree/main/FW_Pack

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#37 21191325 14 Aug 2024 23:45

divadiow divadiow

Level 35

Helpful post? (0)

Post #37
21191325 14 Aug 2024 23:45

well. I should be expecting to see "demo_app1: 1" , "demo_app1: 2" I believe:

I've an AP of Opulinks-TEST-AP / 1234abcd but nothing is joining. Tried 3 APs on different hardware - all 2.4Ghz

Added after 4 [minutes]:

I have packed the m3 with the m0 and used patchdata,txt as the script. boots still but no change

Added after 24 [minutes]:

also did A2 hello world and A3 log bins. hmmm

Added after 8 [minutes]:

divadiow wrote:
A2 hello world

https://blog.csdn.net/qq_24258593/article/details/112751210

Added after 22 [minutes]:

ah, but if I use the script and m0 files as seen in that blog in the pack with my m3

then the app loads

Added after 12 [minutes]:

log doesn't seem to want to connect to any of the APs but does run

Code: Text
Log in, to see the code
#38 21191435 14 Aug 2024 23:54

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #38
21191435 14 Aug 2024 23:54

Good job! Well, there are many demos in the SDK and it seems now we can compile them all? Maybe one of them does WiFi

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#39 21192318 15 Aug 2024 20:32

divadiow divadiow

Level 35

Helpful post? (0)

Post #39
21192318 15 Aug 2024 20:32

hmm.

i've been playing with wpa_station and these are curious

[sys_cfg_rf_m0_set_impl 132] ipc_m3_msg_write fail
[sys_cfg_rf_init_patch 181] sys_cfg_rf_m0_set fail

I'm wondering about what the 128 or 256kb flash built into the OPL1000 contains, or did contain, from factory. Are some of the addresses in PatchData.txt used not correct? where is the RF data held? What effect does having the 8mbit flash in addition to the on-board memory have on PatchData.txt? Do the demos assume only the on-board flash is present?

There's vey little online about this chip as we know.
#40 21192331 15 Aug 2024 20:44

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #40
21192331 15 Aug 2024 20:44

Wait, before we dig into it, you're saying that STA/AP modes are not working in those samples?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#41 21192333 15 Aug 2024 20:47

divadiow divadiow

Level 35

Helpful post? (+1)

Post #41
21192333 15 Aug 2024 20:47

spoke too soon.

packed and flashed this demo

and it can list all the APs around me

Code: Text
Log in, to see the code

and connect to my test AP

not sure of what this means though for the content of a patchdata file for a firmware that'll not fit on the OPL onboard memory

Added after 1 [minutes]:

p.kaczmarek2 wrote:
Wait, before we dig into it, you're saying that STA/AP modes are not working in those samples?

correct. not in the flashed binaries compiled from get_started folder

Added after 55 [seconds]:

= wifi has only worked for me with precompiled binaries
#42 21192352 15 Aug 2024 21:05

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Topic author Helpful post? (0)

Post #42
21192352 15 Aug 2024 21:05

Maybe we shall try this example?
https://github.com/Opulinks-Tech/OPL1000A3-SD...SDK/APS_PATCH/examples/wifi/wpa2_station_gpio
Quote:

WPA2 AP SSID and password is defined in wpa2_station_app.h
Make sure "Opulinks-TEST-AP" AP is open when run this demo.
Refer Doc\OPL1000-SDK-Development-guide.pdf to know how to create a new app project.

Enter your ssid/pass here:
https://github.com/Opulinks-Tech/OPL1000A3-SD...les/wifi/wpa2_station_gpio/wpa2_station_app.h

Docs:
https://github.com/Opulinks-Tech/Document/tree/master/SDK/en

Or find other PatchData.txt?

Attachments:

OPL1000-SDK-Development-guide_ENG.pdf Download (443.33 KB)

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#43 21192439 15 Aug 2024 22:22

divadiow divadiow

Level 35

Helpful post? (+1)

Post #43
21192439 15 Aug 2024 22:22

ha. OK. went back to original m0 and patchdata and tried OPL1000A2-SDK-master\SDK\APS_PATCH\examples\wifi\wpa2_station_gpio
so packing looks like

and after flash

Code: Text
Log in, to see the code

and the device is connected to router

Added after 9 [minutes]:

Couldn't get the LED to light though. Looked like GPIO2 in the pic but also tried a few others
#44 21192459 15 Aug 2024 22:29

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Topic author Helpful post? (0)

Post #44
21192459 15 Aug 2024 22:29

Very good progress!

So:
Code: text Expand Select all Copy to clipboard
OPL1000A2-SDK-master\SDK\APS_PATCH\examples\wifi\wpa2_station_gpio

works and connects to WiFi
but
Code: text Expand Select all Copy to clipboard
https://github.com/Opulinks-Tech/OPL1000A3-SDK/tree/main/SDK/APS_PATCH/examples/wifi/wpa2_station_gpio

does not work?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#45 21192469 15 Aug 2024 22:39

divadiow divadiow

Level 35

Helpful post? (+1)

Post #45
21192469 15 Aug 2024 22:39

I'll do A3 again. I don't recall trying that. Your post just before here https://www.elektroda.com/rtvforum/topic4007556-30.html#21191325 links to A3, but my picture just below shows A2,

Added after 2 [minutes]:

oh no, I did wpa2_station this morning but not with the script file or m0 I am using this evening
ADVERTISEMENT
#46 21192473 15 Aug 2024 22:41

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #46
21192473 15 Aug 2024 22:41

Hm ok so please do more tests so we can be sure what works and what doesn't. What's the difference between A2 and A3?

We could really start porting OBK soon!

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#47 21192488 15 Aug 2024 23:29

divadiow divadiow

Level 35

Helpful post? (+1)

Post #47
21192488 15 Aug 2024 23:29

OK

1.
OPL1000A2-SDK-master\FW_Pack\PatchData.txt
OPL1000A2-SDK-master\FW_Pack\opl1000_m0.bin
OPL1000A2-SDK-master\SDK\APS_PATCH\examples\wifi\wpa2_station_gpio\Output-GCC\opl1000_app_m3.bin (72kb)

= Boots + wifi connects to test AP

2.
OPL1000A3-SDK-main\FW_Pack\PatchData.txt
OPL1000A3-SDK-main\FW_Pack\opl1000_m0.bin
OPL1000A3-SDK-main\SDK\APS_PATCH\examples\wifi\wpa2_station_gpio\Output-GCC\opl1000_app_m3.bin (10kb after build?)

= no boot

Added after 6 [minutes]:

The A2 and A3 Patchdata.txt content and the m0 files differ quite a bit

Added after 22 [minutes]:

p.kaczmarek2 wrote:
What's the difference between A2 and A3?

I haven't been able to find out what the technical differences are between the A2 and A3 chips
#48 21192899 16 Aug 2024 13:02

divadiow divadiow

Level 35

Helpful post? (+1)

Post #48
21192899 16 Aug 2024 13:02

I sent Opulinks some questions. Responses:

Code: Text
Log in, to see the code

I have sent some follow-up questions asking for clarification.
#49 21192907 16 Aug 2024 13:09

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #49
21192907 16 Aug 2024 13:09

Wait but didn't we get A2 to run on OPL1000?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#50 21192908 16 Aug 2024 13:28

divadiow divadiow

Level 35

Helpful post? (0)

Post #50
21192908 16 Aug 2024 13:28

well exactly. my question back to them is about A1 vs A2. Maybe the silkscreen is OPL1000 series, but actually it's an OPL1200 and then it makes sense we should use the A2 SDK.

I have not tried any A1 SDK builds.

Added after 16 [minutes]:

Oh. Series indeed.
ADVERTISEMENT
#51 21192924 16 Aug 2024 13:31

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #51
21192924 16 Aug 2024 13:31

Well, both our photos shows "A2", when you look closely...

So I guess that's solved?

Sadly I don't have my one already (I was flashing a batch of devices for a friend and no he is using it with original cloud) so I may need to get another one soon.

Anyway, so in A2 SDK everything works so far?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#52 21192926 16 Aug 2024 14:16

divadiow divadiow

Level 35

Helpful post? (0)

Post #52
21192926 16 Aug 2024 14:16

p.kaczmarek2 wrote:
Well, both our photos shows "A2", when you look closely...

Yes. Indeed
p.kaczmarek2 wrote:
Anyway, so in A2 SDK everything works so far?

Yes. Seems to be fine so far

Added after 22 [minutes]:

I hadn't clocked these different HDK resources. including OPL1200 datasheet. I've been using https://github.com/Opulinks-Tech/OPL1000-HDK/...aster/OPL1000-DataSheet-NonNDA_DS0-04-1.1.pdf

https://github.com/Opulinks-Tech/OPL1000-HDK/tree/master

https://github.com/Opulinks-Tech/OPL1000-HDK/...aster/OPL1200-DataSheet-NonNDA_DS0-01-1.1.pdf

Added after 19 [minutes]:

anyway. what even is the next step for Opulinks builds? Do you want me to try anything else?

I haven't been able to get an LED to light, even changing code in wpa2_station_app.c to pull high all likely GPIOs

Code: C / C++
Log in, to see the code
#53 21193052 16 Aug 2024 15:52

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #53
21193052 16 Aug 2024 15:52

What is actually this function doing:
Code: C / C++
Log in, to see the code

maybe we need more?
https://github.com/search?q=Hal_Vic_GpioOutput&type=code

I've found this:
Code: C / C++
Log in, to see the code

So maybe you are missing a Hal_Vic_GpioDirection call?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#54 21193315 16 Aug 2024 19:27

divadiow divadiow

Level 35

Helpful post? (0)

Post #54
21193315 16 Aug 2024 19:27

ah. the function of the correct GPIO needed changing in hal_pin_config_project.h to PIN_TYPE_GPIO_OUTPUT_HIGH from PIN_TYPE_ICE_M3_CLK

then only the GPIO# in wpa2_station_app.c needs changing.

Code: Text
Log in, to see the code

It's clear from the traces and datasheet the LED is connected to GPIO21

and now LED lights when wifi is connected

hal_pin_config_project.h content is a product of the PinMux tool where the function of each GPIO can be set.

the highlighted files are created on PinMux build
#55 21193451 16 Aug 2024 21:56

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #55
21193451 16 Aug 2024 21:56

Great! So what next?
PWM?
OTA?

PWM:
https://github.com/search?q=repo%3AOpulinks-Tech%2FOPL1000A2-SDK%20PWM&type=code

ota:
https://github.com/Opulinks-Tech/OPL1000A2-SD...mples/system/ota_wifi/http_ota_example.c#L398

If we can get ota_wifi demo working, we could try adding OBK to that.

Just how to get OTA file...

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#56 21193453 16 Aug 2024 21:59

divadiow divadiow

Level 35

Helpful post? (0)

Post #56
21193453 16 Aug 2024 21:59

>>21193451

yes. the OTA demo is on my radar

I was going to OTA Hello World to WPA2_GPIO or something. There's an OTA pack tab in the flash tool.
#57 21193456 16 Aug 2024 22:02

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #57
21193456 16 Aug 2024 22:02

We will also need to think about the futher OTA usage. Can the OTA file be created from commandline? Our automatic Github builds will require that....

I will do the coding, once we have everything confirmed to work, but I don't know much about the build process on Github itself. Maybe we can just reuse the path of one of the other platforms.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#58 21193536 17 Aug 2024 07:40

divadiow divadiow

Level 35

Helpful post? (0)

Post #58
21193536 17 Aug 2024 07:40

p.kaczmarek2 wrote:
Can the OTA file be created from commandline?

not found any mention of a command line option yet. the builder exe does not accept anything cli - it just launches gui.

pausing at this point for tonight

http server is serving opl1000_ota.bin file download for any other device on subnet but not the DW2 yet.

Added after 7 [hours] 49 [minutes]:

Code: Text
Log in, to see the code

back to our original understanding!

Added after 11 [minutes]:

Oh and look https://templates.blakadder.com/unsupported/sonoff_L3.html

If OPL1200 then it's labelled as such.
#59 21194663 18 Aug 2024 09:33

divadiow divadiow

Level 35

Helpful post? (0)

Post #59
21194663 18 Aug 2024 09:33

I am no further forward with a working OTA demo.

Also a little worrying is the distinct lack of a soft-AP demo or any real mention of soft-AP mode in the documentation.

Added after 5 [minutes]:

some mentions
#60 21194822 18 Aug 2024 12:17

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (0)

Post #60
21194822 18 Aug 2024 12:17

Strange:

Did this device support AP mode pairing for the app?

But those comments seem to be related to separate functions, not to AP mode itself..

Here is some STA init code:
https://github.com/Opulinks-Tech/OPL1000A2-SD...amples/protocols/tcp_client/tcp_client.c#L235
Maybe we can change:
- wifi_config.sta_config to wifi_config.ap_config
- WIFI_MODE_STA to WIFI_MODE_AP

Added after 41 [seconds]:

Then it should create AP. The AP initialization itself is NOT listed as unsupported, so it should work.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Reply Cool? Ranking DIY | New topic

Notify about new articles

Report a violation of the law

Topic summary

The discussion centers on the Sonoff DW2 door/window opening sensor based on the OPL1000 WiFi microcontroller, focusing on hardware teardown, firmware backup, and potential firmware modification. The sensor is inexpensive (~30 PLN) and uses WiFi communication, unlike its predecessor DW1 which used RF433MHz. Users confirmed the sensor transmits signals on opening but not necessarily on closing, with no firmware modification currently possible. Efforts to develop OpenBeken (OBK) support for OPL1000 are ongoing but limited by the chip's low popularity and scarce documentation. The OPL1000 SDKs (A1, A2, A3) correspond to different chip revisions or related chips (OPL1000, OPL1200, OPL1600/1800), with the DW2 sensor marked as A2 and compatible with the OPL1000A2 SDK. Firmware dumping was performed by desoldering the TH25Q-80UA 8Mbit SPI flash chip and bit-banging with FTDI, revealing AliCloud firmware with OTA capabilities and AT command support. Flashing custom firmware using the Opulinks Download Tool and compiling SDK examples (e.g., wpa2_station_gpio) was successful, enabling WiFi connection and GPIO control (e.g., LED on GPIO21). However, soft-AP mode is not supported or unclear, with pairing likely done via BLE rather than WiFi AP mode. OTA update demos were tested but initially failed due to improper firmware packaging; using the correct OTA loader and build process resolved this. Challenges remain in understanding flash memory layout, patch data usage, and full SDK utilization. Additional hardware like the E103-W08A OPL1000 module was also examined. The community is progressing toward porting OBK firmware to OPL1000 devices, with ongoing exploration of SDK examples, build environments (MSYS2), and flashing tools. Key technical issues include UART bootloader access, flash dumping, firmware compilation, OTA implementation, GPIO control, and network modes (STA/AP/BLE). The discussion includes detailed logs, code snippets, and hardware photos to support development efforts.
Summary generated by the language model.

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
Smart Home Devices
/
[OPL1000] Sonoff DW2 door/window opening sensor - teardown, firmware

FAQ

TL;DR: The Sonoff DW2-WiFi draws ≤40 µA at idle and successfully flashed a 160 kB OTA image; “We haven’t touched OPL1000 yet due to its very low popularity” [Elektroda, p.kaczmarek2, post #20938882]

Why it matters: clear electrical limits and tool-chain notes save hours when hacking this rare Wi-Fi door sensor.

Quick Facts

• Stand-by current: ≤40 µA; transmit current ≤15 mA [Elektroda, p.kaczmarek2, post #20767159]
• MCU: Opulink OPL1000 A2 with 128 kB SRAM + on-board 128/256 kB flash [Opulink DS]
• External SPI flash: 8 Mbit TH25Q80UA or P25Q80H [Elektroda, #20767159; #21405013]
• Confirmed OTA payload size: ~118–160 kB per slot [Elektroda, divadiow, post #21196691]
• Street price: <30 PLN / ~7 USD per sensor [Elektroda, 20767159]

Does the DW2-WiFi report both open and close events?

Yes. Field tests and multiple video reviews show separate MQTT/cloud packets for opening and closing when the stock eWeLink firmware is paired [Elektroda, p.kaczmarek2, post #20767671]

Which pins expose the UART console and at what speed?

GPIO0 = UART TX for flashing/AT (115 200 bps), GPIO8 = boot log TX. Ground GPIO1 to enter boot mode, then toggle power and start the Opulinks Download Tool [Elektroda, divadiow, #21186407; #21190297].

What is the maximum OTA image size?

The built-in dual-slot updater accepted and wrote 118 300 bytes and later 160 180 bytes without error; larger 1 MiB images were rejected at ~167 kB, so the practical limit is ≈160 kB per slot [Elektroda, divadiow, post #21196691]

Is Soft-AP provisioning supported?

No. The SDK exposes WIFI_MODE_STA and BLE setup; WIFI_MODE_AP symbols exist but link-time flags disable them, so pairing relies on BLE, not an access-point [Elektroda, divadiow, post #21205368]

How do I dump the external flash safely?

Desolder the SOIC-8 chip to avoid bus contention. 2. Read with CH341 A using NeoProgrammer; the TH25Q80UA is detected as ID 0xEB6014. 3. Verify MD5 before re-soldering [Elektroda, p.kaczmarek2, post #20767159]

What happens if the OTA download is interrupted?

The loader writes to the inactive slot; checksum is validated before reboot. If power fails mid-write, the device boots from the untouched slot. Edge case: corrupt header triggers “ota_prepare fail” and aborts update [Elektroda, 21194948]

Can I compile and flash my own firmware?

Yes. The OPL1000 A2 SDK builds with arm-none-eabi-gcc under MSYS2. Use the Opulinks Pack Tool v2.0.0 to merge m0, m3 and ota_loader, then flash via UART. A custom WPA2-station demo connected and toggled GPIO21 LED successfully [Elektroda, #21192439; #21196691].

Is there an open-source port like OpenBeken?

Not yet. Developers have proofs-of-concept, but most contributors prioritise ESP8266 because “I still have more ESP8266 support requests than the OPL1000 ones” [Elektroda, p.kaczmarek2, post #21176434]

What alternative battery Wi-Fi sensors exist?

LN882-based door sensors now run OpenBeken and cost similar money. Tuya-MCU units also exist but need serial bridging and draw higher stand-by current (~80 µA) [Elektroda, 20938882]

Which GPIO drives the status LED?

On Sonoff DW2-WiFi PCB rev 1.2 the LED anode sits on GPIO21. Setting it as PIN_TYPE_GPIO_OUTPUT_HIGH lights the LED after connection [Elektroda, divadiow, post #21193315]

Stat: How long will two AAA cells last in stock firmware?

With ≤40 µA idle and ~15 mA for 500 ms per open/close, two 1000 mAh AAA cells last approx. 18 months (theoretical) [Texas Instruments CR formula; Elektrode data #20767159].

Edge case: does the tool check image authenticity?

Only a simple header checksum is used. Manual byte edits in the header break the checksum and prevent boot, but body encryption is absent, letting researchers patch code freely [Elektroda, 21360269]

3-step: How to push an OTA update over Wi-Fi?

Host opl1000_ota.bin on an HTTP server at 192.168.x.x:8000. 2. Flash http_ota_example; it connects and fetches the file. 3. After 100 % write, device reboots from MW_OTA[1] slot [Elektroda, 21196691]

Can I buy a breadboard-friendly OPL1000 module?

Ebyte’s E103-W08A exposes 24 pads but uses 1.27 mm pitch; adaptors required. It ships with a rich AT set and the same 8 Mbit flash [Elektroda, #21386402; #21386543].