PIC24EP256GU814
PIC24EP256MC202 PIC24EP256MC204 PIC24EP256MC206 PIC24EP32GP202 PIC24EP32GP203 PIC24EP32GP204 PIC24EP32MC202 PIC24EP32MC203 PIC24EP32MC204 PIC24EP512GP202 PIC24EP512GP204 PIC24EP512GP206 PIC24EP512GP806 PIC24EP512GU810 PIC24EP512GU814 PIC24EP512MC202 PIC24EP512MC204 PIC24EP512MC206 PIC24EP64GP202 PIC24EP64GP203 PIC24EP64GP204 PIC24EP64GP206 PIC24EP64MC202 PIC24EP64MC203 PIC24EP64MC204 PIC24EP64MC206PIC24EP256GU814
Support summary
ICSP Connection
PIC24EP256GU814 has more than one pair of PGECx and PGEDx pins. You can use any pair, but you must use them as a pair. For example, if PGEC2 is used for ICSPCLK, then ICSPDAT must be connected to PGED2.
All VSS and VDD pins must be connected. Even if one of these pins is not connected, programming may fail.
PIC24EP256GU814 is more sensitive to cross-talk between PGEC and PGED lines than other PIC devices. This may lead to programming failures, such as inability to connect or various verification failures. One of the methods to improve connectivity is to connect a small 20pF capacitor between PGEC line and VSS as close to the chip as possible. A bigger capacitor may be used, however you will have to decrease ICSP communication speed.
Programming Benchmarks for NSDSP-1 and NSDSP-2
We have measured time necessary to program and verify PIC24EP256GU814 with NSDSP-1 or NSDSP-2 (both yeild the same speed).
Operation | FCKSM=0x | FCKSM=1x | Programming and Verification | 6.0s | 7.8s | Programming only | 5.9s | 6.0s | Verification only | 4.8s | 4.8s |
---|
The measurements reflect the time necessary to program/verify the entire chip, including all user programmable memory areas.
Debugging
NSDSP firmware contains all the necessary provisions for debugging PIC24EP256GU814 and may be debugged when debugging software becomes available.
PIC24EP256GU814 uses unordered halting, has 8 hardware breakpoints.
Debugging does not consume resources in the user space.
Links
© 2007-2025 Northern Software Inc. All Rights Reserved.