New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added retries to FRAM init and read #13581
Conversation
@tridge We had some trouble with a CubeOrange with ADSB Carrier Board with lost parameter (default) on ArduPlane 4.0.4. After applying this PR on top of ArduPlane 4.0.4, the problems seems to be gone. |
This adds equivalent functionality that was originally added in: ArduPilot#13581
This adds equivalent functionality that was originally added in: ArduPilot#13581
This adds functionality similar to what was originally added in: ArduPilot#13581
this now incorporates many of the changes from @sypaq-nexton from #13621. It adds the retries and crc checks, as well as fixing fujitsu device support |
- added retries on all operations - detect errors with a CRC - fixed detection of fujitsu devices
this saves on flash and prevents confusing results when fram fails
@tridge: I've confirmed this works on our custom hardware with a Fujitsu FRAM chip (MB85RS128TY). |
This is an attempt to fix an intermittent issue reported where parameters are lost with FRAM based boards under certain power conditions.
It does 3 things:
The fallbacks are being disabled as they could be causing a board to change between different storage systems on different boots