summaryrefslogtreecommitdiff
path: root/src/ec
diff options
context:
space:
mode:
authorJimmy Zhang <jimmzhang@nvidia.com>2014-02-11 17:21:20 -0800
committerMarc Jones <marc.jones@se-eng.com>2014-11-12 20:16:53 +0100
commitbf04edaba71e61d8d2c7ee900c68fee82e0722c5 (patch)
tree9e5eace41f5381d44f1072e481af4a8f58667b06 /src/ec
parent7f0cb159994985dffe76ff034aae5a844386b447 (diff)
tegra124: enable JTAG in Security Mode
Once SECURITY_MODE fuse is burned, JTAG is disabled by default. To reenable JTAG, besides chip unique id and SecureJtagControl need to be built into BCT, Jtag enable flag is also needed to be set. BUG=None TEST=Burn SECURITY_MODE fuse, build chip specific BCT, coreboot comes up and jtag hooks up fine. Original-Change-Id: Ic6b61be2c09b15541400f9766d486a4fcef192a8 Original-Signed-off-by: Jimmy Zhang <jimmzhang@nvidia.com> Original-Reviewed-on: https://chromium-review.googlesource.com/186031 Original-Reviewed-by: Julius Werner <jwerner@chromium.org> (cherry picked from commit ff962b81f424c840ef171d4287a65ab79b018a28) Signed-off-by: Marc Jones <marc.jones@se-eng.com> Change-Id: I14b496932dbc0ed184a2212a5b33d740e1f34a4e Reviewed-on: http://review.coreboot.org/7403 Tested-by: build bot (Jenkins) Reviewed-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
Diffstat (limited to 'src/ec')
0 files changed, 0 insertions, 0 deletions