Merged.
Thanks!
I've tested with --enable-dummy driver, this does not check that
your code builds without warnings or errors, but that it does not
break other driver builds in any obvious way. Good 'nuf for now.
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-98
Before we can accept this patch, it must not break other
drivers or build configurations.
If there is a dependency on libdti (???) then the config files
must only check for it's presence if those other dependencies
are required.
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US t
Hi,
it doesn't seem to build:
./configure --enable-dummy --enable-maintainer-mode
hecking whether standard drivers can be built... yes
checking usb.h usability... no
checking usb.h presence... no
checking for usb.h... no
configure: error: usb.h is required to build some OpenOCD driver(s)
--
Ø
On Thursday 23 June 2011 00:41:29, Drasko DRASKOVIC wrote:
> Wow! Great work, Martin.
>
> BR,
> Drasko
Thanks for taking a look at it!
Best regards,
Martin
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.
Wow! Great work, Martin.
BR,
Drasko
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Tuesday 21 June 2011 19:11:17 Christopher Harvey wrote:
>
> Hi Martin,
> I've got a ulink at home with an MCB board (I forgot the exact number),
> so this is exciting news for me.
>
> I've been wanting to lean the internals of OCD and Jtag for a while,
> could anybody suggest some technic
On Tue, 21 Jun 2011 18:34:16 +0200, Martin Schmölzer
wrote:
Hi,
my ULINK driver for OpenOCD is finally in a usable state. Attached is
a patch
set that adds this driver + the custom firmware for the ULINK
adapter.
Currently, this is only tested with an Olimex STM32-P103 development
board
(ST
