I just finished rebuilding my adapter thingy for EEPROM sniffing and have all the lines labeled. It was giving a fail 84 and it turns out that if anything is wrong as in being plugged in wrong or what not the?EEPROM is easily corrupted, probably the WE being engaged when it shouldn't. It seems to be solid now. ?I'm using a 2k chip so the extra 4 pins are not utilized (24 pin part). Already seeing some interesting things if my connections are correct. It appears it's hitting up the EEPROM every 4.6 milliseconds to grab some data but not all that much data, like 13 or 15 bursts of one bit width of data then it recycles but the patterns are not exactly the same. Write enable does go active quite often as well which is interesting but from what I'm seeing just in looking briefly just now it's not simultaneous to CE of the EEPROM so perhaps it's writing something else....dunno...strange.? I'm still learning DSView since everything I do involves me doing a cannonbal?into the deepest end then flailing around learning the tools and methods simultaneously. I will try to push out a file here in a bit and anyone should be able to grab DSView since it's free and view it.? What speed and file size should I use? I am using the DSLogic U3Pro32. Right now I'm just looking at 1 second at 1 Mhz with it sitting on a channel not scanning and zero options enabled, not even PL. I think it's RX 30.000, TX 31.000 TA freq 32.000.? LOL I just did a 1 Mhz 20 second read and exported to CSV. It created a 1 Gb Excel file. Damn! On Sat, Aug 6, 2022 at 7:50 AM Skip Hansen <skip@...> wrote:
|