Re: [Openocd-development] another STM32 problems with RLink

2009-03-06 Thread Rob Brown
lou.openocd...@fixit.nospammail.net wrote: > On Fri, Mar 06, 2009 at 12:36:52PM +0100, freddie_cho...@op.pl wrote: >> I'm using openocd-0.1.0 for Windows >> >> I got the STM32F10X-128k-EVAL board with the original RLink. I can debug the >> primer1, which has the Rlink embedded. I connect to the cu

Re: [Openocd-development] another STM32 problems with RLink

2009-03-06 Thread lou . openocd012
On Fri, Mar 06, 2009 at 12:36:52PM +0100, freddie_cho...@op.pl wrote: > I'm using openocd-0.1.0 for Windows > > I got the STM32F10X-128k-EVAL board with the original RLink. I can debug the > primer1, which has the Rlink embedded. I connect to the current board with > the same command > > openoc

Re: [Openocd-development] BeagleBoard - OMAP - & DRSCAN and IRSCAN issues

2009-03-06 Thread Kees Jongenburger
Thanks Duane, I will test your patch this week-end. Thanks for the input Greetings On Fri, Mar 6, 2009 at 6:01 PM, Duane Ellis wrote: > Dirk/Kees, > > On (3/2) I posted a patch that I believe adds the required functionality > to openocd = specifically it adds an "endstate" option to the IRSCAN

[Openocd-development] BeagleBoard - OMAP - & DRSCAN and IRSCAN issues

2009-03-06 Thread Duane Ellis
Dirk/Kees, On (3/2) I posted a patch that I believe adds the required functionality to openocd = specifically it adds an "endstate" option to the IRSCAN and DRSCAN commands. Specifically to address this comment by Dirk: Dirk Behme> In [1] Rick proposed Dirk Behme> "... that the C function for

Re: [Openocd-development] Reset, Halt, and Init Problems with AT91SAM9G20

2009-03-06 Thread Duane Ellis
Pieter Conradie wrote: > Hi Rob, > > I have found that if the jtag_khz setting is decreased to 1 kHz, then OpenOCD > behaves better, but it is still not 100%. > > I have connected a signal analyser to capture the JTAG signals between > OpenOCD rev 1399 and an AT91SAM9260 target using a Olimex JTA

Re: [Openocd-development] another STM32 problems with RLink

2009-03-06 Thread Spencer Oliver
> > timed out while waiting for target halted Runtime error, file > "command.c", line 456: > > The board and the rlink are ok, because they were used with > succes a few hours ago (in ride7). I will check that anyway > in a moment. > > any ideas what can I do? the debug messages give nothing

Re: [Openocd-development] Naming convention of *.cfg files

2009-03-06 Thread Duane Ellis
Pieter Conradie wrote: > Hi all, > > I have updated the config file naming convention according to all the > suggestions. Is this better? > Yes, thank you for your work. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https

Re: [Openocd-development] another STM32 problems with RLink

2009-03-06 Thread freddie_chopin
I've tried with another RLink (that one is completely new) and it's the same. I've also tried the primer again and it works completely fine with exactly the same setup 4\/3!! ___ Openocd-development mailing list Openocd-development@lists.berlios.de htt

[Openocd-development] another STM32 problems with RLink

2009-03-06 Thread freddie_chopin
I'm using openocd-0.1.0 for Windows I got the STM32F10X-128k-EVAL board with the original RLink. I can debug the primer1, which has the Rlink embedded. I connect to the current board with the same command openocd -f interface/rlink.cfg -f board/stm32f10x_128k_eval.cfg I can connect with no pro

Re: [Openocd-development] Naming convention of *.cfg files

2009-03-06 Thread Michael Schwingen
Pieter Conradie wrote: > Hi all, > > I have updated the config file naming convention according to all the > suggestions. Is this better? > Looks good to me. cu Michael ___ Openocd-development mailing list Openocd-development@lists.berlios.de https: