Lpc2000

John Heenan wrote:

>The Signum JTAGjet claims download speed in excess of 1 MByte/sec, 
>not 1Mbit/sec. From the Signum web site 
>http://www.signum.com/Signum.htm 
>"Actual speed 1.062 Mbyte/sec tested with ARM Evaluator 7T board and 
>600 MHz Pentium III PC with USB 2.0 port. Faster PCs may yield faster 
>downloads."
>
>Since the JTAGjet uses USB 2.0 this is reasonable, provivded the 
>target device and connections can hold up.
>
>Leaving aside the issue of delays introduced by programming Flash, 
>which many developers do not need to bother with during development 
>if all their code fits into RAM, the claimed speed supports what many 
>developers welcome and which was mentioned by Chris: rapid reading of 
>data blocks at breakpoints.
>
>The Signum JTAGjet also claims compatibility with all major ARM 
>debuggers and another version of the JTAGjet supports ETM.
>  
>
What's a major debugger?

>I am simply pointing out factual issues. This is what I welcome from 
>a newsgroup, along with a balance of relevance and fair 
>represenstation. 
>  
>
The LPC22xx could be used to run programs from an external SRAM - this 
is an approach that can be used to avoid the two breakpoints limitation. 
It would be useful for someone who has this hardware combination (Signum 
JTAGjet and LPC22xx+SRAM) to provide download (and upload) figures.

Michael

>John Heenan
>
>
>--- In lpc2000@yahoogroups.com, "Paul Curtis" <plc@r...> wrote:
>  
>
>>Chris, 
>>
>>    
>>
>>>When I said 5 or 6 seconds, I was not trying to be that 
>>>precise.  These were not measurements taken with any stop 
>>>watch or by any elaborate timing method.  That was just my 
>>>feeling.  It could be anywhere from 3-7 seconds as far as I 
>>>now.  I don't pay that close attention to it.  I'm always 
>>>erasing different amounts of memory.  Sometimes it is all 
>>>256K, and other times it is just 32K.  It depends.  So I get 
>>>different times.
>>>
>>>But programming is not what my point was about, as far as 
>>>being JTAG speed.  Reading back the data for large blocks 
>>>during debugging is where the speed comes in.  Stopping and 
>>>starting breakpoints is when the data has to be pulled back 
>>>through the JTAG.  That is a lot faster at 1M than at 14K.  
>>>All of my half dozen windows fill quick.
>>>      
>>>
>>You just don't seem to understand.  14K is the flashing rate in 
>>    
>>
>bytes
>  
>
>>per second and has nothing to do with your "1M rate" which is bits 
>>    
>>
>per
>  
>
>>second on TDI/TDO and clocking the JTAG state machine  If I told you
>>that the CrossConnect actually runs a 4MHz clock on TCK that's 
>>    
>>
>faster
>  
>
>>than your 1M rate isn't it?
>>
>>You're comparing apples with oranges.  Until you can understand 
>>    
>>
>that we
>  
>
>>can write data into RAM at 200Kbytes/second (that equates to
>>1.6Mbit/second), you're just not going to grasp that these pieces of
>>hardware are comparible and, as far as I can tell form what you've 
>>    
>>
>said,
>  
>
>>the CrossConnect is faster.
>>
>>-- Paul.
>>    
>>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>