Mark Weaver wrote:
If you look at the 123 send log, you can see that each button in the
code set produces an enormous amount of data. This data doesn't
appear to be set up or anything -- in "normal" winTV use, each button
really does send that amount of stuff. Changing the code sets around
changes the data (as you would expect). The other logs are just power
on / power off.
If anyone has any more clues than that, I'd be very grateful!
What I notice is this appears to be an upload into registers 01-63,
followed by an "execute" command. Note the first byte in the addr 70
writes is 01, then it sends 4 bytes, the next write starts at 5, goes 4
bytes, etc until it writes 0x61-0x63. Then it sends a 0x40 to register
0, which is probably an some sort of "prepare". Then it reads reg 0
until it changes to 0xa0, which I'm guessing means the blaster is ready
to send. Then it sends 0x80 to register 0, which I'd assume is
execute. It then polls register 0 until it changes can read back that
0x80.
I don't know wtf is going on on address 0x71, but I think those can be
safely ignored.
Now, what's in that block? Well the first byte is the length of the
block. The rest is a big ? for now. You might want to run some scripts
against the dumps and have them dump out the data blocks in a line so it
is easier to compare them for similarities.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
