logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

NiceMCU XH-WB3S BK7238 Flashing, Testing, Pinout, Development, Porting

divadiow 6630 223
ADVERTISEMENT
Reply | New topic
  • ADVERTISEMENT
  • #122 21509919
    insmod
    Level 23  
    >>21509907
    Looking at features on bekencorp site, BK7231U is like BK7231S, but with possibility of ram/flash extension via qspi. So all in all, BK7231S is just an earlier version of BK7231U. Maybe you should try to spi flash S dump to U?

    Updated PSK pull-request, now powersave will just check if BL0937 driver is running. If not running - mcu ps will be enabled. It will break combos of BL0937 and DS18B20/DHT, at least until https://github.com/openshwprojects/OpenBK7231T_App/pull/1579 is merged.

    Still need someone to test bl0937 on T with new sdk, i need to see if the problem is N only or something that affects all chips (meaning something in sdk is wrong).
    Shall i port BK7252? I see little reason to do so, considering it is often used in cameras.
  • ADVERTISEMENT
  • #123 21510004
    divadiow
    Level 34  
    insmod wrote:
    Maybe you should try to spi flash S dump to U?


    can do. I expect it will probably work, or mirror this, which I wrote on Discord in August after flashing (but not full spi) to C-8133U:

    Code: Text
    Log in, to see the code


    Quote:
    Still need someone to test bl0937 on T with new sdk


    one of my lost replies stated that I couldn't find any ready-to-go T/BL0937 combos in my collection (only T/BL0942) and I guessed the Arduino emulator sketch wouldn't be good enough to really satisfy testing. But, oh, I can surely replace a CB2S/LN-02 with a WB2S or something - I must have a few of those options at least.

    insmod wrote:
    Shall i port BK7252? I see little reason to do so, considering it is often used in cameras


    I'm a yes please, of course! But your call. I could shout about it on all the places that people have asked for BK7252/cam alternatives and maybe it'll attract others to do cam driver/wrapper development. It could kickstart quite a development flurry?
  • #125 21510688
    divadiow
    Level 34  
    >>21510653

    tasty. any changes caught your eye?
  • ADVERTISEMENT
  • #126 21510693
    insmod
    Level 23  
    >>21510688 Since there is no changelog, i'll just have to import the whole tree.
    Haven't done that yet, still porting 7252. I'm a little stuck on it. My camera only has 2mb of flash, but it tries to erase beyond that.
    Code: text Expand Select all Copy to clipboard
    V(0.1.3)
CPSR:0x000000D3
R0:0xF5D3F9F3
R1:0xBCAFFFDF
R2:0xFF7FBE7B
R3:0xEFFBABFD
R4:0xD7FFFAD7
R5:0xFBF5FFFB
R6:0xAFFBFFFF
R7:0x5FFFBFC7
R8:0x3F76D6FF
R9:0xFFFFB1BF
R10:0xEFFBABFD
R11:0xF7FFE5FB
R12:0xFEDE3FD9
R13:0xFB7B7FBF
R14(LR):0x7FFFFDFD
[I/FAL] Fal(V0.4.0)success
[I/OTA] RT-Thread OTA package(V0.2.4) initialize success.
[E/OTA] (ota_main:290) App verify failed! Need to recovery factory firmware.


go os_addr(0x10000)..........
prvHeapInit-start addr:0x418198, size:163432
prvHeapInit-start addr:0x900000, size:262144
[Flash]id:0x1c7015
--write status reg:b4,1--
[Flash]init over
QSPi_init
QSPi_init1
sctrl_sta_ps_init
SDK Rev: 3.0.70 943bdd1
OSK Rev: F-3.0.44 943bdd1
cset:0 0 0 0
Entering initLog()...
Commands registered!
initLog() done!
--write status reg:80,1--
--write status reg:fc,1--
--write status reg:80,1--
Erase error:invalid address0x201000
Erase error:invalid address0x202000
--write status reg:fc,1--
--write status reg:80,1--
Write error[addr:0x201000 len:0x4]
--write status reg:fc,1--
--write status reg:80,1--
--write status reg:fc,1--
--write status reg:80,1--
Erase error:invalid address0x201000
Erase error:invalid address0x202000

    And loops
  • #129 21510699
    divadiow
    Level 34  
    ok. give me a mo. just fiddling with BK7231S/U

    Added after 1 [hours] 8 [minutes]:

    divadiow wrote:
    can do. I expect it will probably work, or mirror this, which I wrote on Discord in August after flashing (but not full spi) to C-8133U:

    yes. spi flash of LED driver firmware shipped on BK7231S/C-8133U modules does boot on HLK-B30/CC8000

    I'd forgotten also there's this CC8000 dump from a Leedarson module that I'd already flashed to HLK-B30 and was discovered by the AiDot app https://www.elektroda.com/rtvforum/topic3941318-30.html#21054699
  • #130 21510817
    insmod
    Level 23  
    I just noticed that your bk7252 device is tuya-made. That means flash is encrypted, my binaries won't work.
  • #131 21510820
    divadiow
    Level 34  
    >>21510817

    bum OK.

    Just soldering up a CB2S in a plug with BL0937 in place of WL2S.
  • #132 21510847
    p.kaczmarek2
    Moderator Smart Home  
    I think I have one bk7252 camera, but as far as I remember, I've accidentally overwrote bootloader so now I will most likely need to do SPI recovery, which may be hard if pins are not accessible..

    Some time ago I tried getting another A9, but got that:
    Close-up of a circuit board with an XF16 chip and a USB port.
    Disassembled camera with electronic components on a wooden table.
    Helpful post? Buy me a coffee.
  • Helpful post
    #133 21510860
    insmod
    Level 23  
    I got BK7252 to boot, but OTA doesn't work. Probably bootloader problem
    Code: text Expand Select all Copy to clipboard
    nfo:OTA:1b0000
Info:OTA:
Info:OTA:close OTA, additional 0xd60 FF added 
Info:OTA:1b1000
--write status reg:34,1--
Info:OTA:close OTA, addr 0x1b1400
--write status reg:0,1--
--write status reg:7c,1--
Info:MAIN:Time 63, idle 0/s, free 359064, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 6/20 
Info:MAIN:Module reboot in 2...
Info:MAIN:Time 64, idle 0/s, free 373360, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 5/20 
Info:MAIN:Module reboot in 1...
bk_reboot(1)
wdt reboot

V(0.1.3)
CPSR:0x000000D3
R0:0x00000000
R1:0x00000003
R2:0x0E330001
R3:0x00000000
R4:0x000B278B
R5:0x004093AC
R6:0x000C3304
R7:0xFFFFFFFF
R8:0x0000800D
R9:0x00000002
R10:0x00000000
R11:0x11111111
R12:0x00000075
R13:0x00403BF8
R14(LR):0x000119A8
[I/FAL] Fal(V0.4.0)success
[I/OTA] RT-Thread OTA package(V0.2.4) initialize success.
[E/OTA] (ota_main:290) App verify failed! Need to recovery factory firmware.


go os_addr(0x10000)..........
prvHeapInit-start addr:0x418268, size:163224
prvHeapInit-start addr:0x900000, size:262144
[Flash]id:0x1c7015
--write status reg:34,1--
[Flash]init over
QSPi_init
QSPi_init1
sctrl_sta_ps_init
SDK Rev: 3.0.76 13c04ee
OSK Rev: F-3.0.49 13c04ee
cset:0 0 0 0
Entering initLog()...
Commands registered!
initLog() done!
--write status reg:0,1--
--write status reg:7c,1--
--write status reg:0,1--
--write status reg:7c,1--
--write status reg:0,1--
--write status reg:7c,1--
--write status reg:0,1--
--write status reg:7c,1--
--write status reg:0,1--
--write status reg:7c,1--
Main_Init_Before_Delay done
Main_Init_Delay
No TLV header found in flash
[FUNC]rwnxl_init
chip id=7221a device id=18221020
IP Rev: W4-3.0.76-P0
txdesc flush
[FUNC]intc_init
[FUNC]calibration_main
No TLV header found in flash

rfcali_mode:1, 0
*********** finally result **********
gtx_dcorMod            : 0x8
gtx_dcorPA             : 0xa
gtx_pre_gain           : 0x10
gtx_i_dc_comp          : 0x1f6
gtx_q_dc_comp          : 0x209
gtx_i_gain_comp        : 0x3f7
gtx_q_gain_comp        : 0x3ff
gtx_ifilter_corner over: 0x10
gtx_qfilter_corner over: 0x10
gtx_phase_comp         : 0x1d3
gtx_phase_ty2          : 0x201
gbias_after_cal        : 0x19
gav_tssi               : 0x0
g_rx_dc_gain_tab 0 over: 0x80748070
g_rx_dc_gain_tab 1 over: 0x88708870
g_rx_dc_gain_tab 2 over: 0x98689868
g_rx_dc_gain_tab 3 over: 0xd04cb454
g_rx_dc_gain_tab 4 over: 0xd248d048
g_rx_dc_gain_tab 5 over: 0xd64cd24c
g_rx_dc_gain_tab 6 over: 0xd24ed54c
g_rx_dc_gain_tab 7 over: 0xd24ed650
grx_amp_err_wr         : 0x211
grx_phase_err_wr       : 0x01a
**************************************
NO RF TLV in flash, write def tab
calibration_main(07b911b30) over
NO TXPWR_TAB_TAB found in flash
Load default txpwr for b:0xd0251
Load default txpwr for g:0xd0287
fit n20 table with dist:2
Load default txpwr for n40:0xd0295
Load default txpwr for ble:0xd025f
NO TXID found in flash, use lpf i&q:16, 16
NO TXID found in flash, use def xtal:16
xtal in flash is:16
xtal_cali:16
rwnx_tpc_pa_map_init
[FUNC]ps_init
int watchdog enabled, period=10000
task watchdog enabled, period=60000
[FUNC]func_init_extended OVER!!!

start_type:3
Initializing TCP/IP stack
rf_thread_inbk_wlan_app_init finished
it ok

delaying start
Info:MAIN:Main_Init_Before_Delay
Info:CFG:####### Boot Count 2 #######
Warn:CFG:CFG_InitAndLoad: Correct#Startup delayed 0ms#
 config has been loaded with 2 changes count.
Error:CMD:lfs is absent
Info:GEN:PIN_SetupPi#Startup delayed 10ms#
ns pins have been set up.
Info:MAIN:Main_Init_Before_Delay done
Info:MAIN:Main_Init_Delay#Startup delayed 20ms#

#Startup delayed 30ms#
#Startup delayed 40ms#
#Startup delayed 50ms#
#Startup delayed 60ms#
#Startup delayed 70ms#
#Startup delayed 80ms#
#Startup delayed 90ms#

starting....
Main_Init_Delay done
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:Using SSID []
Info:MAIN:Using Pass []
Info:MQTT:MQTT_RegisterCallback called for bT obk8C428848/ subT obk8C428848/+/set
Info:MQTT:MQTT_RegisterCallback called for bT obks/ subT obks/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/obk8C428848/ subT cmnd/obk8C428848/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/obks/ subT cmnd/obks/+
Info:MQTT:MQTT_RegisterCallback called for bT obk8C428848/ subT obk8C428848/+/get
Info:CMD:CMD_StartScript: started @startup at the beginning
Error:CMD:LFS_ReadFile: lfs is absent
Info:CMD:CMD_StartScript: failed to get file autoexec.bat
Info:MAIN:Main_Init_After_Delay done
Info:HTTP:TCP server listening
Info:MAIN:Time 1, idle 0/s, free 392816, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/20 

    Sockets jump from 2 to 5 after ap is started.
    This was done with 3.0.76 sdk.
    Main change is a new chip, the BK7252N. And beginnings of BK7253 support.
  • #134 21510984
    divadiow
    Level 34  
    divadiow wrote:
    Just soldering up a CB2S in a plug with BL0937 in place of WL2S.


    right. What am I expecting to see and under what conditions? I see no spikes - no load and no calib yet
    Device configuration interface named OpenBK7231T displaying measurement data.

    Added after 1 [hours] 24 [minutes]:

    soldering iron from standby to 400c. Is the wavering between 230s to 240s indicative of the issue seen on N?

    OpenBK7231T energy monitoring system interface with an on button and displayed electrical parameters.
  • #136 21511229
    divadiow
    Level 34  
    insmod wrote:
    Are voltage drops similar with normal T firmware?


    no.

    new comparison this morning
    1.18.75
    OpenBK7231T interface screen with electrical data, off button.

    _7231u_t_c1b0ac146bf0
    Screenshot of an interface displaying electrical load information with identifier OpenBK7231T_E1EFE0F2.
  • #137 21511355
    p.kaczmarek2
    Moderator Smart Home  
    I have BK7231T with BL0937, what can I test?

    Screenshot displaying electrical energy measurements from the device BK7231T_LSPA9_BL0937, showing various voltage, current, and power values.
    A chart displaying the device's voltage, current, and power with system information.
    Probably I should update first.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #139 21511398
    p.kaczmarek2
    Moderator Smart Home  
    i see.. but maybe we should come up with some better approach to testing?
    Code: text Expand Select all Copy to clipboard
    
lfs_appendFloat log.txt $voltage

    Wait a sec, it seems there is some kind of bug, I'll need to debug this

    Added after 2 [minutes]:

    Console screen with a command tool for the BK7231T device.
    Source code snippet in C with the CMD_LFS_Append_Internal function.

    Added after 2 [minutes]:

    Strange, I was always working under assumption that snprintf will take NULL terminating character into the account.

    Added after 11 [minutes]:

    Ok I did a work around script:
    Code: text Expand Select all Copy to clipboard
    
addRepeatingEvent 1 -1 backlog lfs_appendInt log.txt $voltage*1000; lfs_append log.txt ,


    User interface for managing files in LittleFS.
    I'm on Built on Dec 1 2024 01:33:16 version charts_d447f3f91843

    Added after 1 [minutes]:

    My script :
    Spoiler:

    Code: text Expand Select all Copy to clipboard
    


startDriver charts
startDriver NTP
waitfor NTPState 1
// chart with max 100 samples, 3 variables and 3 separate vertical axes
// TODO: tune samples count
chart_create 100 3 3
// set variables along with their axes
chart_setVar 0 "Voltage" "axvolt"
chart_setVar 1 "Current" "axcurr"
chart_setVar 2 "Power" "axpower"
// setup axes
// axis_index, name, flags, label
chart_setAxis 0 "axvolt" 0 "Voltage (V)"
chart_setAxis 1 "axcurr" 1 "Current (A)"
chart_setAxis 2 "axpower" 2 "Power (W)"

// every 30 seconds, -1 means infinite repeats
// TODO: tune time here
addRepeatingEvent 30 -1 chart_addNow $voltage $current $power


//addRepeatingEvent 1 -1 SendGET http://192.168.0.169:8002/log.php?voltage=$voltage¤t=$current&power=$power

addRepeatingEvent 1 -1 backlog lfs_appendInt log.txt $voltage*1000; lfs_append log.txt ,



    Added after 6 [minutes]:

    EDIT: It seems that my LFS dump script has actually biased the results... the graph has started before I run my script.
    Charts of voltage, current, and power on a console background with a configuration menu.
    Code: text Expand Select all Copy to clipboard
    
229927,226752,226752,226896,226896,223432,223432,228195,228651,226586,227040,225308,225759,223721,223273,217947,132054,174213,223143,223143,225308,225308,225308,225308,224875,224875,215638,215638,217515,217515,493,224875,224875,211163,211163,217805,217370,225247,217709,218669,218669,214050,214050,214050,102105,152852,205101,205101,207122,207122,217081,217081,207844,207844,208277,208277,203514,203514,1091,209143,209143,213761,213761,219968,219968,217947,217947,200338,200338,201204,201204,201204,47233,104290,217514,217514,206545,206545,211308,211308,214483,214483,212174,212174,208854,363,213177,212326,194565,194565,213040,213466,207699,207284,212895,212895,211308,211308,211308,1648,19629,220986,220104,196395,188693,201060,201060,187059,187059,210009,210009,195142,448,183306,183306,199003,198209,198462,198462,201637,201637,194853,194853,190235,190235,54334,112726,199328,199328,178467,177754,206112,206112,203081,203081,186482,186482,186482,198,169595,169595,200482,200482,175719,175017,190326,189946,185101,185471,198606,198606,10117,48641,201204,201204,207699,207699,191338,190574,201781,201781,184894,184894,184894,185,164473,171327,212174,212174,183306,191372,166896,173865,214050,214050,216608,17069,63219,176811,176811,164687,164687,187781,187781,166752,166086,194132,194132,176,188647,188647,199183,199183,185616,185616,169883,170223,177020,175960,172193,9628,47197,193554,193554,165842,165842,188070,188070,172914,172914,170817,167169,167169,1,131113,172106,203150,180822,166479,138992,185018,175681,129981,176336,176336,6,1325,172325,147430,162895,177921,166188,203275,137760,170192,153531,153531,0,136993,147531,202503,193510,130397,126538,183367,194051,129121,150820,150820,0,379,174948,193200,159404,147232,104524,115758,182485,182830,143366,143366,6,98379,144617,113966,140409,150424,142084,181025,240143,105323,111815,4821,34155,152312,159787,171533,164386,178832,200292,132096,150109,167862,43,128723,128723,173544,178543,162557,183235,96465,111745,155334,145588,145588,0,485,101116,128321,130035,180475,92467,116004,220380,231340,231340,0,155638,169758,149285,145758,131194,180906,127551,134776,94049,104290,0,0,2,799,118983,161909,137972,139624,119382,168081,121565,56,173477,192371,131784,169687,97594,131583,130549,157735,132821,132821,0,0,3,833,135328,167563,126584,136906,154599,141001,141001,0,183316,131886,160468,177001,146509,
    Helpful post? Buy me a coffee.
  • #140 21511433
    divadiow
    Level 34  
    ok weird. I used your script (though charts isnt enabled on new-SDK PR anyway) and now the readings really are crazy after reboot.

    Screenshot of a control panel displaying OFF and energy usage data.

    removed autoexec entirely so no ntp even and now readings are frozen after reboot and even after counter reset. not sure what's happening. will flash back to general release and report back on change
  • #141 21511440
    p.kaczmarek2
    Moderator Smart Home  
    This is BL0937 code:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/driver/drv_bl0937.c
    The main part is here:
    Code: C / C++
    Log in, to see the code

    It should be time-agnostic as long as xTaskGetTickCount() is correct and calculations are correct.

    At first I would say that LFS operations are making EverySecond called less often than every second and we get time drift, but time calculation should take care of that.
    And we already had this PR:
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1280
    Helpful post? Buy me a coffee.
  • #142 21511447
    divadiow
    Level 34  
    OK. I have responsive BKT on PR build again. Had to unplug- not rebooting from GUI. Let me know if you want me to anything specific.
  • Helpful post
    #143 21511507
    p.kaczmarek2
    Moderator Smart Home  
    Currently I'm not sure what is happening with that BL0937. Maybe we need to set up a scenario in Simulator to test it or add more logging.

    Added after 4 [hours] 57 [minutes]:

    Did something happen to BK7231T build process?
    https://github.com/openshwprojects/OpenBK7231T_App/pull/1588
    Helpful post? Buy me a coffee.
  • #144 21511867
    insmod
    Level 23  
    >>21511507 Ubuntu 20.04 is being phased out from gh actions. Today is 'blackout' day.
    https://github.com/actions/runner-images/issues/11101
    Is otafix really needed for T? It was the reason i didn't move T builds to 22.04. It somehow fails to run on 22.04 actions, even if it works for me on 22.04 and 24.04.

    Added after 5 [hours] 9 [minutes]:

    I noticed that if i disable mqtt (on device, not in code), readings are much more consistent.
    I set it up in a way that default voltage is 250v. Readings are in 248-254 range for 7-9 seconds, then drops to 220-230 for 2-3 seconds then repeat again. But no drops below 200.

    @divadiow have you already tried to flash bk7252? I made it so that both zero keys and tuya ones are included in the build.
  • #145 21512391
    divadiow
    Level 34  
    insmod wrote:
    @divadiow have you already tried to flash bk7252? I made it so that both zero keys and tuya ones are included in the build.

    saw a little while ago. if you're following my blurb in the other thread you'll see UART flashing has been a no-go at any baud, adaptor, flash programme (LT and EF) so I've had to hook up the SPI way again. I've erased flash in Neo and tried both Tuya and non-Tuya QIO from 0x0. Sadly neither output any log on TX2 or TX1.

    I'm about to flash back original dump and then I guess maybe I should try flashing the UA or maybe even RBL to see if it OTAs. Any pointers on the addresses for these before I go looking?

    Added after 1 [minutes]:

    assuming original dump boots :/
  • #146 21512399
    insmod
    Level 23  
    >>21512391
    Usually you can find rbl header in dump.
    Mine was at 0x153f9a-0x153fff. So, logically i should flash rbl at 0x154000. But nothing happened after i did it.
    You shouldn't have tried to flash qio, both of them contains unencrypted bootloader.
  • #147 21512421
    divadiow
    Level 34  
    insmod wrote:
    You shouldn't have tried to flash qio, both of them contains unencrypted bootloader.

    :(

    Attempting to get into SPI now to reflash. what if it doesn't boot? :(

    Added after 8 [minutes]:

    🤬🤬🤬🤬 not looking good. when is a flash dump not a flash dump? what are the possibilities for why it wouldn't boot?

    Added after 6 [minutes]:

    false alarm. we're good :)

    I'll try some things and report back

    Added after 59 [minutes]:

    OK. I don't see the usual RBL headers in the dump. So went with the Tuya UA (transplanted into full dump) at 11000, which gives this on boot

    Code: Text
    Log in, to see the code


    or if transplanted to 11110 just:

    Code: Text
    Log in, to see the code


    this is what original dump looks like around here
    Flash memory dump in hexadecimal table form with signs of read errors.
  • #148 21512533
    p.kaczmarek2
    Moderator Smart Home  
    [quote="insmod,post=21511867"
    I noticed that if i disable mqtt (on device, not in code), readings are much more consistent.[/quote]
    The main question is where the problem is, are we getting skipped interrupt calls due to the CPU overheat? Maybe we could devise a simple test scenario to check that, with a simplest PWM signal generator and pin interrupt in a separate driver.

    One nicemcu as test device, second as PWM source. Create a simple driver, just count pulses, on every second get time delta and print pulses per seconds. It should be a constant value, no matter the stuff in backgrund...

    Maybe change interrupt priority in sDK?
    Helpful post? Buy me a coffee.
  • #149 21512537
    insmod
    Level 23  
    p.kaczmarek2 wrote:
    Maybe change interrupt priority in sDK?

    First thing i thought about after you mentioned xTaskGetTickCount.
    Two differences i noticed:
    new sdk THD_EXTENDED_APP_PRIORITY is 5, N sdk is 5+1.
    new sdk configTIMER_TASK_PRIORITY is 2, N sdk is 6.
    But changing them to N default values changed nothing.

    Added after 1 [hours]:

    It is logging that is the problem, after i turned off mqtt and gen (network info) off (in app, not in code), voltage became very stable.
    But since it was previously stated that writing to flash also breaking it, probably any 'heavy' load would break it. (but why is log so 'heavy' then?)

    @divadiow btw, have you thought about spi flashing T bootloader to U and vice versa? Ones from current dumps aren't suitable though, because U are unencrypted.
  • #150 21512675
    divadiow
    Level 34  
    insmod wrote:
    @divadiow btw, have you thought about spi flashing T bootloader to U and vice versa? Ones from current dumps aren't suitable though, because U are unencrypted.

    I don't recall. I'll set aside some time to see what works and what doesn't.
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the NiceMCU XH-WB3S development board, which utilizes the BK7238 chip. Users share experiences regarding flashing the device, testing its functionalities, and addressing issues related to encryption keys and firmware compatibility. There are debates about the correct identification of the chip (BK7238 vs. BK7231T) and the implications for development. Participants discuss the use of various tools for flashing, such as BKFIL and Easy Flasher, and the challenges faced with OTA updates and memory management. Additionally, there are insights into the SDKs available for development, including Arduino compatibility and the potential for porting OpenBeken firmware. The conversation also touches on specific sensor integrations, such as DHT11 and DS18B20, and the timing issues encountered during their operation.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT