w1kl4s/lab-docu
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

add correct 6610 jtag output

Browse Source
This commit is contained in:
Jon Sands
2019-10-29 17:15:58 -04:00
parent 48cea5ce44
commit e73f42dd60
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/jtag6610.md
View File

@@ -63,10 +63,10 @@ md 0xfff80000
``` ```
Depending on how corrupt your bootloader area is, you should see something that looks similar to the u-boot or brocade beginning contents below (might not match exactly, depending on what bootloader you are running): Depending on how corrupt your bootloader area is, you should see something that looks similar to the u-boot or brocade beginning contents below (might not match exactly, depending on what bootloader you are running):
``` ```
fff80000: 4d554348 02057be5 0005a2d6 00004058 MUCH..{.......@X 0_fff80000 : 4d554348 07f571f1 0005a807 00004058 MUCH..q.......@X
fff80010: 00000000 00012f2c 0004d880 00600028 ....../,.....`.( 0_fff80010 : 00000000 0001493e 0004ddb3 00600028 ......I>.....`.(
fff80020: 00030030 0004ffff ffffffff 00000000 ...0............ 0_fff80020 : 00030030 0004ffff ffffffff 00000000 ...0............
fff80030: 4e6ab6ae 07030000 74727a30 37333030 Nj......trz07300 0_fff80030 : 52b166af 0a010000 67727a31 30313030 R.f.....grz10100
``` ```
If you get something similar to above, the JTAG session is working. If you get something similar to above, the JTAG session is working.