MaxineMuster

I tried to make a version with the changes below: [dev_20240821_115931.zip](https://github.com/user-attachments/files/16691296/dev_20240821_115931.zip) (since I don't have a BL602, I can't test and there is a slight danger, this version won't work...

> @MaxineMuster does this build also contain the trace statements by @giedriuslt just in case there are reboots to at least see where? Yes, my test-version is based on this...

> BENCH BL602 with serial logging using @MaxineMuster version: **12 hours no BL_RST and counting** I'm curious: Is temperature reading working? Are there some -999° readings (in this simple test...

> on version 655 Sorry to ask, but, did you try the "release" version or the firmware offered in this PR?

O.k., the fix tested here is not yet in release version, but only in the versions offered here. So your watchdog reset could still be caused by the infinite loop...

Could you please try this patch or the version attached for the driver code? ``` diff --git a/src/driver/drv_ds1820_simple.c b/src/driver/drv_ds1820_simple.c index be59a73b..e42869c7 100644 @@ -308,6 +309,29 @@ int OWTouchByte(int Pin, int...

BTW: What duration is shown in log for the "usleepds()" loops on BL602 if sensor is not attached? Maybe we can "tweak" the number of nop lines for BL602, too?

I would appreciate your feedback on this approach! I made some tests here with LN882H and BK7231N an "usleepds" works "o.k." (still with some bad readings from time to time)...

> I did test disabling interrupts and not, disabling interrupts improves reading accuracy a lot: Tested both for more than 20 hours. > > 2011/15556 or ~13% failed reading without...

I also found this issue, but somehow fogott about... IIRC the "better" AP was shown in the list, so if that is the case, I'm not sure, if changing "scan_time"...