On Fri, Apr 29, 2011 at 3:32 PM, Jonas Hoerberg
wrote:
>
> On Friday, April 29, 2011 3:03 PM, Øyvind Harboe
> [mailto:oyvind.har...@zylin.com] wrote:
>>
>> So is this something that should be fixed or is this an
>> inherent limitation of the parport driver?
>>
>> The parport drivers main purpose,
On Friday, April 29, 2011 3:03 PM, Øyvind Harboe
[mailto:oyvind.har...@zylin.com] wrote:
>
> So is this something that should be fixed or is this an
> inherent limitation of the parport driver?
>
> The parport drivers main purpose, IMHO, is to act as reference
> code for the bitbang driver.
I
So is this something that should be fixed or is this an
inherent limitation of the parport driver?
The parport drivers main purpose, IMHO, is to act as reference
code for the bitbang driver.
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International
Test results:
JTAGkey-Tiny (FT2232D): Works
JTAGkey2 (FT2232H): Works
Parport (Wiggler clone):
Works as long as any calls to "parport_toggling_time" is done after the speed
is set.
It cannot be called before because the
"parport_handle_parport_toggling_time_command" function calls "jtag_get_speed
Test results using dummy interface.
a) Failure as expected without settings speed:
openocd -c "interface dummy"
Open On-Chip Debugger 0.5.0-dev-00867-g9ae4ddd (2011-04-29-12:45)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only o
Any objections?
I'd rather like to hear some testing feedback on this one!
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer