One log has filled the whole on-board flash chip

What ArduPilot says:

• Chip full, logging stopped

This board logs to a flash chip used as a ring: at the end it continues from the start, erasing the oldest logs as it goes. It stops only when the log being written has itself grown as large as the chip and would erase its own beginning. Logging then stops, the message repeats about once a minute, and the pre-arm checks say “Logging failed” until the logs are erased or the board is rebooted.

What to do, most likely first

1. LOG_DISARMED is on and the board stayed powered for a long time: one endless log.

   CheckLOG_DISARMED is 1 or 3, and the board sat on the bench or on USB for a long while.

   FixDownload what you need and erase the logs. Set LOG_DISARMED back to 0 unless you are chasing a start-up problem, or set LOG_FILE_DSRMROT to 1 so that every disarm closes the log and the next one starts fresh.

2. The flight is longer than the chip holds at this logging rate.

   CheckThe message appears in flight, after about the same time each flight. Many boards have only 16 MB of log flash.

   FixLog less: LOG_BLK_RATEMAX limits how many times a second each streamed message is written to the chip, and LOG_BITMASK without the fast attitude and raw IMU bits makes a much smaller log.

3. The board also has a card slot, and the flash chip was chosen by a copied parameter file.

   FixSet LOG_BACKEND_TYPE to 1 (File), fit a card and reboot: a card holds hours of logs.

Parameters to look at

Where to do it:Setup & Tuning Guide