search

agwoska / hexiwear_apps

Implementations using Hexiwear
1 stars 0 forks source link

HTU thread error #1

Closed agwoska closed 2 years ago

agwoska commented 2 years ago

As a user, I do not want random crashes when using the HTU sensor and the device in general

Background Information When using the HTU screen for an extended period of time on Hexi_fullsensor2, an error appears seemingly at random. This is only happening to the HTU screen specifically. All other screen remain unaffected by this after extended testing. This only started happening after implementing the mutex into the system.

The error appears as such:

++ MbedOS Error Info ++
Error Status: 0x80010133 Code: 307 Module: 1
Error Message: Mutex: 0x20002710, Unknown
Location: 0x10005
Error Value: 0x20002710
Current Thread: application_unnamed_thread  Id: 0x20007A5C Entry: 0x8FD1 StackSize: 0x1000 StackMem: 0x2000D1A8 SP: 0x2002FF44 
For more info, visit: https://mbed.com/s/error?error=0x80010133&tgt=HEXIWEAR
-- MbedOS Error Info --

Link to more info for convenience: mbed

Note that the HTU may not need to be implemented for the final outcome.

Acceptance Criteria

agwoska commented 2 years ago

Check the new HTU driver recently created to see if the problem is fixed

agwoska commented 2 years ago

Driver is not the problem. Check the mutex for a deadlock issue.