ubertooth (SqueakyFloors) errors

5 recurring problems engineers report in ubertooth (SqueakyFloors), ranked by impact.

#108 by errors trackedFirmware

Recurring ubertooth (SqueakyFloors) errors, by impact

  1. 1CI checks the revision inside each .bin, but the .dfu users are told to flash is never built or checked in CI, so a packaging, suffix, or ID break would pass every job and surface when someone tries to flash a board.Firmware · Agent failure · 1 report74
  2. 2The badge radio range test writes and reads the CC2400 FIFO one byte per SPI transaction, so packets go out with no data and reads come back as zeros, while the CRC_OK flag is set either way because zeros from an empty FIFO satisfy it.Firmware · Agent failure · 1 report74
  3. 3After #791, tests that claimed to check Select Endpoint vs Clear Interrupt could not: the USB fake stored the command register without acting on it, so putting the clearing form back on main still passed all 213 checks; now the fake runs the command and the same revert fails 22 checks across 10 tests.Firmware · Agent failure · 1 report66
  4. 4One DMA error ends a BLE capture forever; the loop keeps feeding the watchdog and answering control requests, so the capture looks alive and records nothing until the tool is killed.Firmware · Agent failure · 1 report66
  5. 5Setting the channel while the board is still in LE follow mode returns success but keeps the old channel, so the next capture runs on the wrong frequency with nothing to say so.Firmware · Agent failure · 1 report66

How it fails

  1. Agent failure5

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.