Re: [Openocd-development] Connect to MIPS target using DLC5 cable

2008-12-16 Thread Andi
Hi Spencer, thanks for that hint. I was now able to successfully connect to my mips board! Thus, I would also vote for deleting the mips branch as that may confuse people (like me). Best regards Andi Spencer Oliver wrote: >> I grabbed the current release from the mips branch and >> compiled op

Re: [Openocd-development] Connect to MIPS target using DLC5 cable

2008-12-10 Thread Øyvind Harboe
> Should we just delete these old branches to avoid confusion? They would > still be in the repo, but wouldn't show up in the latest revisions. You > would need to check out a specific repo revision to see them. It gets my vote. I see no advantage to keeping them. -- Øyvind Harboe http://ww

Re: [Openocd-development] Connect to MIPS target using DLC5 cable

2008-12-10 Thread Rick Altherr
On Dec 10, 2008, at 7:07 AM, Spencer Oliver wrote: I grabbed the current release from the mips branch and compiled openocd with "./configure --enable-parport --enable-parport_ppdev". Please use svn trunk, the mips branch was for initial testing and is now not maintained. Cheers Spen

Re: [Openocd-development] Connect to MIPS target using DLC5 cable

2008-12-10 Thread Spencer Oliver
> > I grabbed the current release from the mips branch and > compiled openocd with "./configure --enable-parport > --enable-parport_ppdev". > Please use svn trunk, the mips branch was for initial testing and is now not maintained. Cheers Spen ___

[Openocd-development] Connect to MIPS target using DLC5 cable

2008-12-10 Thread Andi
Hi list, I grabbed the current release from the mips branch and compiled openocd with "./configure --enable-parport --enable-parport_ppdev". Openocd successfully determines my jtag device. However, I am still getting a strange error as you can see below. How can I get rid of this error message?