Difference between revisions of "JTAG explorer toy"

From Electriki
Jump to navigationJump to search
Line 1: Line 1:
 
[[Image:Batman.jpg|thumb|'''Fig.1: batman.''' Holy mackerel Batman! JTAG really is THE SHIT!!1]]
 
[[Image:Batman.jpg|thumb|'''Fig.1: batman.''' Holy mackerel Batman! JTAG really is THE SHIT!!1]]
  
[[Image:michai_015_schem.jpg|thumb|'''Fig.2: schematics.''' The only slightly interesting bits are the 4 TAP-lines going between the MCU's, and the fact they share mutually-exclusive use of the serial Tx-line (the Rx-line is always shared).]]
+
[[Image:michai_015_schem.jpg|thumb|'''Fig.2: toy-board schematics.''' The only slightly interesting bits are the 4 TAP-lines going between the MCU's, and the fact they share mutually-exclusive use of the serial Tx-line (the Rx-line is always shared).]]
  
 
[[Image:michai_015_bscan.jpg|thumb|'''Fig.3: JTAG boundary-scan chain.''' A host talks to the TAP (''Test Access Port'') controller using 4 lines, shifting data in and out.]]
 
[[Image:michai_015_bscan.jpg|thumb|'''Fig.3: JTAG boundary-scan chain.''' A host talks to the TAP (''Test Access Port'') controller using 4 lines, shifting data in and out.]]

Revision as of 16:41, 4 January 2009

Fig.1: batman. Holy mackerel Batman! JTAG really is THE SHIT!!1
Fig.2: toy-board schematics. The only slightly interesting bits are the 4 TAP-lines going between the MCU's, and the fact they share mutually-exclusive use of the serial Tx-line (the Rx-line is always shared).
Fig.3: JTAG boundary-scan chain. A host talks to the TAP (Test Access Port) controller using 4 lines, shifting data in and out.
Fig.4: 2 JTAG boundary-scan cells. One cell sits between core logic and an input pin, and the other sits between core logic and an output pin.
Fig.5: 'before'. The big MCU there (ATmega32) is horribly oversized both in size and ability for this application, but ok, was all I had.
Fig.6: 'after'. Finished toy-board. The funny thing is that when it's finished and toying has been done, it'll totally useless.

LALALA

la.