On Dec 15, 2008, at 10:29 PM, Dirk Behme wrote:
Rick Altherr wrote:
I got a Flyswatter today to use with the BeagleBoard I got a week
ago. I just did some basic tests and it appears my hardware is
working. I'm going to start playing with the JTAG chain
configuration and hopefully I'l
Rick Altherr wrote:
> I got a Flyswatter today to use with the BeagleBoard I got a week ago.
> I just did some basic tests and it appears my hardware is working. I'm
> going to start playing with the JTAG chain configuration and hopefully
> I'll have a useable config file in a few days. Do
I got a Flyswatter today to use with the BeagleBoard I got a week
ago. I just did some basic tests and it appears my hardware is
working. I'm going to start playing with the JTAG chain configuration
and hopefully I'll have a useable config file in a few days. Does
anyone know what docume
andreas> Program received signal SIGSEGV, Segmentation fault.
andreas> 0x000519ec in interface_jtag_add_dr_out (device_num=0,
num_fields=0, num_bits=0x2, value=0xf1040, end_state=TAP_RTI) at jtag.c:721
andreas> 721 (*last_cmd)->cmd.scan->ir_scan = 0;
Hmm - Some ideas
1) As rick asks
On Mon, Dec 15, 2008 at 10:42:01AM -0800, Rick Altherr wrote:
> In the future, please don't start a new thread by replying to an old one
> and changing the subject line. It makes following the thread very
> confusing in the archives and when using a mail program that groups by
> thread.
Oops
On Dec 15, 2008, at 9:42 AM, lou.openocd...@fixit.nospammail.net wrote:
I'm working on adding support for a "new" interface, and I'm new to
this
project.
Should I just attach the patch (against svn trunk) and tar.gz file
to a
message in this list, or is submission supposed to work another
On Mon, Dec 15, 2008 at 6:42 PM, wrote:
> I'm working on adding support for a "new" interface, and I'm new to this
> project.
> Should I just attach the patch (against svn trunk) and tar.gz file to a
> message in this list, or is submission supposed to work another way?
That's it.
Remember to a
I'm working on adding support for a "new" interface, and I'm new to this
project.
Should I just attach the patch (against svn trunk) and tar.gz file to a
message in this list, or is submission supposed to work another way?
The tar archive is because svn diff doesn't produce patches which
include n
On Dec 15, 2008, at 8:32 AM, Andreas Kuehn wrote:
I compiled it with uClibc as part of an buildroot environment. Running
openocd from gdb with a well formed config file results in:
Info: JTAG device found: 0x0792603f (Manufacturer: 0x01f, Part:
0x7926, Version: 0x0)
Program received signal S
Thanks so far. You are right, to me the RTCK signal was somehow out of
sight. I added a loop that checks for the correct change on the RTCK
line and there is the feedback. It will receive some improvements but my
SIGSEGV problem is still there.
I compiled it with uClibc as part of an buildroot
> Hi,
>
> Find attached a patch (1st part) that enables openocd to talk
> to gdb using pipes (stdin, stdout) rather than sockets. It
> has been lying around my pc for about 6 months, thought it
> was about time to get it into trunk.
> It is enabled using the new cmd line option --pipe or -p
>
11 matches
Mail list logo
