Tuya WiFi IR T1-3S - does the module support OpenBeken? UART logs, chip identification

divadiow wrote:

you could also try BKFIL and see if there is any difference

https://www.elektroda.pl/rtvforum/topic4059172.html

.

It went the first time.

EDIT:
I'll take pictures, solder and post everything on the forum.

null wrote:

It worked first time.

.
Oh, great. Interesting. I wonder what this means for Easy Flasher. I've ordered something that looks like the same device. I hope it will have a T1!

Added after 4 [minutes]: .

Out of curiosity, did BKFIL refer to the chip as "BK7238" in the log during flashing? BKFIL should output the data to a .log file in the BKFIL folder if you have already closed the application.

divadiow wrote:

Out of curiosity, did BKFIL refer to the chip as "BK7238" in the log during flashing? BKFIL should output the data to a .log file in the BKFIL folder if you have already closed the application.

.

Is OpenBeken taking off?

So BKFil works and Easy Flasher doesn't? Interesting...

p.kaczmarek2 wrote:

From this it appears that OpenBeken is running on your device. Can you give me (I'll use for the tutorial) an accurate and clearer picture of this module and information where the device comes from, pictures of the case, any info you have?

.
Bought: https://pl.aliexpress.com/item/10050078048597...in.11.2e2e1c24Xufr2H&gatewayAdapt=glo2pol



.

.

Added after 20 [minutes]:

Thanks to everyone for their help. When flashing the chip.
I'm left to figure out why the IR receiver isn't working, but that's for after the holidays.

Congratulations on the programming of the T1, you are the first person to do it officially with us. Thank you for your help with the testing! However, it was worth the struggle rather than immediately giving up and sending the chip to me. So that means OBK is working on the next module. I'll have to make a separate news topic about that.

can we expect the timings to be OK on BK7238 for ir to work? I could test I guess. Does ir send/receive work @Nargo?

divadiow wrote:

Can we expect the timing to be OK on the BK7238 to make it work? I could test this. Does ir send/receive work @Nargo?

.

It receives something, sends something. haven't played with it yet.

Interestingly enough, Tuya lists T chips up to 5 here:

I wonder if they are all Beken? T2 pins looks like Beken...
T3 says: 32-bit Armv8-M STAR-MC1 MCU , it also has P40 and P41...
T5 is similar. Both T3 and T5 has WiFi 6.

>>21621714
T1 - BK7238
T2 - BK7231N
T3 - BK7236
T5 - BK7258

Sources? I didn't manage to find that yet.

Related https://www.elektroda.com/rtvforum/topic4068365.html#21291302

Also, that T4 SDK, whatever that is

T1 - well, we already know.
T2 - https://github.com/tuya/TuyaOpen-T2/blob/e34a...9/t2_os/beken378/app/config/sys_config.h#L119
T3 - i have one, BKFIL recognizes it as BK7236 and https://github.com/tuya/TuyaOpen-T3/blob/0656...3_os/tuya_build/bk7236/config/sdkconfig.h#L10
T4 - BK7252N (from T4 SDK, T4_0.0.1_temp/t4_os/build.sh#5)
T5 - https://github.com/tuya/TuyaOpen-T5AI/blob/3d...d1d94513dd945e2682bba329f3/t5_os/build.sh#L10

From the HA, it is easy to send a remote control command via MQTT.
However, I cannot figure out how to receive commands in HA.
There are commands in the OpenBK logs, but nothing reaches the HA via MQTT.

Activate flag 22
.

Do you think that Easy Flasher works for T1? We have a sample size of 1 and supposedly there is an issue.

Easy Flasher did not work for me. BKFIL programmed without a stammer.

https://github.com/OpenBekenIOT/webapp/commit/499a6049ce9075d812262e3ab1f6ec940125910e

no T1 for me

Same here:


Added after 6 [minutes]:

I moved T2-U discussion there: https://www.elektroda.com/rtvforum/topic4133041.html

Hi. I've got the same T1-S3 chip as op and have tried flashing with BKFil (v2.2.12.1) and I may have mess up and possibly bricked it. This is my first time flashing something like this.
I have 3 wires soldered to the chip. Tx1(16), Rx1 (15), and grd(9). The other end is connected to the usb serial in reverse order for the tx, rx pins. When I click read flash, it is asking for a bin file. Not knowing where to find this file, I thought I could use the `OpenBK7238_QIO_1.18.145.bin` from BK7231 Flasher. Click on read flash again, I get no response.

```
2025-08-07 09:34:31.497 stop Read thread.
2025-08-07 09:34:31.501 start Read thread.
2025-08-07 09:34:31.532 cmdline: |C:/Users/Duc/Desktop/BEKEN_BKFIL_V2.1.12.1_20250424/bk_loader.exe read -p 4 -b 1500000 --uart-type CH340 --mainBin-multi C:/Users/Duc/Downloads/OpenBK7238_QIO_1.18.145.bin@0x0-0x132000 --fast-link 1 |
bk_loader version 2.1.12.1: build @apr 24 2025 17:11:46
2025-08-07 09:34:31.532 start Read thread.
2025-08-07 09:34:31.596 Current port : COM4 + BaudRate : 115200 connect success
2025-08-07 09:34:31.596 do_reset_signal
2025-08-07 09:34:31.596 Getting Bus...
2025-08-07 09:34:32.087 Gotten Bus...
2025-08-07 09:34:32.195 Current Chip is : BK7238
2025-08-07 09:34:32.225 Current baudrate : 1500000 success
2025-08-07 09:34:32.225 [ 0 ] file_startAddr : 0x00000000
2025-08-07 09:34:32.225 [ 0 ] file_path : C:/Users/Duc/Downloads/OpenBK7238_QIO_1.18.145.bin
2025-08-07 09:34:32.225 [ 0 ] file_length : 0x132000 (1224 KB)
2025-08-07 09:34:32.225 [ 0 ] file_crc : 0x181901fe
2025-08-07 09:34:32.225 Begin ReadFlash...
2025-08-07 09:34:32.512 do_reset_signal
2025-08-07 09:34:32.512 Getting Bus...
2025-08-07 09:34:32.512 Getting Bus...
2025-08-07 09:34:47.657 Getting Bus...
```

I saw the Download button and thought this is where I can download the bin file. Click on that and I think it proceeded to erase with success, but got stuck on the flashing part. So I may have erased the stock file which I needed to create the bin file??? Is this bricked?

Added after 4 [hours] 7 [minutes]:

Update: I tried again using the same bin file mentioned above. It completed successfully. I am able to access 192.168.4.1. Now what do I do?
I saw this post where the op provided his esphome yaml code. However, BK7238 chip is not supported in esphome.

Good job on flashing it with OBK. Remember that OBK has two different IR library versions - it can be helpful if you want to use more rare protocols.

So, now you need to access it at 192.168.4.1 and configure it like you configure Tasmota - enter your WiFi data. Then you can configure GPIOs...

>>21628155

Quote:

Remember that OBK has two different IR library versions - it can be helpful if you want to use more rare protocols.

Can you provide a link to where I can download the other library? It seems my AC unit codes are the same for most of the buttons I try to learn.

So you already have pins configured? Can you share config? Or is it the same as here?

Here are our downloads:
https://github.com/openshwprojects/OpenBK7231T_App/releases
Look for irRemoteESP build. If it's not enabled yet for your platform, then we can enable it for you. It actually is not, is it, @divadiow ?

p.kaczmarek2 wrote:

It actually is not, is it, @divadiow ?

nope

>>21628303
irRemoteESP sources are not yet in obk_main.mk
Just copy them from
https://github.com/openshwprojects/OpenBK7231T_App/pull/1718
https://github.com/openshwprojects/OpenBK7231...75bccb32db85578cb9c7fa9/platforms/obk_main.mk

But even then, IR doesn't work yet on BK7238, if i remember correctly?
Probably timing issue, since BK7238 frequency is higher than BK7231

Ok, let's try to enable it:
https://github.com/openshwprojects/OpenBK7231T_App/pull/1750
I am not sure, just from the memory, do we need to update makefile as well or not.

insmod wrote:

But even then, IR doesn't work yet on BK7238, if i remember correctly?

there's this report https://www.elektroda.com/rtvforum/topic4131553-30.html#21621159

I've not tried anything BK7238 and ir myself yet

I think the pins are the same. Though I was not able to send code to AC unit successfully. Also, the led I use is WifiLED. LED did not work.

Quote:

"pins": {
"6": "IRSend;3",
"8": "IRRecv;2",
"9": "dInput;1",
"26": "WifiLED;2"
},

These 3 codes are for turn off unit, turn on AC, turn on heater. All produced the same code. My ac unit is a Mitsubishi Electric (Japan). Why it says PulseDistance. No idea. Also, my Toto toilet is showing PulseDistance with duplicate codes. As reference, I am currently using Broadlink RM3 & RM4 for these units with no issues.

Quote:

Info:IR:IR IR_PulseDistance 0x819 0x809 0 (40 bits)
Info:IR:IR IR_PulseDistance 0x819 0x809 0 (40 bits)
Info:IR:IR IR_PulseDistance 0x819 0x809 0 (40 bits)

These are the url links I have tried, but did not work.

Quote:

http://192.168.1.224/cm?cmnd=IRsend+PulseDistance-0x819-0x809
http://192.168.1.224/cm?cmnd=IRsend+PulseDistance-0x819-0x809
http://192.168.1.224/cm?cmnd=IRsend+PulseDistance-819-809-0

@divadiow @insmod
I'm checking IR for BK7238 (T1) on NiceMCU
IR2 driver with enabled DEBUG_WAVE_WITH_GPIO
https://github.com/openshwprojects/OpenBK7231T_App/pull/1756


Well so far the timer seems correct
10kHz frequency = 100us period = toggle every 50us


Added after 3 [minutes]:

That was from Beken timer, unmodified, so it's same as on BK7231.
10kHz is the same what @DeDaMrAz saw with me when we were creating IR2 driver back in July 2024:



Ok, what about PWM? Default frequency, 50 value in channel, BK7238 P9:

Also seems ok.. default PWM in OBK is 1 kHz.

Added after 2 [minutes]:

Let's change to 500Hz:

Ok...


Added after 15 [minutes]:

Seems to work out of the box on NiceMCU? However, I noticed that my previous IR receiver was faulty. Hmm.



Added after 8 [minutes]:

Events are working for RC6 (out of the box). NiceMCU config:

Script:

Video: