linguini1 opened a new issue, #17030: URL: https://github.com/apache/nuttx/issues/17030
### Description / Steps to reproduce the issue This bug was noticed by @AngusJull during CU InSpace's rocket system testing. The uORB driver implementation for the MS56xx does not use the uORB provided function for getting the timestamp, and instead re-implements the logic using only an `unsigned long` for the microsecond resolution timestamp. This results in a roll-over much earlier than expected, affecting time-stamp quality. https://github.com/apache/nuttx/blob/34ca49b6f50d92d9a8ed87e40decb6b8a42f712b/drivers/sensors/ms56xx_uorb.c#L165C1-L172C1 I suggest this sensor be updated to use the `orb_absolute_time` function. Other uORB sensor implementations should be checked for this error as well. ### On which OS does this issue occur? [OS: Linux] ### What is the version of your OS? Arch Linux ### NuttX Version master ### Issue Architecture [Arch: all] ### Issue Area [Area: Drivers] ### Host information _No response_ ### Verification - [x] I have verified before submitting the report. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
