Closed mattbradford83 closed 3 years ago
Thank you @mattbradford83 , It may take us a few days before we are able to merge and test this (we have many other things going on at the moment). Please feel free to give us a nudge here if you think this is taking too long. Thanks again - and very best wishes, Paul
Hey @PaulZC how's this one going?
Hi @mattbradford83 ,
Thanks for the reminder! ;-)
Can you please re-target your PR at the release-candidate branch so I can merge and test it? Contributing guidelines are here.
Many thanks, Paul
Well, there you go. I learned something new today! ;-) I can change the targeted branch. (Previously I thought only the person submitting the PR could do that...) Merging... Thanks! Paul
Great library with lots of great features for debugging this troublesome chip. One thing that appears to be missing is the tracking of the "Reset Complete" Executable response packet (BNO08X documentation, P24, fig 1-27). This is needed to determine if the chip resets unexpectedly, so that reports can be re-set. It also pairs really well with the resetReason() function. I've added some code to document this working, along with an example of how to use it to show a software reset.