|
|
View previous topic :: View next topic |
Author |
Message |
KamPutty Guest
|
What am I missing?! ICD-U40 |
Posted: Mon Jan 16, 2006 4:34 pm |
|
|
Hi all,
I've been using Microchips ICD-2 for some time now, in the MPLAB IDE. I've finally head enough with the DEBUGGING speed and was told to try the CCS ICD-U40 as it's faster...
So here is my normal dev cycle
#1. Write
#2. Burn
#3. Test
#4. Repeat till done!
I spend more time burning then debugging. In MPLAB, I can compile using CCS's compiler, and then upon success, burn the chip and release to test
Now, I can do the same with the ICD-U40, but using the CCS's IDE. Now, this very fast process (3~4 seconds in MPLAB) takes about 30!!!
Is there ANYTHING I can do to speed this process up? Is there a command line switch for "Compile this badboy, and when ok, burn it all, then release it etc"?
I saw in the Help File, "Icd -T *.hex" file, and when I tried that it just starts the ICD program.
Any thoughts?
~Kam (^8* |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Mon Jan 16, 2006 5:22 pm |
|
|
It could be that the ICD2 is configured to program only the bytes
in the PIC that need programming, but the CCS ICD is configured
to program the entire PIC. This could account for the time difference.
I suggest checking the ICD options menu. |
|
|
KamPutty Guest
|
times... |
Posted: Mon Jan 16, 2006 8:22 pm |
|
|
Okay,
I ran the ICD program and just did a "program". It took 17 seconds with ICD-U40 and 4 seconds in MPLAB with ICD-2.
Any thoughts?
They are using the same connector (ICD). Is there something special with the CCS ICD connector vs. the ICD-2? They look the same...
<delay>
The only diff is that the CCS ICD needs a 49k(?) resister for pin1 and ICD-2 does not(?)....
But nothings complaining...
That extra 13 seconds is killing me!
~Kam (^8* |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Mon Jan 16, 2006 10:08 pm |
|
|
Did you read my post ?
Did you look at the Advanced menu in the ICD program ?
Did you read the ICD help file ?
From the help file:
Quote: |
Advanced Screen
Program Modes
This specifies the programming mode that ICD uses for programming the
target chip. The ICD software validates the programming and erase
modes when the user changes them and on start-up.
Fast- The fast mode only works on 5V targets. It provides the
fastest way of programming the chip. This uses the program only
algorithm of the chip, it does not erase before programming. The erase
mode should be set to bulk or erase when needed to use this mode.
Normal- This is the default mode since it will work on both 5V and
3V targets. It can be quite slower than fast mode depending on the
target type. It is normal for the progress bar to stop at a percentage
for a few seconds before continuing. It is better to use Fast Mode for 5V
targets for speed reasons. This mode erases as it programs. The Normal
Mode can function with any of the erase modes. |
|
|
|
KamPutty Guest
|
Sad me... |
Posted: Tue Jan 17, 2006 1:10 am |
|
|
Sad to say, but yes, I did read the help, and did try the +5v, and those where the times based on the fastest mode.
#1. From the ICD menu, selecting a file from "Download Target" takes 3 seconds before the "Write Data" dialog opens
#2. The "Write Data" dialog box take 10 seconds to process
#3. The "Verify" takes 5 seconds to process
All said, it takes approx 18 seconds to burn!
~Kam (^8* |
|
|
KamPutty Guest
|
Re: Sad me... |
Posted: Tue Jan 17, 2006 10:28 am |
|
|
KamPutty wrote: | Sad to say, but yes, I did read the help, and did try the +5v, and those where the times based on the fastest mode.
#1. From the ICD menu, selecting a file from "Download Target" takes 3 seconds before the "Write Data" dialog opens
#2. The "Write Data" dialog box take 10 seconds to process
#3. The "Verify" takes 5 seconds to process
All said, it takes approx 18 seconds to burn!
|
Well, I spoke with CCS Tech Support (Yeh!), and we tried a few things, and it seems that the "#fill rom" pragma was causing the issue. Not really an issue since it programmed the whole ROM regardless of how large my program is. Commenting it out sped the whole process.
The whole cycle now take approx 10 seconds, where 4 seconds is just connecting to the ICD (before the "Download target" dialog apprears). the actual buring takes about 2 seconds, and the verify takes another 2 seconds. Can I turn off the verify?
~Kam (^8* |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|