Hot!ICD4 Invalid combinations of config bits

Author
mosca
New Member
  • Total Posts : 8
  • Reward points : 0
  • Status: offline
2018/03/14 05:03:57 (permalink)
0

ICD4 Invalid combinations of config bits

Hello,
I want to use the ICD4 instead of ICD3 in an existing project with a PIC32MX575F512L.
The debugging of this project with ICD3 works without problems.

With ICD4, after start with the "Debug Project" icon, I got the following error in the ICD4 window:
###############################
Connecting to MPLAB ICD 4...
Currently loaded versions:
Application version............01.02.16
Boot version...................01.00.00
FPGA version...................01.00.00
Script version.................00.02.23
Script build number............45a591cbc0
Application build number.......0123456789
Target voltage detected
Target device PIC32MX575F512L found.
Device Id Revision = 0xA5
Erasing...
The following memory area(s) will be programmed:
program memory: start address = 0x1d008000, end address = 0x1d0087ff
program memory: start address = 0x1d009000, end address = 0x1d064fff
configuration memory
boot config memory
Script WriteDebugVector failed with status Type = runScript, Script name = WriteDebugVector, Status = 0x102
.
Could not enter debug mode because programming the debug information failed. Invalid combinations of config bits may cause this problem
###############################
Which config bits have to change ?
Is it possible to debug the project with the same settings with ICD3 and ICD4 ?
#1

7 Replies Related Threads

    mosca
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Status: offline
    Re: ICD4 Invalid combinations of config bits 2018/03/14 05:11:47 (permalink)
    0
    additional Info:  using MPLAB-X v4.15
    #2
    Jim Nickerson
    User 452
    • Total Posts : 5444
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: online
    Re: ICD4 Invalid combinations of config bits 2018/03/14 06:19:31 (permalink)
    0
    maybe use IPE to erase chip
    remove all breakpoints
    set MplabX to stop at main when starting
    Single step from there
    #3
    mosca
    New Member
    • Total Posts : 8
    • Reward points : 0
    • Status: offline
    Re: ICD4 Invalid combinations of config bits 2018/03/14 06:32:27 (permalink)
    0
    Hello Jim,
    I tried your proposals:
    - erased chip with IPE v4.15
    - removed all breakpoints
    - set MplabX to stop at main when starting
    - normal build runs without errors
    - try to debug project: again the same error message in ICD4 window:
    Script WriteDebugVector failed with status Type = runScript, Script name = WriteDebugVector, Status = 0x102
    Could not enter debug mode because programming the debug information failed. Invalid combinations of config bits may cause this problem

    I tried also "halt at reset vector", but same problem.
    #4
    Jim Nickerson
    User 452
    • Total Posts : 5444
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: online
    Re: ICD4 Invalid combinations of config bits 2018/03/14 06:34:20 (permalink)
    0
    Maybe this chip is not fully supported yet
    #5
    Jim Nickerson
    User 452
    • Total Posts : 5444
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: online
    Re: ICD4 Invalid combinations of config bits 2018/03/14 06:35:59 (permalink)
    0
    Or maybe it does not like your config bits.
    Maybe you could try with the defaults
     
    #6
    sherwood
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2017/03/23 13:01:04
    • Location: 0
    • Status: offline
    Re: ICD4 Invalid combinations of config bits 2018/04/12 13:19:47 (permalink)
    0
    I"m having the same issue. picKit3 works fine with no changes (other than plugging in the picKit3,) which is a bummer.
    #7
    RISC
    Super Member
    • Total Posts : 5301
    • Reward points : 0
    • Status: offline
    Re: ICD4 Invalid combinations of config bits 2018/04/12 16:06:32 (permalink)
    4 (1)
    Hi,
     
    If you have Pickit4 issues, report them to the mail addresse shown on this page : http://microchip.com/pickit4
    ====================================================================
    The MPLAB PICkit 4 In-Circuit Debugger/Programmer supports many, but not all, PIC MCUs and dsPIC DSCs at this time. The firmware is continually being upgraded to add support for new devices. To request priority device support or to report issues, email: PICkit4_Update@microchip.com
    To check supported devices: If you have MPLAB X IDE installed, you can browse to the “docs” folder under your MPLAB X installation directory and open the file “Device Support.htm”. Alternatively, you can download it from this link: http://www.microchip.com/mplabx-ide-release-notes
    ====================================================================
     
    If you have ICD4 issues, report them to the mail addresse shown on this page :   http://www.microchip.com/icd4
    ====================================================================
    The MPLAB ICD 4 In-Circuit Debugger/Programmer supports many, but not all, PIC MCUs and dsPIC DSCs at this time. The firmware is continually being upgraded to add support for new devices. To request priority device support or to report issues, email: ICD4_update@microchip.com
    If you have MPLAB X installed, you can browse to the “docs” folder under your MPLABX installation directory and open the file “Device Support.htm”. Alternatively, you can download it from this link: http://www.microchip.com/mplabx-ide-release-notes
    ====================================================================
     
    #8
    Jump to:
    © 2018 APG vNext Commercial Version 4.5