What chipset is inside the “generic” TW02 SmartPlug?
The module is a TW-02 carrying the WinnerMicro W600 Wi-Fi MCU, an 80 MHz ARM Cortex-M3 with 1 MB flash and 288 KB SRAM [Elektroda, iprak, #20239610; WinnerMicro Datasheet].
W600 TW02 Generic SmartPlug
TL;DR
- Teardown of an unbranded SmartPlug wifi switch showed it used a W600 TW-02 module and the Smart Life app.
- Serial output identified Tuya IoT SDK V2.0.0, firmware TC0025_TW02_PLUG_L1_P0, and the board exposed 3.3V, Gnd, PA5 switch input, PB8 blue LED, and PB15 relay/red LED.
- The module drew around 80mA in stock condition, while the FCC filing said it could consume up to 230 mA.
- OpenBK7231T was adapted to compile the W600 SDK, and the W600 build became part of OpenBK7231T's standard build.
- The module ran a bit warm, and opening required a sharp spudger plus patient desoldering of the power connections.
This is a teardown of an unbranded wifi switch named SmartPlug. The printed manual referred to Smart Life app.
The appearance is quite generic with a single button on one side. There is a blue LED around the button.
I was able to safely open using using a sharp spudger. The electronics are recessed so spudger has quite less change of damaging anything. Desoldering the power connections takes patient but I was able to do just using a desoldering wick.
And here is the cleaned up board and the chip.
The module had power and serial connection cleared marked and serial connection showed this.
So LSP-A was actually a W600 TW-02 module.
W600 - https://www.winnermicro.com/en/html/1/156/158...%20Wi,industrial%20and%20other%20IoT%20fields.
There is also a FCC filing about TW-02 - https://fccid.io/2ASQV-TW-03/User-Manual/User-manual-4210975.pdf
Examination of the board showed that there was actually a red and a blue LED; red was tied to the relay.
Later I was able to adjustOpenBK7231T app to compile the W600 SDK (originally obtained from https://github.com/w600/sdk). The W600 build is now part of OpenBK7231T's standard build.
And here are the actual connections:
Side-A
* 3.3V
* Gnd
* PA5 connected to switch pulled high
* PA4 - No connection
* PB16 - No connection
* PB15 - relay tied to red LED
Side-B
* PB13 - No connection
* PB18 - No connection
* PB8 - blue LED
* PB7 - No connection
* Reset - No connection
The module seems to run a bit warm and took around 80mA in stock condition before custom firmware. The FCC filing mentioned that it can consume up to 230 mA so this was well within range.
The appearance is quite generic with a single button on one side. There is a blue LED around the button.
I was able to safely open using using a sharp spudger. The electronics are recessed so spudger has quite less change of damaging anything. Desoldering the power connections takes patient but I was able to do just using a desoldering wick.
And here is the cleaned up board and the chip.
The module had power and serial connection cleared marked and serial connection showed this.
<TUYA IOT SDK V:2.0.0 BS:30.01_PT:2.2_LAN:3.3_CAD:1.0.1_CD:1.0.0 >
[FW]: TC0025_TW02_PLUG_L1_P0 | [HW]: TW-02 V2.0 | [SW]: V1.4.0 (Nov 18 2019 08:48:17) | [PID]: nqvhejakb112obkn
[01-01 00:00:00 TUYA Notice][hw_table.c:532] wifi status is :0
[01-01 00:00:00 TUYA Notice][wifi_hwl.c:1316] <LF> old mode is 4 <LF>
[01-01 00:00:04 TUYA Notice][tuya_main.c:143] wf_assign_ap_scan failed(-606)
[01-01 00:00:04 TUYA Notice][gw_intf.c:2270] gw_cntl.gw_wsm.stat:1
[01-01 00:00:04 TUYA Info][wifi_hwl.c:1261] Low Power Mode
[01-01 00:00:05 TUYA Notice][hw_table.c:532] wifi status is :0
[01-01 00:00:14 TUYA Notice][tuya_device.c:694] free_mem_size:89880
So LSP-A was actually a W600 TW-02 module.
W600 - https://www.winnermicro.com/en/html/1/156/158...%20Wi,industrial%20and%20other%20IoT%20fields.
There is also a FCC filing about TW-02 - https://fccid.io/2ASQV-TW-03/User-Manual/User-manual-4210975.pdf
Examination of the board showed that there was actually a red and a blue LED; red was tied to the relay.
Later I was able to adjustOpenBK7231T app to compile the W600 SDK (originally obtained from https://github.com/w600/sdk). The W600 build is now part of OpenBK7231T's standard build.
And here are the actual connections:
Side-A
* 3.3V
* Gnd
* PA5 connected to switch pulled high
* PA4 - No connection
* PB16 - No connection
* PB15 - relay tied to red LED
Side-B
* PB13 - No connection
* PB18 - No connection
* PB8 - blue LED
* PB7 - No connection
* Reset - No connection
The module seems to run a bit warm and took around 80mA in stock condition before custom firmware. The FCC filing mentioned that it can consume up to 230 mA so this was well within range.
Comments
Good job, @iprak . As far as I can tell, you're the first one in the world to flash custom IoT firmware on W600 product. I also have one W600 product in the queue (a RGBCW bulb), but I haven't found... [Read more]
Sorry, I don't know where the plugs came from. I got it from a local guy who claimed they no longer worked. [Read more]
To replace the personally killed WB2S module, which are not available for free sale, TW-02 2.0 was purchased . I begin to conduct the following tests of the brain and iron. https://obrazki.elektroda.pl/1085525200_1666679666_thumb.jpg... [Read more]
@omelchuk890 don't worry, as far as I remember, on W600 platform you have just to use the "basic" OTA mechanism, the one from WWW panel, that takes a HTTP server link to a binary file. You can use Xampp... [Read more]
Yes, both W800 and W600 don't support webApp based drag-n-drop OTA update. You can use the native webApp to directly upload the firmware. [Read more]
@iprak Tell me how? I'm not good at the web Will it be enough if a file is sent to him at the request of the module? [Read more]
The second option would be to implement http_rest_post_flash from rest_interface.c. I am not sure how the internals of W600/W800 OTA look like, tough. @omelchuk890 hmm install xampp on windows, make... [Read more]
You need a local webserver, that is what Xampp or Node Red is. There are variety of other options including IIS, nodejs. I personally use IIS since it comes bundled with Windows and give you more instructions.... [Read more]
I have a bad idea of the sequence of actions. Will such a design work? https://obrazki.elektroda.pl/6704436300_1666718955_thumb.jpg Added after 16 [minutes]: Ok, tomorrow [Read more]
@omelchuk890 if you have a node-red (as you shown on screenshot), then you obviously don't need xampp. That sequence could work, but please make sure that file is read as a raw binary stream. It's one... [Read more]
@pkaczmarek2 Everything turned out using Node-Red. It's very simple. Absolutely. But a little instruction to those who follow in my footsteps. Copy the file we need to the home folder, I put it in... [Read more]
@omelchuk890 end? where? It's just the beginning. We are going to support all major platforms as long as they are possible to support. The release files were just missing because I didn't have to update... [Read more]
@pkaczmarek2 board W600 versions 70 and 71 do not work after the update. Not by ota wifi, not by com port. Rolled back to version 1.14.69 After downloading 71, the network 4.1 does not appear ... [Read more]
@omelchuk890 thank you for reporting the issue. From what I can see, our developer @iprak is already investigating it. https://github.com/openshwprojects/OpenBK7231T_App/issues/354 @omelchuk890 @iprak... [Read more]
I'm sure this it the wrong place for this, but the poor W600 is one of the least-supported chips out there. This project makes me happy because some time ago I bought a bag of Wemos W600-Pico boards.... [Read more]
You can find flashing instructions here https://github.com/openshwprojects/OpenW600 and custom firmware here https://github.com/openshwprojects/OpenBK7231T_App under Releases. [Read more]
We can add WS2812 support, if that's needed. [Read more]
I don't know how much effort that would be on this processor, but it would be very nice to have it. The W600-Pico dev board comes with a pretty limited version of Micropython that has not been updated... [Read more]
Sorry but I feel that features should be added based on the presence of a real device and not a dev SDK. Otherwise the testing would be very limited and might lead to overall instability. That Micropython... [Read more]