11/10/2022 0 Comments Sanyo tool reset bq8030 datasheet![]() ![]() (I wasn't really bothered by the chip dying as this was one of 2 sacrificial controller boards I kept just for messing around with.) And the results? Apparently we can corrupt (ideally just) the first couple of blocks of flash if we bully PIN #28 while the chip is trying to start up. Is the chip fried? It's at this point that I coded up the flash tool to try and read the flash contents. ![]() Well that's not good! It seems we're stuck in the Boot ROM. SANYO TOOL RESET BQ8030 DATASHEET SERIAL$ smbusb_sbsreport SMBusb Firmware Version: 1.0.1 - Manufacturer Name: ERROR Device Name: ERROR Device Chemistry: ERROR Serial Number: Manufacture Date: 1980.00.00 Uh-oh. Scan range: 00 - ff Skipping: None - ACK, Byte writable, Word writable, Block writable ACK ACK ACK ACK, Byte writable, Word writable, Block writable ACK, Byte writable, Word writable, Block writable ACK, Byte writable, Word writable ACK, Byte writable, Word writable ACK ACK, Byte writable, Word writable ACK, Byte writable, Word writable Wow, that worked? Let's just reset for now. $ smbusb_scan -w 0x16 - smbusb_scan - SMBusb Firmware Version: 1.0.1 Scanning for command writability. 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. The connection between the BQ8030 and bq20z90 I opened up the datasheet for. No obvious BOOT pin as one would expect with a device that's not meant to be tampered with.īut maybe pulling some pin high or low during reset will get me somewhere. SANYO TOOL RESET BQ8030 DATASHEET FULLScan 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |