On Fri, Jul 31, 2009 at 8:29 PM, Xiaofan Chen wrote:
> On Fri, Jul 31, 2009 at 8:24 PM, Xiaofan Chen wrote:
>> V0.2.0 release works with the on-board ftdi interface. But it still has the
>> same problem with J-Link. Firstly I have to reduce jtag_khz to around
>> 1000. Secondly it still does not wor
On Sat, Aug 1, 2009 at 11:00 PM, Qiang Wang wrote:
> But if we can make it as fast as them ,open ocd will be more popular .
Software is one thing. But the underline hardware debugger
needs to be fast as well. For example, I believe those
two ICE you used will have high speed USB interface,
fast FP
But if we can make it as fast as them ,open ocd will be more popular .
2009/8/1 Xiaofan Chen :
> On Sat, Aug 1, 2009 at 7:02 PM, Qiang Wang wrote:
>>> I know what is RDI. But what is the JTAG debugger hardware you
>>> are using? And what is the host software you are using?
>>
>> RealView 3.1 + I
On Sat, Aug 1, 2009 at 7:02 PM, Qiang Wang wrote:
>> I know what is RDI. But what is the JTAG debugger hardware you
>> are using? And what is the host software you are using?
>
> RealView 3.1 + ICE(Got From ARM)
This RealView ICE? Pretty high end stuff. You probably
can not compare it to the cheap
Qiang Wang wrote:
> hello, all
> sorry, I repeat the message again because nobody answer it.
> I test the JTAG interface with Logic Analyze Device, today .
> I found some fact as below.
>
> 1. the jtag_khz will affect the TCK of JTAG.
> When 6000, It will be 6MHz of the TCK, when 3000, the TCK wil
Hi Stefano,
I think, I have the same problem...
I have a MMnet1001 module from Propox. This module has a AT91SAM9260
chip. This chip has an ARM926EJ-S Processor.
I am using the Amontec Chameleon dongle, loaded with the JTAG
Accelerator configuration. (RTCK-feature enabled)
When commanding the
> I know what is RDI. But what is the JTAG debugger hardware you
> are using? And what is the host software you are using?
RealView 3.1 + ICE(Got From ARM)
We also use the Yokogawa ICE from a Japan Maker.
We got the same speed with the two ICE.
best regards
wangqiang
___
On Sat, Aug 1, 2009 at 6:12 PM, Qiang Wang wrote:
> hello Xiaofan
>>That is pretty fast. What is the target? What is the test condition?
> I use the ARM 926ej-s , 300MHz. JTAG 20pins
>
>> Sorry but what is RDI ICE debugger?
> RDI is the "Remote Debug Interface" which is defined by ARM Inc.
> You ca
hello Xiaofan
>That is pretty fast. What is the target? What is the test condition?
I use the ARM 926ej-s , 300MHz. JTAG 20pins
> Sorry but what is RDI ICE debugger?
RDI is the "Remote Debug Interface" which is defined by ARM Inc.
You can refer the ARM doc.
http://infocenter.arm.com/help/index.jsp
On Sat, Aug 1, 2009 at 3:34 PM, Qiang Wang wrote:
> hello,
> I report the speed I have test.
> Transfer rate: 68KB/sec with open-ocd + gdb.
> I download 1096208 bytes which consume 160seconds.
That is pretty fast. What is the target? What is the test condition?
> To compare, I list the the RD
hello, all
sorry, I repeat the message again because nobody answer it.
I test the JTAG interface with Logic Analyze Device, today .
I found some fact as below.
1. the jtag_khz will affect the TCK of JTAG.
When 6000, It will be 6MHz of the TCK, when 3000, the TCK will be 3MHz.
But if I change the j
hello,
I report the speed I have test.
Transfer rate: 68KB/sec with open-ocd + gdb.
I download 1096208 bytes which consume 160seconds.
To compare, I list the the RDI ICE debugger speed.
I download the 11MB file with only 17 seconds, means transfer rate 647KB/sec.
I test the data with the s
Ananda Regmi pisze:
> Based on the manual should the flash bank command contain lpc2000_v1
> instead of lpc2000_v2?
?
LPC2103 is specifically listed as _v2...
lpc2000_v2 (LPC213x, LPC214x, *LPC210[123]*, LPC23xx and LPC24xx)
Moreover - this file works fine.
4\/3!!
___
13 matches
Mail list logo
