Max Maeder
Max Maeder
Hi, thanks for responding. I currently have the changes proposed in #71229 applied, and `anym-no-latch` set, as per your suggestion. I added a log statement to `lis2dh_thread_cb`, and it prints...
Thanks for the response, I'm now trying something like this, but the interrupt doesn't fire, nor does the print statement in the we added to `lis2dh_thread_cb` print. Did I configure...
I really appreciate it, when I call `sensor_attr_set`, this is printed ` lis2dh: int2_ths=0x3 range_g=2 ums2=499999`, which indicates that the threshold *should be* set correctly. Still no luck detecting actual...
> Did you probe the gpio line, is the hardware trigger actually firing? I know the hardware interrupt works as the anymotion trigger was working fine for me. Unfortunately, the...
@deveritec-rosc Any luck reproducing this issue?
@avisconti I checked out #69847, it is essentially a duplicate of #71229. They both change the same trigger mode. I've already tried applying the change, to no luck. The tap...
Just tried out your fixes, am seeing interrupt events being generated now and the driver is working! I set odr to 400 Hz, full scale to 2g, threshold as 0.5g,...
Ok, I got it working, thanks! However, my solution required me to 'hardcode' changing the registers into the driver code. There didn't appear to be any way to change these...
Yikes, sorry I guess I missed this. I'll look at pushing an update.