Template:BEAGLEBOARD RUNOCDBRIEF WIN
For more information, see Running OpenOCD on Windows. When you start OpenOCD, its output should look like this:
{{IMG_OCDSTARTUP_BEAGLE_{{{1}}}}}
JTAG-DP_STICKY_ERROR on startup
The -c init -c "reset init" commands in the OpenOCD startup are a workaround for a bug in OpenOCD that affects the Beagleboard and TI Beagleboard XM. If you start OpenOCD without these commands, you will see errors like this:
{{IMG_OCDSTARTUPERR_BEAGLE_{{{1}}}}}
If you see these errors, then the next time you try to start OpenOCD it will give an error the next time it tries to communicate with the Beagleboard. When you exit OpenOCD you will need to disconnect and reconnect the power cable to the Flyswatter before OpenOCD will be able to communicate with the Beagleboard again.
JTAG Tap Unexpected Errors
On startup you may sometimes encounter this error:
Info : JTAG tap: omap3530.jrc tap/device found: 0x000000ff (mfg: 0x07f, part: 0x0000, ver: 0x0) Warn : JTAG tap: omap3530.jrc UNEXPECTED: 0x000000ff (mfg: 0x07f, part: 0x0000, ver: 0x0) Error: JTAG tap: omap3530.jrc expected 1 of 1: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)
This output means OpenOCD has failed to initialize the JTAG chain. The -c init -c "reset init" commands are a partial workaround for this error. Look for the following line later in the output:
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)
If you see this line, everything is fine.
Troubleshooting
Getting OpenOCD to initialize JTAG correctly with the Beagleboard is sometimes difficult. If you are having difficulties beyond those described above, consult the troubleshooting page below.
