On Mon, Mar 23, 2015 at 11:05:57AM +0300, Paul Fertser wrote:
> On Sun, Mar 22, 2015 at 11:36:53PM +0100, Michael Schwingen wrote:
> > I started working with an LPC812. Using a ST-Link V2 as SWD interface,
> > this seems to work, but I can't get reset working - it seems the reset
> > output is always active, so I decided to pull out my bus blaster.
> 
> Active as in pulled low? Is that with reset_config srst_only or none?
> I think stlinkv2 is known to behave properly in this regard.

yes, low = target continuously in reset. I tried both srst_only and none,
but I did not pull out the 'scope, because it worked with disconnected reset
line.

> > Any hints where to look? Is FT2232+KTLINK or the LPC812 considered stable?
> 
> Both are known to work (with ktlink CPLD bitstream from the URL
> mentioned in the config file), and you're the first to report an
> issue.

The bitstream from the URL in the config file did not work at all (readback
always '1'), so I took the one from the busblaster SVN. Also, I had to use
urjtag - flashing from openocd did not work at all (I can provide traces if
someone is interested, but I wanted to get debugging running first).

BTW: the OpenOCD config files seem to use the wrong device ID - at least my
board has 0x0403/0x8878, although I am not sure if this is standard or not.

cu
Michael

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to