On Tue, Dec 20, 2011 at 4:04 PM, Steve Battazzo <[email protected]> wrote:
> Hi all,
>
> I have connected a new JTAG debugger based on FT2232D to our OR1200 using
> OpenOCD.
> This basically works OK, but the two LED indicators are always alternately
> flashing after I connect.
> Then, when I make a connection to GDB, I see the following messages:
>
> Warn : acknowledgement received, but no packet pending
> undefined debug reason 6 - target needs reset
>
> It's a bit inconsistent, but I also get strange behavior in GDB. It appears
> that loading the elf files is working very well, but about half of the time
> when I run "c" I get something like:
> "The target is not in the halted nor runing stated, stepi/continue ignored."
> followed by:
> "Program received signal SIGINT, Interrupt."
>
> At this point, the execution is at address 0x104 so it's happening on the
> first instruction.
>
> Anybody seen something like this?
> Or does anyone have any recommendation of what I can do to start looking at
> why this might be happening?
Hi Steve,
Nice to hear you're using OpenOCD. I've been wanting people to switch
over to that from or_debug_proxy for a while, so good on you for
taking the plunge!
I would dump out the program's debug info when running OpenOCD and
take a look. I have added in a lot of debug information to come out
when it's run. So enable that (the option escapes me right now, but
just turn on debugging to the highest level) and dump the trace (it'll
probably be quite long) from start to finish into pastebin, with
annotations (like "this is where I typed X into gdb" etc.) if you can.
That will shed light on what the OpenOCD software thinks it's doing,
anyway.
Once you do that I can look over the communication and potentially
pinpoint where things are going wrong.
Cheers,
Julius
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc
