On Sunday 01 November 2009, Freddie Chopin wrote:
> David Brownell pisze:
> > With "this" being the warning about "-irmask 1" ... since
> > you have that particular hardware, you can test to see if
> > the config files even need to include those two optional
> > parameters for those TAPs.
>
> I th
David Brownell pisze:
With "this" being the warning about "-irmask 1" ... since
you have that particular hardware, you can test to see if
the config files even need to include those two optional
parameters for those TAPs.
I thought it was more complicated than "trial & error" <: If the results
On Saturday 31 October 2009, Freddie Chopin wrote:
> David Brownell pisze:
> > Looks like you can fix this for the LPC2103 and STM32
> > chips...
>
> How?
With "this" being the warning about "-irmask 1" ... since
you have that particular hardware, you can test to see if
the config files even need
On Thursday 29 October 2009, Freddie Chopin wrote:
> 5. Some time ago there was some talk about adding the
> libusb-win32/libftdi driver file with some info to the repository. What
> about it? libusb-win32/libftdi use is still complicated (nothing
> changed) and the forums are full of questions
On Saturday 31 October 2009, Freddie Chopin wrote:
>
> > But unless some other maintainer is happier with
> > merging untested stuff, I'll ask you to trim
> > this down to just the stuff you tested, plus
> > LPC and CFI changes.
>
> Sorry, working with your newest idea - git - is way over my pati
David Brownell pisze:
> Hmmm ... we're at RC0, which means I've now got my
> "avoid merging patches" hat. Tested patches are by
> and large OK when they fix bugs, and getting rid of
> these warnings passes my "ok to merge" filter.
>
> And in this case think it's clear the other LPC
> files have t
David Brownell pisze:
> Looks like you can fix this for the LPC2103 and STM32
> chips...
How?
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Thursday 29 October 2009, Freddie Chopin wrote:
> 1. When using lpc2103.cfg or stm32.cfg (probably many other target
> scripts) when started OpenOCD warns:
>
> > Warn : use 'lpc2103.cpu' as target identifier, not '0'
>
> which is because lines like:
>
> > flash bank stm32x 0 0 0 0 0
>
> wh
On Thursday 29 October 2009, Freddie Chopin wrote:
> 2. When using stm32.cfg OpenOCD says (beside the above):
>
> > Warn : stm32.bs: nonstandard IR mask
>
> which is because of
>
> > jtag newtap $_CHIPNAME bs -irlen 5 -ircapture 0x1 -irmask 0x1
> > -expected-id $_BSTAPID1 -expected-id $_BSTA
OpenOCD 0.3.0-rc0 compiled on mingw with ftd2xx.dll
1. When using lpc2103.cfg or stm32.cfg (probably many other target
scripts) when started OpenOCD warns:
> Warn : use 'lpc2103.cpu' as target identifier, not '0'
which is because lines like:
> flash bank stm32x 0 0 0 0 0
which should be
> fl
10 matches
Mail list logo
