On Tue, Oct 12, 2010 at 4:29 AM, Nicolas Pitre wrote:
>
> On Tue, 12 Oct 2010, Michael Hope wrote:
>
> > Ah, I see. You use the JTAG unit and on-chip debug hardware for the
> > kernel and use the JTAG-supplied DCC connection for applications. So
> > you can use the DCC instead of Ethernet or ser
On Tue, 12 Oct 2010, Michael Hope wrote:
> Ah, I see. You use the JTAG unit and on-chip debug hardware for the
> kernel and use the JTAG-supplied DCC connection for applications. So
> you can use the DCC instead of Ethernet or serial, which is nice as it
> frees up a port.
>
> You might want to
On Mon, Oct 11, 2010 at 8:06 PM, Øyvind Harboe wrote:
> On Mon, Oct 11, 2010 at 12:36 AM, Michael Hope
> wrote:
>> Hi Øyvind. You might want to ask the OpenOCD list about this. I've
>> used the DCC as an end user before for sending printf() style messages
>> and RPC over and it's quite good fo
On Mon, Oct 11, 2010 at 12:36 AM, Michael Hope wrote:
> Hi Øyvind. You might want to ask the OpenOCD list about this. I've
> used the DCC as an end user before for sending printf() style messages
> and RPC over and it's quite good for that.
I did, no response. (I'm also one of the main OpenOCD
Hi Øyvind. You might want to ask the OpenOCD list about this. I've
used the DCC as an end user before for sending printf() style messages
and RPC over and it's quite good for that.
I'm not sure how your proposal would work though. My understanding is
that the DCC is only accessible over JTAG an
Hi all,
I was wondering someone knows about a ARM DCC (debug
communications channel) device driver.
The idea is to run gdbserver on /dev/dcc such that application
debugging does not hog a serial/ethernet port.
I'd modify OpenOCD to forward the DCC onto a TCP/IP port
to connect GDB to the gdbserv
