00:07.56 | *** join/#openjtag _julian (~quassel@hmbg-4d06d70c.pool.mediaWays.net) |
00:15.28 | *** join/#openjtag drath (~vmaster@p4FDBDFDD.dip.t-dialin.net) |
02:33.04 | *** join/#openjtag roxfan (dunno@91.180.10.105) |
08:13.03 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
09:39.19 | *** join/#openjtag drath (~vmaster@p4FDBBC68.dip.t-dialin.net) |
10:13.44 | *** join/#openjtag Weaselweb (~quassel@77-64-193-225.dynamic.primacom.net) |
19:05.13 | *** join/#openjtag drath (~vmaster@p4FDBBC68.dip.t-dialin.net) |
21:00.25 | *** join/#openjtag juliusb (~jules@212-107-141-82.customers.ownit.se) |
21:00.37 | juliusb | hello there |
21:01.31 | juliusb | haha, is the topic's URL for real? |
21:28.02 | juliusb | anyway, i would like to add a debug target to openocd |
21:29.03 | juliusb | im currently maintaining a debug proxy, providing a GDB RSP server, and communicates to a debug core and TAP available on OpenCores, and ultimately, OpenRISC-processor based systems |
21:29.31 | juliusb | i mean it communicates and controls OpenRISC-based systems |
21:30.17 | juliusb | and instead of maintaining my proxy, which supports one kind of ft2232 debugger (the one available through opencores.org) I figure I just put support for the debug system into openocd, and hopefully gain more cable support |
21:31.16 | juliusb | does this sound like the sort of thing openocd could be used for? I figure at some point a different target system can be described? |