On Saturday 16 January 2010, Andreas F wrote:
> Could somebody tell where to start und where my main focus
> should lie if I want to add a new hardware dongle.
Start with the protocol. Implement the methods needed
to populate a "struct jtag_interface" ... which holds
driver methods, even though
Hi,
I just checked the list of supportet JTAG hardware dongles and found out, that
the Keil ULINK isn't supported.
I would like to start supporting the device and develop the necessery
parts, but after reading a bit through the refernces I got a bit
confused.
Could somebody tell where to
On Saturday 16 January 2010, Freddie Chopin wrote:
> On 2010-01-16 20:59, David Brownell wrote:
> > Oh, and while this is clearly a "bug", from what I've heard it
> > isn't a "regression" from the last release ... "just" a long
> > standing bug.
>
> My bisection (
> https://lists.berlios.de/piper
On 2010-01-16 20:59, David Brownell wrote:
> Oh, and while this is clearly a "bug", from what I've heard it
> isn't a "regression" from the last release ... "just" a long
> standing bug.
My bisection (
https://lists.berlios.de/pipermail/openocd-development/2010-January/014229.html
) shows that t
On Thursday 14 January 2010, richard vegh wrote:
> here it is a patch for
> that crash for file lpc3180.c.
> It contains these corrections:
> -Crash and related functionality
> -some debug message
> -Command handling now works
After minor cleanups, I committed this and now it's in mainline.
So, ca
On Saturday 16 January 2010, Freddie Chopin wrote:
> with STM32 the first
> gdb "load" after power-up of STM32 fails.
Just for reference, the relevant bits of "first.log" seem to be
the appended lines. I have an idea, which I'll look at later;
it revolves around general weakness in fault handlin
On Saturday 16 January 2010, Freddie Chopin wrote:
> I was thinking about providing developement packages (whole tree [exe,
> scripts, dlls, pdf, info, etc.]), but without installer. The main
> problem is that on my webpage I don't have enough:
> 1. bandwith
> 2. quota
> If only OpenOCD could pub
On Saturday 16 January 2010, Alan Carvalho de Assis wrote:
> I'm trying to figure out what DAP is waiting for.
Sorry, cant help there. But surely turning on the debug
output options (there's a separate JTAG I/O option too)
should provide more than enough clues for you. :)
_
On Saturday 16 January 2010, Alan Carvalho de Assis wrote:
> > And I don't see any event code to *enable* the DAP using SJC, so there
> > is no point in requesting that it be enabled. If it's not already
> > present on the scan chain, you'd need to write SJC code to enable it.
> >
>
> Unfortunate
On 2010-01-16 14:03, Freddie Chopin wrote:
> In 0.2.0 (mingw32 compilation, libftdi-0.16) it works fine.
> In 0.3.0-rc0 (mingw32 compilation, libftdi-0.16) it doesn't.
> In 0.3.1 (mingw32 compilation, libftdi-0.16) it doesn't.
> In 0.4.0-rc1-dev (i686-w64-mingw32 crosscompilation, libftdi-0.17) it
On 2010-01-16 16:57, Dean Glazeski wrote:
> Do you have a tutorial online for doing the cross compile process? That
> may be a more viable solution than trying to post development versions
> of the software. I'd at least like to know the steps involved :). If
> it's scriptable, I may put togethe
On Sat, Jan 16, 2010 at 7:30 AM, Freddie Chopin wrote:
> On 2010-01-16 14:14, Thomas Kindler wrote:
> > Could you also provide a recent build for normal Win32?! I tried to
> > compile one myself a few days ago, but failed to get the libftdi stuff
> > working.
>
> I was thinking about providing de
If anyone wishes to try the development versions of OpenOCD, those can
be found on my website www.freddiechopin.info > Download > OpenOCD dev
Currently there are two packages with the most recent version - one for
32-bit systems, the other for 64-bit versions. The package is a zip
archive of co
Hi David,
On 1/15/10, David Brownell wrote:
>> OpenOCD detects all TAPs, but I receive a Timeout:
>>
>> Warn : imx51.SDMA: nonstandard IR value
>> RCLK - adaptive
>> Info : device: 4 "2232C"
>> Info : deviceID: 67353760
>> Info : SerialNumber: 0100480 A
>> Info : Description: Signalyzer A
>> Info
On 2010-01-16 14:14, Thomas Kindler wrote:
> Could you also provide a recent build for normal Win32?! I tried to
> compile one myself a few days ago, but failed to get the libftdi stuff
> working.
I was thinking about providing developement packages (whole tree [exe,
scripts, dlls, pdf, info, et
Hi Freddie!
Freddie Chopin wrote:
> I've got snapshots of 0.4.0-rc1-dev compiled for 64-bit Windows systems,
> but I cannot test that (I use 32-bit Windows). I can produce releases of
> 64-bit versions (just like the "regular" releases on my website), but
> I'd like to test the executable, driv
Hi Paul,
On 1/16/10, Paul Fertser wrote:
...
>
>> In my programmer VSProg, I use a .xml configuration file for all
>> these settings.
>
> Does it work over JTAG? Which JTAG adapters does it support?
>
Do you think it could be possible to implement ICD for AVR8 which
doesn't have a JTAG TAP inter
I've got snapshots of 0.4.0-rc1-dev compiled for 64-bit Windows systems,
but I cannot test that (I use 32-bit Windows). I can produce releases of
64-bit versions (just like the "regular" releases on my website), but
I'd like to test the executable, drivers, and the whole package. If
anyone care
On 2009-12-30 00:10, Johnny Halfmoon wrote:
> after being slapped in the face by the error, try manually entering
> the following:
>
> cd src x86_64-w64-mingw32-gcc -std=gnu99 -g -O2
> -D__USE_MINGW_ANSI_STDIO -I/home/freddie/Pobrane/ftd2xx -Wall
> -Wstrict-prototypes -Wformat-security -Wextra -Wno
Hi,
On Sat, Jan 16, 2010 at 12:13:33PM +0300, Paul Fertser wrote:
> On Sat, Jan 16, 2010 at 04:44:37PM +0800, simon qian wrote:
> > For AVR8 support, there are other problems:
> > 1. chips library
> > Different AVR chips have different parameters, including Flash Page Size,
> > EEPROM Page Size, F
On Saturday 16 January 2010, Paul Fertser wrote:
> > If use .cfg for a AVR8 chip, there will be many such configure
> > files.
>
> I do not see a problem. Moreover if openOCD implements proper avr
> support one can automatically convert configs.
Simon, do the AVR8 chips have proper JTAG IDs, from
On Sat, Jan 16, 2010 at 04:44:37PM +0800, simon qian wrote:
> AVR-OCD-Document is verry old, it doesn't support some new
> devices.
Do you have anything better with JTAG OCD documentation for AVR8?
> For AVR8 support, there are other problems:
> 1. chips library
> Different AVR chips have dif
AVR-OCD-Document is verry old, it doesn't support some new devices.
As I know, Atmel will never open the debugging protocol of their JTAG spec.
You can hack current AVRs for the protocol, but if Atmel releases new chips
which is different from the hacked protocol, it will be an endless work to
23 matches
Mail list logo
