You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently each nibble that appears on the LPC data lines is converted directly to an ASCII character representing the hexadecimal digit for it, which doubles the amount of data that needs to be sent. There is also a lot of unnecessary information such as the TAR and SYNC clock cycles when all we really need is the cycle type, addressing information, and data.
Changing the data format to something more structured that only stores the required information would cut down on the amount of data that needs to be stored and sent, as well as make it easier to parse the resulting dumps. Perhaps use something similar to the other existing lpc sniffer projects out there
The text was updated successfully, but these errors were encountered:
Currently each nibble that appears on the LPC data lines is converted directly to an ASCII character representing the hexadecimal digit for it, which doubles the amount of data that needs to be sent. There is also a lot of unnecessary information such as the TAR and SYNC clock cycles when all we really need is the cycle type, addressing information, and data.
Changing the data format to something more structured that only stores the required information would cut down on the amount of data that needs to be stored and sent, as well as make it easier to parse the resulting dumps. Perhaps use something similar to the other existing lpc sniffer projects out there
The text was updated successfully, but these errors were encountered: