On 06:58 Fri 06 May , Øyvind Harboe wrote:
+# The chip may run @ 32khz, so set a really low JTAG speed
+adapter_khz 8
this is the wrong place it's not board specific but soc specific
tcl/target/at91rm9200.cfg
Perhaps jtag_rclk 8 should be used, i.e. use RCLK if it is supported
On Fri, May 6, 2011 at 10:33 AM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 06:58 Fri 06 May , Ųyvind Harboe wrote:
+# The chip may run @ 32khz, so set a really low JTAG speed
+adapter_khz 8
this is the wrong place it's not board specific but soc specific
/ +# The chip may run @ 32khz, so set a really low JTAG speed
// +adapter_khz 8
// this is the wrong place it's not board specific but soc specific
//
// tcl/target/at91rm9200.cfg
//
// Perhaps jtag_rclk 8 should be used, i.e. use RCLK if it is supported
// and fall back to 8 khz. Of
On Wednesday, May 04, 2011 8:08 PM , Øyvind Harboe wrote:
On Wed, May 4, 2011 at 7:51 PM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 04:17 Wed 04 May , Ųyvind Harboe wrote:
why do you want to set one the adapter is in auto adaptive mode by
default
no need to
Merged.
Thanks!
--
Ø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
___
Best regards
Jonas Hörberg
diff --git a/tcl/board/at91rm9200-ek.cfg b/tcl/board/at91rm9200-ek.cfg
index 07a006b..cf0fb7a 100644
--- a/tcl/board/at91rm9200-ek.cfg
+++ b/tcl/board/at91rm9200-ek.cfg
@@ -18,6 +18,8 @@ $_TARGETNAME configure -event reset-init {
at91rm9200_ek_init }
set
+# The chip may run @ 32khz, so set a really low JTAG speed
+adapter_khz 8
this is the wrong place it's not board specific but soc specific
tcl/target/at91rm9200.cfg
Perhaps jtag_rclk 8 should be used, i.e. use RCLK if it is supported
and fall back to 8 khz. Of course post reset init
On 04:17 Wed 04 May , Øyvind Harboe wrote:
why do you want to set one the adapter is in auto adaptive mode by default
no need to set any speed
OpenOCD doesn't have an auto-adaptive mode, so I guess you need
to explain what you are referring to.
on J-Link
if you set the speed to
On Wed, May 4, 2011 at 7:51 PM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 04:17 Wed 04 May , Ųyvind Harboe wrote:
why do you want to set one the adapter is in auto adaptive mode by default
no need to set any speed
OpenOCD doesn't have an auto-adaptive mode, so I
Please revert this break the rm9200-ek with jlink
where we do have a adapter_khz specified in the init script
Best Regards,
J.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
Please be more specific. We intend to move forward on this one and
we are interested in hearing what problems you are seeing.
This is an important and somewhat tricky problem that we intend
to put to bet once and for all, and knew that there were risks of
regressions before we would get it right.
On 14:26 Tue 03 May , Øyvind Harboe wrote:
Please be more specific. We intend to move forward on this one and
we are interested in hearing what problems you are seeing.
This is an important and somewhat tricky problem that we intend
to put to bet once and for all, and knew that there
The error message is working as intended, near as I can tell.
You have to specify the JTAG communication frequency, there
no longer is any concept of a default frequency.
These scripts are missing a statement to set the JTAG communication
frequency.
Patches gladly accepted!
--
Øyvind Harboe
On 15:52 Tue 03 May , Øyvind Harboe wrote:
The error message is working as intended, near as I can tell.
You have to specify the JTAG communication frequency, there
no longer is any concept of a default frequency.
These scripts are missing a statement to set the JTAG communication
why do you want to set one the adapter is in auto adaptive mode by default
no need to set any speed
OpenOCD doesn't have an auto-adaptive mode, so I guess you need
to explain what you are referring to.
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434
Merged.
Thanks!
--
Ø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
___
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
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
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
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 /
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
On Fri, Apr 29, 2011 at 3:32 PM, Jonas Hoerberg
jhorb...@sauer-danfoss.com 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
Note: completely untested
---
Signed-off-by: Jonas Hörberg jhorb...@sauer-danfoss.com
---
src/jtag/core.c | 15 +++
src/jtag/drivers/amt_jtagaccel.c |6 --
src/jtag/drivers/ft2232.c|6 --
src/jtag/drivers/gw16012.c |5 -
I haven't been able to test, but this does indeed seem
like what we need.
Testing anyone?
Do we want to do away with adapter_speed as user visible command entirely?
The error message should use adapter_khz instead of adapter_speed.
--
Øyvind Harboe
Can Zylin Consulting help on your project?
On Thursday, April 28, 2011 12:38 PM, Øyvind Harboe
[mailto:oyvind.har...@zylin.com] wrote:
I haven't been able to test, but this does indeed seem
like what we need.
Testing anyone?
Do we want to do away with adapter_speed as user visible command entirely?
The error message should
25 matches
Mail list logo
