linguini1 opened a new issue, #15826:
URL: https://github.com/apache/nuttx/issues/15826

   ### Description / Steps to reproduce the issue
   
   I am encountering numerous strange issues on the STM32H743.
   
   Floating point numbers seem to not work for the MS56xx driver, used on an 
MS5607.
   
   ```console
   Mointor objects num:1
   object_name:sensor_baro, object_instance:0
   
sensor_baro(now:18990000):timestamp:18990000,pressure:42948200.000000,temperature:21.870001
   
sensor_baro(now:19030000):timestamp:19030000,pressure:42948204.000000,temperature:21.809999
   
sensor_baro(now:19070000):timestamp:19070000,pressure:42948204.000000,temperature:21.760000
   
sensor_baro(now:19110000):timestamp:19110000,pressure:42948204.000000,temperature:21.760000
   
sensor_baro(now:19150000):timestamp:19150000,pressure:42948204.000000,temperature:21.760000
   
sensor_baro(now:19190000):timestamp:19190000,pressure:42948204.000000,temperature:21.879999
   
sensor_baro(now:19230000):timestamp:19230000,pressure:42948204.000000,temperature:21.700001
   
sensor_baro(now:19270000):timestamp:19270000,pressure:42948204.000000,temperature:21.750000
   
sensor_baro(now:19310000):timestamp:19310000,pressure:42948204.000000,temperature:21.700001
   
sensor_baro(now:19350000):timestamp:19350000,pressure:42948204.000000,temperature:21.809999
   Object name:sensor_baro0, recieved:10
   Total number of received Message:10/10
   ```
   
   I am also seeing strange floating point numbers on the LIS2MDL driver and 
LSM6DSO32 driver. Additionally, when running `uorb_listener`, the kernel panics 
if I try to read from the LSM6DSO32. I had an earlier kernel panic with `ps` 
which I resolved by increasing stack sizes as recommended in this issue: 
https://github.com/apache/nuttx/issues/11463
   
   I also cannot seem to get any information about the panic. I've enabled core 
dumps, scheduler and sensor error output, etc. without luck. If there are any 
suggestions on what I can enable or try to debug this and provide more 
information, please let me know. These drivers work without issue on RP2040 
based boards, so I am not sure what could be the issue.
   
   I have tried with the FPU enabled and disabled with the same results. I've 
increased every stack size option I could find to 4096 bytes without success.
   
   This is the output seen before the kernel crashes:
   ```console
   nsh> uorb_listener -n 10 sensor_accel0
   
   Mointor objects num:1
   object_name:sensor_accel, object_instance:0
   lsm6dso32_activate: About to lock
   lsm6dso32_activate: locked
   lsm6dso32_activate: About to set odr
   lsm6dso32_activate: odr set
   lsm6dso32_activate: Waking up LSM6DSO32 polling thread
   lsm6dso32_activate: LSM6DSO32 activated
   Waited for 5 seconds withou
   ```
   Then the output is cut off and the kernel panic status LED is activated. 
Some times the LED is held static, other times it blinks at 1Hz (for the same 
`uorb_listener` command).
   
   ### On which OS does this issue occur?
   
   [OS: Linux]
   
   ### What is the version of your OS?
   
   Arch Linux
   
   ### NuttX Version
   
   master
   
   ### Issue Architecture
   
   [Arch: arm]
   
   ### 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

Reply via email to