Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision | ||
| toh:meraki:mr18:jtag [2020/10/10 19:50] – fixed some typos k4my4b | toh:meraki:mr18:jtag [2021/09/06 23:21] – [Uploading a kernel] dddamion | ||
|---|---|---|---|
| Line 180: | Line 180: | ||
| Our plan to upload this code into the RAM of the device, and then point the CPU at it to execute, much like a bootloader would. | Our plan to upload this code into the RAM of the device, and then point the CPU at it to execute, much like a bootloader would. | ||
| - | Firstly, we need to catch the boot process early. This is important, as we need to boot our own kernel before any hardware peripherals in the device have begun to initialize. | + | Firstly, we need to catch the boot process early. This is important, as we need to boot our own kernel before any hardware peripherals in the device have begun to initialize, but late enough that the processor has been set up correctly by the existing Meraki bootloader. |
| + | |||
| + | On some devices this time window is very small. | ||
| + | Reports show the place to interrupt the boot process is during '' | ||
| + | |||
| + | [[https:// | ||
| + | Note: It appears to be impossible to get the correct timing if using POE. | ||
| Provide power to the MR18 and at that exact moment, run OpenOCD: | Provide power to the MR18 and at that exact moment, run OpenOCD: | ||