Skip to content

Report more data in bose-dfu info #7

@tchebb

Description

@tchebb

Currently, we query three different fields from the device, each of which has a two-digit identifier:

bose-dfu/src/protocol.rs

Lines 160 to 167 in f79694c

// Packet captures indicate that "lc" is also a valid field type for some devices, but on mine
// it always returns a bus error (both when I send it and when the official updater does).
request_report[0] = INFO_REPORT_ID;
request_report[1..3].copy_from_slice(match field {
DeviceModel => b"pl",
SerialNumber => b"sn",
CurrentFirmware => b"vr",
});

Those three identifiers (plus lc, which I couldn't get working as per the comment) were the only ones I was able to learn from USB captures. But by searching firmware binaries for known strings that get returned from info requests, I've found indications of other identifiers that might return different data. I haven't disassembled the source—this is purely based on strings that occur near each other—so there's no guarantee they're what I think they are. But it's worth trying them out anyway to see if they return anything interesting.

So far, I've looked at the SoundLink Color II (Foreman) and SoundLink Mini II (KCup) firmware images.

Both

  • vr (known)
  • v2
  • v4
  • pl (known)
  • sn (known)
  • lc (known, not working)
  • la
  • bt
  • sr
  • sh
  • fd
  • pw
  • uq

SoundLink Color II only

  • db
  • mq
  • ep
  • ua
  • aa

SoundLink Mini II only

  • rs
  • list (unsure why not 2 characters like the others)
  • hr
  • vo

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions