Bosch Shared
- Top Results
See all results
- About alastair
- About alastair
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About alastair
since
05-11-2020
07-31-2023
alastair
Member
9
Posts
0
Likes
1
Solution
07-31-2023
10:25 AM
Is it possible to use the BMM350 as an auxilliary sensor with the BMI270? The BMI270 appears to only support a max aux sensor read size of 8 bytes, and the BMM350 has three registers per axis + temperature sensor for a total of 12 bytes. Even if we only wanted to use the two MSBs of each axis, it doesn't seem like this would be possible since there's no way to read non-contiguous registers automatically?
... View more
05-30-2020
12:37 AM
@Vincent wrote: Can you print out the frame header which you parse error to cause the function exited? Your implementation looks fine and our API is considering all possible FIFO frame header situation in our API code. It will only finish parsing if they met 0x8080 as padding bytes under FIFO header mode. The length for aux data is hardcoded, it's not using the setting as far as I can see. When I had the aux read size set to 6 I would expect a full frame to have 6 aux + 6 accel + 6 gyro = 18 bytes, but the library assumes 20 bytes, so as soon as it seems a frame with aux data in it it breaks.
... View more
05-24-2020
11:33 PM
I found the problem. The extract_xxx functions for extracting data from the FIFO use the record lengths in the fifo frame structure (e.g. fifo_all_frm_len), but these values are incorrectly populated by the library. They're set to hardcoded values rather than matching the actual configuration of the device. So.. setting the burst read length of the auxilliary sensor to anything other than 8 results in these functions producing incorrect results. I'm going to open a bug on the github repo with this but Bosch doesn't seem to pay any attention to these.
... View more
05-24-2020
10:07 PM
Even with that value fixed it doesn't work. Interestingly it made no difference to operation (6 bytes was correctly being read by the BMI270 with both settings), I guess the library masked off the top bit making the values 2 and 6 the same anyway.
... View more
Still looking for something?
- Top Results
See all results