First make sure you have the serial connector connected properly to our evaluation board.
See How to connect evaluation board to your platform HW
If these requirements are satisfied, then the following entries in the log file should appear:
17:17:57 11/20/07 %225843D INIT_STAGE A: Soft Reset of ASIC
17:17:57 11/20/07 %225843E @^@ha34BBASQAgICAgICAgICAgICAgICAgP4A/QAAVaoA//wAAAAAAAAAAAAA
17:17:57 11/20/07 %225843E @^@ha14BBAQwA/gD9byIA3sCtC/38
The strings started with "@^@ha" prefix contain the data traffic between ASIC and HOST. This data can be converted to the human readable format using the glb64decode.exe utility:
glb64decode.exe -i log.txt -o log-encoded.txt
Where
The snippet of the log file above now will look like this:
17:17:57 11/20/07 %225843D INIT_STAGE A: Soft Reset of ASIC
17:17:57 11/20/07 %225843E @^@ha34BBASQAgICAgICAgICAgICAgICAgP4A/QAAVaoA//wAAAAAAAAAAAAA
H->A 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 fe 00 fd 00 00 55 aa 00 ff fc 00 00 00 00 00 00 00 00 00 00
17:17:57 11/20/07 %225843E @^@ha14BBAQwA/gD9byIA3sCtC/38
H->A fe 00 fd 6f 22 00 de c0 ad 0b fd fc
This output from the log file can now be compared with output captured by the serial traffic analyzer. They should match exactly, in other hands all data marked with H->A must be seen in the capture from HOST to ASIC, and all data captured from ASIC to HOST should be seen in the lines marked with H<-A
We use this serial traffic sniffer: http://www.iftools.com/#msba