Re: [Openocd-development] ST-Link

2011-01-08 Thread vinit agrawal
no responses . :| On Sat, Jan 8, 2011 at 1:51 PM, vinit agrawal wrote: > Hi guys, > > I have got this STM32 Discovery Kit, which is really lost cost dev platform > for stm32 line of MCUs and it also include an onboard > JTAG-Programmer/debugger based on ST's own Protocol called ST-Link. I a

Re: [Openocd-development] mips coprocessor instruction

2011-01-08 Thread loody
hi all: 2011/1/8 loody : > Hi all: > I remember there is an instruction called COP which can used for > taking look at coprocessor registers. > But I cannot find out the usage. > From the help message, if I want to take a look at coprocessor 13 > select 0, it should use "cop cp 13 0", > but I alwa

Re: [Openocd-development] [PATCH] lpc21xx: common target script

2011-01-08 Thread Freddie Chopin
Hi! Here's another path which improves the idea. I've come with a problem, that has two solutions. When a board (or whatever) configures some event handlers (like "reset init") this is usually done like this: $_TARGETNAME configure -event reset-init { ... } But now, _TARGETNAME is

[Openocd-development] mips coprocessor instruction

2011-01-08 Thread loody
Hi all: I remember there is an instruction called COP which can used for taking look at coprocessor registers. But I cannot find out the usage. >From the help message, if I want to take a look at coprocessor 13 select 0, it should use "cop cp 13 0", but I always get error message as below: > help

[Openocd-development] ST-Link

2011-01-08 Thread vinit agrawal
Hi guys, I have got this STM32 Discovery Kit, which is really lost cost dev platform for stm32 line of MCUs and it also include an onboard JTAG-Programmer/debugger based on ST's own Protocol called ST-Link. I am sure most of you are already aware of that. to be able to program this board from lin