Doc: jtag_init must validate scan chain too
Same requirement as like init_reset, and for the same reason: we need to start with a known and working state.__archive__
parent
6726b78707
commit
6ec1026bbb
|
@ -1573,6 +1573,11 @@ which uses only a lightweight JTAG reset before examining the
|
|||
scan chain.
|
||||
If that fails, it tries again, using a harder reset
|
||||
from the overridable procedure @command{init_reset}.
|
||||
|
||||
Implementations must have verified the JTAG scan chain before
|
||||
they return.
|
||||
This is done by calling @command{jtag arp_init}
|
||||
(or @command{jtag arp_init-reset}).
|
||||
@end deffn
|
||||
|
||||
@anchor{TCP/IP Ports}
|
||||
|
|
Loading…
Reference in New Issue