]> sigrok.org Git - sigrok-dumps.git/blame - aud/README
st7735: Add a snippet file.
[sigrok-dumps.git] / aud / README
CommitLineData
84d7eaee 1-------------------------------------------------------------------------------
2Renesas/Hitachi AUD (Advanced User Debugger)
3-------------------------------------------------------------------------------
4
5This is a set of example captures of the Renesas/Hitachi AUD (Advanced User
6Debugger) protocol.
7
8Details:
9http://www.renesas.eu/products/mpumcu/superh/sh7050/sh7058/Documentation.jsp
10("rej09b0046 - SH7058 Hardware manual")
11
12
13Logic analyzer setup
14--------------------
15
16 Probe Pin
17 ---------------
18 1 AUDCK
19 2 nAUDSYNC
20 3 AUDATA3
21 4 AUDATA2
22 5 AUDATA1
23 6 AUDATA0
24
25The audgen-* files are artificially generated thus:
26
27 - audgen-01.v is written in Verilog; due to limitations in sigrok only
28 single-bit values are output.
29 - Icarus Verilog is run to create a VCD dump:
30 - "iverilog audgen-01.v"
31 - "./a.out" (created by iverilog)
32 - The resulting VCD can probably be opened directly by PulseView, but is
33 here converted to a .sr dump.
34
35AUD traffic can be challenging to capture because it is clocked out at the
36MCU's clock frequency (20MHz typical). This requires an LA capable of either:
37
38 - Timing analysis on 6 channels (clock, sync, data3..0) at >= 80MSps
39 (40MSps gives very inconsistent results)
40 - State analysis @ 20MHz, this would be "easy" but cheap hardware like
41 Logic/Logic16 can't do it.
42
43
44Data
45----
46
47Example to view decoded output:
48
49 sigrok-cli -i audgen-01.sr -P aud:audck=AUDCK:naudsync=nAUDSYNC:audata3=AUDATA3:audata2=AUDATA2:audata1=AUDATA1:audata0=AUDATA0
50