PIC32MZ1025DAG176
PIC32MZ1025DAH169 PIC32MZ1025DAH176 PIC32MZ1025DAK169 PIC32MZ1025DAK176 PIC32MZ1025DAL169 PIC32MZ1025DAL176 PIC32MZ1025DAR169 PIC32MZ1025DAR176 PIC32MZ1025DAS169 PIC32MZ1025DAS176 PIC32MZ1025W104132 PIC32MZ1064DAA169 PIC32MZ1064DAA176 PIC32MZ1064DAA288 PIC32MZ1064DAB169 PIC32MZ1064DAB176 PIC32MZ1064DAB288 PIC32MZ1064DAG169 PIC32MZ1064DAG176 PIC32MZ1064DAH169 PIC32MZ1064DAH176 PIC32MZ1064DAK169 PIC32MZ1064DAK176 PIC32MZ1064DAL169 PIC32MZ1064DAL176 PIC32MZ1064DAR169 PIC32MZ1064DAR176 PIC32MZ1064DAS169 PIC32MZ1064DAS176 PIC32MZ2025DAA169 PIC32MZ2025DAA176 PIC32MZ2025DAA288 PIC32MZ2025DAB169 PIC32MZ2025DAB176 PIC32MZ2025DAB288 PIC32MZ2025DAG169 PIC32MZ2025DAG176 PIC32MZ2025DAH169 PIC32MZ2025DAH176 PIC32MZ2025DAK169 PIC32MZ2025DAK176 PIC32MZ2025DAL169 PIC32MZ2025DAL176 PIC32MZ2025DAR169 PIC32MZ2025DAR176 PIC32MZ2025DAS169 PIC32MZ2025DAS176 PIC32MZ2048ECG064 PIC32MZ2048ECG100 PIC32MZ2048ECG124 PIC32MZ2048ECG144 PIC32MZ2048ECH064 PIC32MZ2048ECH100 PIC32MZ2048ECH124 PIC32MZ2048ECH144 PIC32MZ2048ECM064 PIC32MZ2048ECM100 PIC32MZ2048ECM124 PIC32MZ2048ECM144 PIC32MZ2048EFG064 PIC32MZ2048EFG100 PIC32MZ2048EFG124 PIC32MZ2048EFG144 PIC32MZ2048EFH064 PIC32MZ2048EFH100 PIC32MZ2048EFH124 PIC32MZ2048EFH144 PIC32MZ2048EFM064 PIC32MZ2048EFM100 PIC32MZ2048EFM124 PIC32MZ2048EFM144 PIC32MZ2051W104132 PIC32MZ2064DAA169 PIC32MZ2064DAA176 PIC32MZ2064DAA288 PIC32MZ2064DAB169 PIC32MZ2064DAB176 PIC32MZ2064DAB288 PIC32MZ2064DAG169 PIC32MZ2064DAG176 PIC32MZ2064DAH169 PIC32MZ2064DAH176 PIC32MZ2064DAK169 PIC32MZ2064DAK176 PIC32MZ2064DAL169 PIC32MZ2064DAL176 PIC32MZ2064DAR169 PIC32MZ2064DAR176 PIC32MZ2064DAS169 PIC32MZ2064DAS176PIC32MZ1025DAG176
Support summary
- Programming - Yes
- Debugging provisions - Yes
ICSP Connection
PIC32MZ1025DAG176 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.
Dual boot architecture
PIC32MZ1025DAG176 has two boot sectors, called boot sector 1 (0x1fc40000) and boot sector 2 (0x1fc60000). These memory locations are not used directly. Instead they are mapped to lower boot alias (0x1fc00000) and upper boot alias (0x1fc20000). Boot sector 1 may be mapped to lower alias while boot sector 2 is mapped to upper boot alias. Or the mapping may be reversed - boot sector 1 is mapped to upper boot alias and boot sector 2 is mapped to lower boot alias. Mapping may change - see datasheet for details.
Because Microchip XC32 compiler produces HEX files where boot sector uses addresses of lower boot alias (0x1fc00000), NSDSP recognizes these addresses as valid. Any memory ranges belonging to lower boot alias (0x1fc00000-0x1fc14000) are programmed to boot sector 1 (0x1fc40000-0x1fc54000). Any addresses from upper boot alias (0x1fc20000-0x1fc34000) are programmed to boot sector 2 (0x1fc60000-0x1fc74000). Direct addressing of boot sectors (0x1fc40000-0x1fc54000 and 0x1fc60000-0x1fc74000) is considered invalid and will cause errors.
When NSDSP is used to read memory, boot sector 1 is reported as lower boot alias (0x1fc00000-0x1fc14000) and boot sector 2 is reported as upper boot alias (0x1fc20000-0x1fc34000) regardless of the actual mapping of the sectors on the chip.
Such arrangement guarantees consistency - if you read a HEX file from the device, then re-program it onto other device, both devices will have identical programming.
Debugging
NSDSP firmware contains all the necessary provisions for debugging PIC32MZ1025DAG176 and may be debugged when debugging software becomes available.
PIC32MZ1025DAG176 uses ordered halting, has 10 hardware breakpoints.
Debugger requires 20 bytes of RAM.
Links
© 2007-2025 Northern Software Inc. All Rights Reserved.