Either way, about 5 minutes of poking at PIN #28 with a resistor connected to 3.3v in hand and triggering RESET at random intervals while running a continuous command scan. Maybe I saw a presentation somewhere about blackbox chips and N/C pins years and years and years ago but I could just be imagining things. I have no logical explanation as to why I came to this decision. How about I try to abuse N/C pins instead. Or maybe there's no such combination at all. So maybe we have to set multiple pins into multiple states for it to work. But maybe pulling some pin high or low during reset will get me somewhere.Īfter the first pass no, not really. No obvious BOOT pin as one would expect with a device that's not meant to be tampered with. Scan range: 70 - ff Skipping: None - ACK, Byte writable, Word writable ACK ACK So this actually unlocks an extra command which disappears again when an SBS command is issued (or when doing a full command scan starting from 0.) The command however is not writable. $ smbusb_comm -a 16 -c 71 -w 0x0214 $ smbusb_scan -w 0x16 -b 0x70 - smbusb_scan - SMBusb Firmware Version: 1.0.0 Scanning for command writability. Includes Hardware, Full Software, Full Firmware DataBase, Cable, Dc power adapter.
Running on Windows 95, 98, ME, 2000, XP, Vista, Win7, Win 8.
