Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:tp-link:tl-mr3420:debrick.using.jtag [2018/05/31 18:29] – patchwork.. bugger google benryanau | toh:tp-link:tl-mr3420:debrick.using.jtag [2018/05/31 18:46] – Fixup1 benryanau | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| The pinout of the [[http:// | The pinout of the [[http:// | ||
| ^ JTAG Common Name ^ AR724x Pin ^ Connector EJTAG for DIR-615 Ex ^ | ^ JTAG Common Name ^ AR724x Pin ^ Connector EJTAG for DIR-615 Ex ^ | ||
| - | | | <del> EJTAG_SEL </ del> // (do not use) // | 79 | {{: media: dlink: dir-615: e4-photos: d-link.dir-615e4-jtag.jpg? | + | | <del> EJTAG_SEL </ |
| - | | | ** TDI ** | 81 | ::: | | + | | ** TDI ** | 81 | ::: | |
| - | | | ** TDO ** | 82 | ::: | | + | | ** TDO ** | 82 | ::: | |
| - | | | ** TMS ** | 84 | ::: | | + | | ** TMS ** | 84 | ::: | |
| - | | | ** TCK ** | 85 | ::: | | + | | ** TCK ** | 85 | ::: | |
| - | | | <del> RST </ del> // (do not use) // | 93 | ::: | | + | | <del> RST </ |
| If there is no marking of the reference of the processor feet on the board, then one can use this orientation: | If there is no marking of the reference of the processor feet on the board, then one can use this orientation: | ||
| Line 27: | Line 27: | ||
| ** Note: ** Debugging and testing (for writing this instruction) was performed with a working loader, so it was necessary to temporarily disable the flash memory of the device (** CS0 ** => 3.3V), so that the device initialization and boot process was interrupted in the bootloader, there may be an instruction to disable the JTAG port to release the GPIO line). | ** Note: ** Debugging and testing (for writing this instruction) was performed with a working loader, so it was necessary to temporarily disable the flash memory of the device (** CS0 ** => 3.3V), so that the device initialization and boot process was interrupted in the bootloader, there may be an instruction to disable the JTAG port to release the GPIO line). | ||
| - | ** EJTAG_SEL ** pin - AR724 ** 0 ** / AR724 ** 1 ** / AR724 ** 2 ** Considering that EJTAG connector is not displayed on many devices - the logical state of this pin does not have a specific role for JTAG operation protocol. It's enough to interrupt the device boot from the flash memory, described in the above way. And if you consider that you are reading this manual - most likely, your device does not boot properly. | + | ** EJTAG_SEL ** pin - AR724**0**/ |
| - | ** RST ** pin - AR724 ** 0 ** / AR724 ** 1 ** / AR724 ** 2 ** completely resets the processor, i.e. including the recorded CPU initialization registers, this state is equivalent to disconnecting power from the device - therefore, we will not ** use this pin ** either. | + | ** RST ** pin - AR724**0**/ AR724**1**/ AR724**2** completely resets the processor, i.e. including the recorded CPU initialization registers, this state is equivalent to disconnecting power from the device - therefore, we will not ** use this pin ** either. |
| -> [[docs: techref: hardware: port.jtag.cables]] | -> [[docs: techref: hardware: port.jtag.cables]] | ||
| Line 42: | Line 42: | ||
| === Programs for working with JTAG === | === Programs for working with JTAG === | ||
| - | * ** OpenOCD ** ((If necessary, you can replace it with ** OCD Commander **, but remember that there is another format for sending registers to the processor, so the config file needs to be changed to this format.)) - [[http: // | + | * ** OpenOCD ** ((If necessary, you can replace it with ** OCD Commander **, but remember that there is another format for sending registers to the processor, so the config file needs to be changed to this format.)) - [[http: // |
| * ** PuTTY ** - '' | * ** PuTTY ** - '' | ||
| - | * ** [[# # init-ar7240.cfg | init-ar7240.cfg]] ** - config. file for the OpenOCD program and your device (config file, you need to copy it to the OpenOCD program folder as target / init-ar7240.cfg). | + | * ** [[# # init-ar7240.cfg | init-ar7240.cfg]] ** - config. file for the OpenOCD program and your device (config file, you need to copy it to the OpenOCD program folder as target / |
| * ** [[http:// | * ** [[http:// | ||
| - | | + | * ** backup.bin ** - a conditional bootloader or another piece of flash data that needs to be restored. \\ \\ ** Note: ** Note that the bootloader stores information about the MAC address (TP-Link: U-boot MAC offset 0x01fc00 (value in HEX format))) and the PIN code (TP-Link: U -boot PIN offset 0x01fe00 (value in Dec format))) of the device. It should also be aware that the ** art ** section used with EEPROM information for the wireless communication chip must match the wireless chip of the device being restored. \\ For example: ** art ** section of MR3420 router (WiFi Chip: AR9287) does not fit to MR3220 router (WiFi Chip: AR9285) and vice versa. |
| - | + | ||
| - | * ** backup.bin ** - a conditional bootloader or another piece of flash data that needs to be restored. | + | |
| === The OpenOCD commands used === | === The OpenOCD commands used === | ||
| - | < | + | < |
| - | // In the example presented in this section, the command is used as - identification of the identifier and device status, not more. Usually, when this command is executed, the ** nSRST ** is activated, but in our case ** RST ** pin is not the same .// | + | //B In the example presented in this section, the command is used as - identification of the identifier and device status, not more. Usually, when this command is executed, the ** nSRST ** is activated, but in our case ** RST ** pin is not the same .// |
| \\ | \\ | ||
| - | < | + | < |
| // Put the processor into debugging mode (accepting commands) .// | // Put the processor into debugging mode (accepting commands) .// | ||
| \\ | \\ | ||
| - | < | + | < |
| // After executing this command, the script for this event (enclosed in braces) will be executed, which is in the config. file (sending commands to the processor) .// | // After executing this command, the script for this event (enclosed in braces) will be executed, which is in the config. file (sending commands to the processor) .// | ||
| Line 74: | Line 72: | ||
| < | < | ||
| dump_image <file name> <start address in memory area or flash drive> < | dump_image <file name> <start address in memory area or flash drive> < | ||
| - | </ code> | + | </ |
| // This command saves the dump ** from ** the device' | // This command saves the dump ** from ** the device' | ||
| Line 81: | Line 79: | ||
| < | < | ||
| load_image <file name> <address in memory area only> <file format> | load_image <file name> <address in memory area only> <file format> | ||
| - | </ code> | + | </ |
| // This command loads the ** file into ** the device memory. The command must be executed ** after ** initializing the processor and device memory. // | // This command loads the ** file into ** the device memory. The command must be executed ** after ** initializing the processor and device memory. // | ||
| Line 88: | Line 86: | ||
| < | < | ||
| resume <address in memory area or flash drive> | resume <address in memory area or flash drive> | ||
| - | </ code> | + | </ |
| // This command starts the loader, analog ** go ** in uboot' | // This command starts the loader, analog ** go ** in uboot' | ||
| Line 174: | Line 172: | ||
| # serial SPI capable flash | # serial SPI capable flash | ||
| # flash bank < | # flash bank < | ||
| - | </ code> | + | </ |
| \\ | \\ | ||
| Line 189: | Line 187: | ||
| openocd-0.5.0.exe -f interface / parport.cfg -f target / init-ar7240.cfg | openocd-0.5.0.exe -f interface / parport.cfg -f target / init-ar7240.cfg | ||
| pause | pause | ||
| - | </ code> // If you use another JTAG adapter, then the name ** parport.cfg ** should be changed to the appropriate configuration file name for your JTAG adapter. // | + | </ |
| * Connect JTAG to the computer and ** disconnected ** the router. | * Connect JTAG to the computer and ** disconnected ** the router. | ||
| Line 217: | Line 215: | ||
| Info: JTAG tap: ar724x.cpu tap / device found: 0x00000001 (mfg: 0x000, part: 0x0000, ver: 0x0) | Info: JTAG tap: ar724x.cpu tap / device found: 0x00000001 (mfg: 0x000, part: 0x0000, ver: 0x0) | ||
| Info: accepting ' | Info: accepting ' | ||
| - | </ code> // If it was not possible to determine the identifier at once, try going to the next item and typing "'' | + | </ |
| * If everything went well, you need to start the console '' | * If everything went well, you need to start the console '' | ||
| Open On-Chip Debugger | Open On-Chip Debugger | ||
| > | > | ||
| - | </ code> \\ | + | </ |
| * Then enter the commands: \\ \\ < | * Then enter the commands: \\ \\ < | ||
| > reset | > reset | ||
| JTAG tap: ar724x.cpu tap / device found: 0x00000001 (mfg: 0x000, part: 0x0000, ver: 0x0) | JTAG tap: ar724x.cpu tap / device found: 0x00000001 (mfg: 0x000, part: 0x0000, ver: 0x0) | ||
| > | > | ||
| - | </ code> // This command should not affect the state of the processor. ** RST ** us we do not handle. However, the command once again determines the identifier and the state of the processor. // \\ \\ \\ < | + | </ |
| > halt | > halt | ||
| target state: halted | target state: halted | ||
| target halted in MIPS32 mode due to debug-request, | target halted in MIPS32 mode due to debug-request, | ||
| > | > | ||
| - | </ code> // This command switches the processor from the " | + | </ |
| > reset init | > reset init | ||
| JTAG tap: ar724x.cpu tap / device found: 0x00000001 (mfg: 0x000, part: 0x0000, ver: 0x0) | JTAG tap: ar724x.cpu tap / device found: 0x00000001 (mfg: 0x000, part: 0x0000, ver: 0x0) | ||
| Line 238: | Line 236: | ||
| target halted in MIPS32 mode due to debug-request, | target halted in MIPS32 mode due to debug-request, | ||
| > | > | ||
| - | </ code> // Initialize the main script in the configuration file ** [[# init-ar7240.cfg | init-ar7240.cfg]] **. In this case, the script sent a group of prisoners' | + | </ |
| > load_image backup_uboot.bin 0x81000000 bin | > load_image backup_uboot.bin 0x81000000 bin | ||
| 131072 bytes written at address 0x81000000 | 131072 bytes written at address 0x81000000 | ||
| Line 249: | Line 247: | ||
| downloaded 262144 bytes in 21.639999s (11.830 KiB / s) | downloaded 262144 bytes in 21.639999s (11.830 KiB / s) | ||
| > | > | ||
| - | </ code> // We load in advance somewhere into the memory, the loader ** u-boot ** and ** art ** section - later, this data will need to be copied to the flash memory. \\ The main thing we do is we load ** 8Muboot_RAM_version.bin ** the loader into the memory area 0x80000000 - the loader was compiled with reference to this address. // \\ \\ ** Note: ** It is possible to do only with the loader ** 8Muboot_RAM_version.bin ** (in the memory area 0x80000000) - using this bootloader, you can flash the flash using [[: en: toh: tp-link: tl-mr3420 # firmware.with the help.tftp | tftp method]] . \\ You should know the features of tftp, in this bootloader: | + | </ |
| * To access the bootloader, you need to enter ** tt ** | * To access the bootloader, you need to enter ** tt ** | ||
| * The IP address of the computer, at the same time, should be - 192.168.1.23 (or use the '' | * The IP address of the computer, at the same time, should be - 192.168.1.23 (or use the '' | ||
| * The following command will start the loader from the SDRAM area of the memory, simultaneously with this process, another console should be started ** PuTTY **, configured on the serial port: < | * The following command will start the loader from the SDRAM area of the memory, simultaneously with this process, another console should be started ** PuTTY **, configured on the serial port: < | ||
| resume 0x80000000 | resume 0x80000000 | ||
| - | </ code> // The loader will try to load ** firmware ** from the flash memory to prevent a failure (and as a result, the reboot of the router) - when the window " | + | </ |
| ==== Work in the bootloader U-boot ==== | ==== Work in the bootloader U-boot ==== | ||
| Line 265: | Line 263: | ||
| Erased 2 sectors | Erased 2 sectors | ||
| AR7241 # | AR7241 # | ||
| - | </ code> // Erase the area in the flash memory for the boot loader ** u-boot **. // | + | </ |
| \\ | \\ | ||
| Line 274: | Line 272: | ||
| done | done | ||
| AR7241 # | AR7241 # | ||
| - | </ code> // Copy from the SDRAM area of the memory, previously written ** u-boot ** bootloader, into the flash memory .// | + | </ |
| \\ | \\ | ||
| Line 284: | Line 282: | ||
| Erased 1 sectors | Erased 1 sectors | ||
| AR7241 # | AR7241 # | ||
| - | </ code> // Erase the area in the flash memory for the ** art ** section (flash memory ** 4M **) .// | + | </ |
| \\ | \\ | ||
| Line 293: | Line 291: | ||
| done | done | ||
| AR7241 # | AR7241 # | ||
| - | </ code> // Copy from the SDRAM area of the memory, previously written ** art ** section, into the flash memory .// | + | </ |