Lpc2000

Here is my opinion using other MCUs (MPC565, PIC16F, PIC18F) and i think 
for LPC the situation is the same regarding programming speeds. There 
are two different speeds, one is speed of internal flash module and 
other is speed of communication PC to Target MCU. Normally when flash 
erase is started speed of erase depends mostly on the speed of flash 
module and not on the speed of interface.
But programming of RAM mostly depends on speed of interface since RAM 
modules are much, much faster than flash modules.
It is good if both of you can test your interfaces on same target MCU 
but with biggest elf file that can be fitted inside flash and/or ram of 
target mcu. This way tests will be performed on same mcu and difference 
will be only on speed of interface and a bit on speed of used PC. This 
way we'll see it JTAGjet really has "jet" spped compared to CrossConnect.
Regards,
Blagoj


Na 28.09.2005 17:21 Paul Curtis rece:

>Chris, 
>
>  
>
>>I guess you missed the point.
>>    
>>
>
>Well, let's work through it shall we.
>
>  
>
>>The programming time is 
>>limited by the internal operation of the LPC CPU.
>>    
>>
>
>Sure.  I understand that.
>
>  
>
>>Erasing sectors is time controlled by the CPU.  The jtag link has 
>>nothing to do with this.  Those time delays are the same for 
>>any programmer.  Just try doing some IAP yourself from your 
>>own internal code and you will understand real quick.  You 
>>can't do it any faster even from inside the CPU.
>>    
>>
>
>I'm sorry if I'm a little thick here.  You'll need to help me with the
>mathematics.
>
>Here's a little dump of what CrossWorks does when downloading using a
>CrossConnect:
>
>Downloading Loader to USB CrossConnect for ARM
>Programming 3.6 KB at 0x40000000
>Programming completed in 141 ms -- 26,808 bytes/sec
>Downloading keil_mcb2140.elf to USB CrossConnect for ARM
>Erasing completed in 2.1 s -- 23,499 bytes/sec
>Programming 47.4 KB at 0x0
>Programming completed in 1.5 s -- 32,575 bytes/sec
>Verifying keil_mcb2140.elf on USB CrossConnect for ARM
>Verifying completed in 375 ms -- 130,216 bytes/sec
>
>I downloaded 3.6K to RAM in 141ms, then I erased the LPC2k's flash in
>2.1s, then I downloaded 47.5K to flash in 1.5s, and then I verified that
>it had downloaded correctly in 375ms.
>
>Total time from cold to debugging = 4.1s.
>
>With a wiggler:
>
>Downloading Loader to Macraigor Wiggler (20 Pin)
>Programming 3.6 KB  at 0x40000000
>Programming completed in 312 ms --12,320 bytes/sec
>Downloading keil_mcb2140.elf to Macraigor Wiggler (20 Pin)
>Erasing completed in 2.0 s -- 24,078 bytes/sec
>Programming 47.4 KB at 0x0
>Programming completed in 2.9 s -- 16,859 bytes/sec
>Verifying keil_mcb2140.elf on Macraigor Wiggler (20 Pin)
>Verifying completed in 390 ms --126,317 bytes/sec
>
>So, I downloaded 3.6K to RAM in 312ms, then I erased the LPC2k's flash
>in 2.0s, then I downloaded 47.5K to flash in 2.9s, and then I verified
>that it had downloaded correctly in 390ms.
>
>Total time from cold to debugging = 5.6s.
>
>You said:
>
>"The download to the Flash/RAM only takes a couple seconds or less. But
>the programming of the flash takes about 6 seconds.  That is due to the
>internal speed..."
>
>Yes, so eight seconds for 48K to download and program.  That compares to
>5.6s to download and program on the wiggler and 4.1s on the
>CrossConnect.
>
>So, where am I making my mistake, and why is the JTAGjet so much better?
>
>-- Paul.
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>__________ NOD32 1.1236 (20050928) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.eset.com
>
>
>
>  
>