openocd fails to attach

Bug #784626 reported by Paolo Pisati
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
x-loader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

with the original MLO that comes with natty, openocd fails to attach:

Texas Instruments X-Loader 1.4.4ss (Mar 18 2011 - 14:14:59)

[flag@newluxor openOCD]$ sudo /home/flag/bin/openOCD/bin/openocd -s /home/flag/bin/openOCD/ -f /home/flag/bin/openOCD/share/openocd/scripts/interface/flyswatter.cfg -f /home/flag/bin/openOCD/share/openocd/scpts/board/ti_pandaboard.cfg
Open On-Chip Debugger 0.5.0-dev-00875-g6349a47 (2011-05-18-15:21)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
RCLK - adaptive
Using dbgbase = 0x80000000
force hard breakpoints
trst_only separate trst_push_pull
Info : RCLK (adaptive clock speed) not supported - fallback to 6000 kHz
Info : JTAG tap: omap4430.jrc tap/device found: 0x3b95c02f (mfg: 0x017, part: 0xb95c, ver: 0x3)
Info : JTAG tap: omap4430.dap enabled
Polling target failed, GDB will be halted. Polling again in 100ms
Polling target failed, GDB will be halted. Polling again in 300ms
Info : JTAG tap: omap4430.m30_dap enabled
Polling target failed, GDB will be halted. Polling again in 700ms
Info : JTAG tap: omap4430.m31_dap enabled

Warn : Invalid ACK 0x6 in JTAG-DP transaction
Polling target failed, GDB will be halted. Polling again in 1500ms
Polling target failed, GDB will be halted. Polling again in 3100ms
Polling target failed, GDB will be halted. Polling again in 6300ms
Polling target failed, GDB will be halted. Polling again in 6300ms
Polling target failed, GDB will be halted. Polling again in 6300ms
Polling target failed, GDB will be halted. Polling again in 6300ms
Polling target failed, GDB will be halted. Polling again in 6300ms

updating x-loader (b6bbfe7 - Fri Mar 25 12:58:05 2011) fixes the problem:

[flag@newluxor openOCD]$ sudo /home/flag/bin/openOCD/bin/openocd -s /home/flag/bin/openOCD/ -f /home/flag/bin/openOCD/share/openocd/scripts/interface/flyswatter.cfg -f /home/flag/bin/openOCD/share/openocd/scripts/board/ti_pandaboard.cfg
Open On-Chip Debugger 0.5.0-dev-00875-g6349a47 (2011-05-18-15:21)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
RCLK - adaptive
Using dbgbase = 0x80000000
force hard breakpoints
trst_only separate trst_push_pull
Info : RCLK (adaptive clock speed) not supported - fallback to 6000 kHz
Info : JTAG tap: omap4430.jrc tap/device found: 0x3b95c02f (mfg: 0x017, part: 0xb95c, ver: 0x3)
Info : JTAG tap: omap4430.dap enabled
Polling target failed, GDB will be halted. Polling again in 100ms
Polling target failed, GDB will be halted. Polling again in 300ms
Info : JTAG tap: omap4430.m30_dap enabled
Polling target failed, GDB will be halted. Polling again in 700ms
Info : JTAG tap: omap4430.m31_dap enabled
Info : omap4430.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : omap4430.m30: hardware has 6 breakpoints, 4 watchpoints
Info : omap4430.m31: hardware has 6 breakpoints, 4 watchpoints
Polling succeeded again

Tags: armel
Paolo Pisati (p-pisati)
tags: added: armel
Revision history for this message
Ricardo Salveti (rsalveti) wrote : Re: [Bug 784626] [NEW] openocd fails to attach

On Wed, May 18, 2011 at 11:27 AM, Paolo Pisati
<email address hidden> wrote:
> Public bug reported:
>
> with the original MLO that comes with natty, openocd fails to attach:
>
> Texas Instruments X-Loader 1.4.4ss (Mar 18 2011 - 14:14:59)

This is not the version delivered with Natty. Here's the log I have
from the release image:

Texas Instruments X-Loader 1.5.0 (Apr 11 2011 - 09:48:22)
Reading boot sector
Loading u-boot.bin from mmc

Revision history for this message
Paolo Pisati (p-pisati) wrote :

you are right, i've been using the x-loader from a beta1 natty image.

closing here.

Changed in x-loader (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.