the comms logs with timestamps is perfect!
and typing notes about your observations in there is great too.
the noisy comms messages are during initial connection which is obviously having some grief.
first it tests to see if the bus is quiet.
if it's not, it listens to determine the current bus master
then it tries to silence the bus master.
it listens again to see if it's quiet
and repeat..
edit: right at the beginning of your log you flash C:/Program Files (x86)/EEHack/BINs/floridabin1_From_flashhack.bin
and the operation is successful (and checksum verified)
i don't see a failed write after that
so it failed before? do you remember what kind of errors came up?
Bookmarks