Upstream/lab-docu
1
0
Fork 0
mirror of https://github.com/Fohdeesha/lab-docu.git synced 2024-11-29 11:15:23 +01:00
Code Issues Projects Releases Wiki Activity

initial 6610 jtag updates

Browse Source
This commit is contained in:
Jon Sands 2019-10-29 03:22:54 -04:00
parent 69811e1fc9
commit f7c06ee98a
2 changed files with 18 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
documentation/jtag.md
View File

@ -1,10 +1,10 @@
# PowerPC JTAG Recovery # PowerPC JTAG Recovery (LB6M)
This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches using a BDI2000. This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches (LB6M) using a BDI2000.
## Preparation ## Preparation
Start by downloading [this ZIP](http://fohdeesha.com/data/other/jtag-recovery.zip). Start by downloading [this ZIP](http://fohdeesha.com/data/other/jtag-recovery.zip).
Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at 192.168.0.1 - make sure the TFTP server is running at this address. Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at the address you specified before the unit was shipped - make sure said TFTP server is running with above files before powering the BDI2000.
If the TFTP server is running on linux, you need to create an empty file in the TFTP root called `badboot.bin` - and give it write permission by running `CHMOD 777 badboot.bin` - this allows the JTAG unit to write to this file. if you are using a windows TFTP server, this shouldn't be necessary. If the TFTP server is running on linux, you need to create an empty file in the TFTP root called `badboot.bin` - and give it write permission by running `CHMOD 777 badboot.bin` - this allows the JTAG unit to write to this file. if you are using a windows TFTP server, this shouldn't be necessary.
@ -13,13 +13,11 @@ If you are outside the US, please plug the power brick into the wall first WITHO
If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off). If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off).
Now very carefully connect the other end of the power brick to the BDI2000 (the power brick should not be plugged into the wall yet) - plug it into the top set of power pins, matching the red and green stripes. MAKE SURE TO GET THIS RIGHT! See the following picture for the correct way: Now plug in the power supply to the BDI2000. Be gentle and make sure the key on the plug is facing the correct way - I had to hack up that power supply out of parts as it did not come with one.
![bdi-power](http://fohdeesha.com/data/other/bdipower.jpg)
Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up. Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up.
Using a telnet capable program like putty, telnet to the BDI2000 unit - it has been preconfigured with an IP of 192.168.0.2 - You should get output like the below, saying it's waiting for a target: Using a telnet capable program like putty, telnet to the BDI2000 unit - it has been preconfigured with the IP you specified before shipping - You should get output like the below, saying it's waiting for a target:
``` ```
TARGET: waiting for target Vcc TARGET: waiting for target Vcc
@ -27,7 +25,7 @@ TARGET: waiting for target Vcc
TARGET: waiting for target Vcc TARGET: waiting for target Vcc
``` ```
Now you must connect the BDI2000 to your switch. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on. Now you must connect the BDI2000 to the LB6M. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on.
Plug in the cable so pin #1 is on the left side, like this: Plug in the cable so pin #1 is on the left side, like this:

26
documentation/jtag6610.md
View File

@ -1,12 +1,10 @@
# TBD # PowerPC JTAG Recovery (ICX6610)
This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches (ICX6610 or FCX) using a BDI2000.
# PowerPC JTAG Recovery
This is a brief guide to recover corrupt bootloaders on PowerPC 85xx switches using a BDI2000.
## Preparation ## Preparation
Start by downloading [this ZIP](http://fohdeesha.com/data/other/jtag-recovery.zip). Start by downloading [this ZIP](http://fohdeesha.com/data/other/jtag-recovery-6610-fcx.zip).
Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at 192.168.0.1 - make sure the TFTP server is running at this address. Put all the files from the zip into the root of your TFTP server - the JTAG unit has been preprogrammed to look for a TFTP server at the address you specified before the unit was shipped - make sure said TFTP server is running with above files before powering the BDI2000.
If the TFTP server is running on linux, you need to create an empty file in the TFTP root called `badboot.bin` - and give it write permission by running `CHMOD 777 badboot.bin` - this allows the JTAG unit to write to this file. if you are using a windows TFTP server, this shouldn't be necessary. If the TFTP server is running on linux, you need to create an empty file in the TFTP root called `badboot.bin` - and give it write permission by running `CHMOD 777 badboot.bin` - this allows the JTAG unit to write to this file. if you are using a windows TFTP server, this shouldn't be necessary.
@ -15,13 +13,11 @@ If you are outside the US, please plug the power brick into the wall first WITHO
If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off). If you plug it into the wall and nothing happens (it shouldn't), unplug it from the wall. Now plug your ethernet cable into the BDI2000 (which should still be powered off).
Now very carefully connect the other end of the power brick to the BDI2000 (the power brick should not be plugged into the wall yet) - plug it into the top set of power pins, matching the red and green stripes. MAKE SURE TO GET THIS RIGHT! See the following picture for the correct way: Now plug in the power supply to the BDI2000. Be gentle and make sure the key on the plug is facing the correct way - I had to hack up that power supply out of parts as it did not come with one.
![bdi-power](http://fohdeesha.com/data/other/bdipower.jpg)
Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up. Once you are sure it is plugged in correctly, and it is also connected to your network via ethernet, plug the power brick into an outlet - the BDI2000 should power up.
Using a telnet capable program like putty, telnet to the BDI2000 unit - it has been preconfigured with an IP of 192.168.0.2 - You should get output like the below, saying it's waiting for a target: Using a telnet capable program like putty, telnet to the BDI2000 unit - it has been preconfigured with the IP you specified before shipping - You should get output like the below, saying it's waiting for a target:
``` ```
TARGET: waiting for target Vcc TARGET: waiting for target Vcc
@ -29,15 +25,17 @@ TARGET: waiting for target Vcc
TARGET: waiting for target Vcc TARGET: waiting for target Vcc
``` ```
Now you must connect the BDI2000 to your switch. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on. Now you must connect the BDI2000 to the ICX6610. Make sure the switch is unplugged and powered off! Find the 16-pin JTAG header on the switch. On the JTAG header, `1` should be printed on one side of the header to indicate pin number 1. Find which side of the header that `1` is on.
Plug in the cable so pin #1 is on the left side, like this: Plug in the cable so pin #1 is on the left side, like this:
![bdi-pins](http://fohdeesha.com/data/other/bdipins.jpg) ![bdi-pins](http://fohdeesha.com/data/other/bdipins.jpg)
On an LB6M, the connection should look like this: On an ICX6610, the connection should look like this:
![bdi-lb6m](http://fohdeesha.com/data/other/bdilb6m.jpg) ![bdi-6610](http://fohdeesha.com/data/other/bdi6610.jpg)
**Note:** The above picture is a 48 port ICX6610. The 24 port ICX6610 will have a slightly different board layout, and I believe the JTAG connector is on the opposite side.
Now that everything is plugged in and the BDI2000 is powered, power up the switch. Now that everything is plugged in and the BDI2000 is powered, power up the switch.
@ -85,7 +83,7 @@ Now we copy the bootloader from the TFTP server to onboard flash:
``` ```
prog 0xfff80000 brocadeboot.bin bin prog 0xfff80000 brocadeboot.bin bin
``` ```
When that finishes, connect a serial console cable to the LB6M switch (while it is still running and connected to JTAG). Open up a serial program so you can watch it's output. We will tell the switch to reset and run like normal (run the following command in the JTAG telnet console): When that finishes, connect a serial console cable to the switch (while it is still running and connected to JTAG). Open up a serial program so you can watch it's output. We will tell the switch to reset and run like normal (run the following command in the JTAG telnet console):
``` ```
reset run reset run
``` ```