• AVR Freaks

Hot!MPLAB X IDE v5.30 with ICD-3 on WIN-7

Author
john.dammeyer
Super Member
  • Total Posts : 423
  • Reward points : 0
  • Joined: 2004/01/02 20:07:06
  • Status: offline
2019/11/06 17:46:11 (permalink)
0

MPLAB X IDE v5.30 with ICD-3 on WIN-7

I've put in an order for an ICD-4 because for some reason v5.30 doesn't seem to recognize my ICD-3. 
 
I can take it to a WIN-7 laptop running v5.15 and under project options that same ICD-3 shows up along with its serial number.  I even have the option to give it a friendly name.  It doesn't seem to work on my workstation with v5.30.  And using the same usb port and cable was working with MPLAB-8. 
 
The Driver Switcher did change it from MPLAB-8 to MPLAB-X because otherwise it wouldn't work on the laptop with v5.15.
 
So please confirm that v5.30 has discontinued support for the ICD-3.  And if not, what process is required to bring it back so it works?
#1

11 Replies Related Threads

    JPortici
    Super Member
    • Total Posts : 852
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/06 23:59:24 (permalink)
    0
    remind me in a few hours
    #2
    JPortici
    Super Member
    • Total Posts : 852
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/07 01:10:05 (permalink)
    +1 (1)
    working fine here.
    win 7 Pro 64bit
    #3
    john.dammeyer
    Super Member
    • Total Posts : 423
    • Reward points : 0
    • Joined: 2004/01/02 20:07:06
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/07 11:40:06 (permalink)
    0
    So no idea how to make it work when it doesn't?  Shows up in Device Manager.  Just doesn't under MPLAB-X.  I'm headed out to try it with a WIN-10 system at the clients site.  Since the ICD-3 support is discontinued the client will also end up buying an ICD-4.
    Still overall prefer MPLAB 8.  It just always works.  Never an issue.  Honestly if I had to start from scratch and pick an processor for an embedded system I'm not sure I'd choose a Microchip part simply because of MPLAB-X.
    #4
    KTrenholm
    Super Member
    • Total Posts : 746
    • Reward points : 0
    • Joined: 2012/08/08 14:04:23
    • Location: Connecticut, USA
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/07 11:55:35 (permalink)
    0
    Have you tried using 5.15 on the machine where it is not working on 5.30?
    You can install more than one version of MPLAB X on one machine, they'll each have their own environment, so it's pretty easy to test this sort of thing.
     
    If it doesn't work on either version on the same machine, it's almost certainly a problem with the configuration of that specific PC.
    ICD3 support should not be going anywhere for a while, and certainly hasn't been discontinued in 5.30.
    post edited by KTrenholm - 2019/11/07 11:59:38
    #5
    john.dammeyer
    Super Member
    • Total Posts : 423
    • Reward points : 0
    • Joined: 2004/01/02 20:07:06
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/13 14:34:35 (permalink)
    0
    Success with the ICD-3.  Of course on the same day that the ICD-4 arrived.  Anyway I've run into a new problem.
    The ICD-3 (and 4 too) is updated with the correct firmware and finds the device.  But it can't program it.
     
    =====================
    Target voltage detected
    Target device dsPIC30F5011 found.
    Device Revision ID = 1005
     
    You are trying to change protected secured memory. In order to do this you must select the "Secure and General Segments" option on the debug tool Secure Segment properties page.
    Failed to program device
    =====================
     
    The attached screen shot shows that I've told the ICD that it can change all secured memory.  Or is the the wrong place?  If so where do I change it?
     

    Attachment(s)

    Attachments are not available: Download requirements not met
    #6
    JPortici
    Super Member
    • Total Posts : 852
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/13 15:39:19 (permalink)
    0
    That is the correct menu. There you have to select secure and general segments.
    #7
    john.dammeyer
    Super Member
    • Total Posts : 423
    • Reward points : 0
    • Joined: 2004/01/02 20:07:06
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/13 16:22:03 (permalink)
    0
    That sort of worked.  Built the project.   Tried with ICD-3  Get the Program File could not be loaded: null message.  This ICD-3, with the exact same connection/wiring/power supply for the target, programs with the MPLAB8 and ICD-3 changed back with the ICD Driver Switcher.
     
    So I guess first question is why, with the ICD-3 set as the programmer, do I get the failure below.  Does the ICD-3 require a COFF file instead of the ELF?
     
    =====================
    make[2]: 'dist/default/production/xIM.X.production.hex' is up to date.
    make[2]: Leaving directory 'C:/Projects/.../xIM_Series/xIM/xIM.X'
    make[1]: Leaving directory 'C:/Projects/.../xIM_Series/xIM/xIM.X'
     
    BUILD SUCCESSFUL (total time: 206ms)
    The program file could not be loaded: null
     ======================
     
    With ICD-4 I've had to slow down the interface from normal to slow.  But even so I'm seeing  a variety of failures.
     
    ======================
    Target voltage detected
    Target device dsPIC30F5011 found.
    Device Revision ID = 1005
     
    Device Erased...
     
    Programming...
     
    The following memory area(s) will be programmed:
    program memory: start address = 0x0, end address = 0x4fff
    configuration memory
    EEData memory
    program memory
    Address: 0 Expected Value: 40100 Received Value: 0
    Failed to program device
    ===============
    I did find one issue with the ICD-4.  The MPLAB-X needs to run with administrator privileges on this PC or it fails somewhat silently when it tries to send to the USB.
     
    post edited by john.dammeyer - 2019/11/13 16:25:38
    #8
    john.dammeyer
    Super Member
    • Total Posts : 423
    • Reward points : 0
    • Joined: 2004/01/02 20:07:06
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/13 16:23:53 (permalink)
    0
    Oh and why is full device not better than select "secure and general segments".  One would think full device includes secure and general segments.
    #9
    JPortici
    Super Member
    • Total Posts : 852
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/14 01:15:15 (permalink)
    0
    I don't know. I know that if you have enabled memory protection in a PIC24/dsPIC/PIC32 that has codeguard and you want to re-program it, you have to either fully erase it manually or match the protection scheme with the programmer.
    It has always been like this.
     
    #10
    john.dammeyer
    Super Member
    • Total Posts : 423
    • Reward points : 0
    • Joined: 2004/01/02 20:07:06
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/14 02:04:45 (permalink)
    0
    The board I was trying to program did have write protection and the ds30Loader bootloader.  Code update is normally done over CAN bus.  So the bootloader is programmed with the ICD-3 and then the ds30_Loader sends the initial encrypted hex file to node 0x7F on CAN bus.  After that program updates are done to whatever nodeID that device has programmed into EEROM.
    But of course, new code may need to be programmed directly without the bootloader in order to set break points and figure out why something works or not.  So during there's an #ifdef __DEBUG that sets the configuration differently compared to release.
     
    In setting up t work with XC16 I may well have inadvertently erased the complete device including protection flags.  On the WIN-7 system I can now build the project with MPLAB-8 and XC16.  The ICD-3 programs the part without problems.  I can also single step and debug so the transition to XC16 from C30 is complete but it was painful.
     
    This approach has been working for more than 7 years with C30 and ICD-3.  So I really don't see any reason why suddenly a programmer that was working fine has problems with configuration bits and protection.
     
     
     
    #11
    JPortici
    Super Member
    • Total Posts : 852
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X IDE v5.30 with ICD-3 on WIN-7 2019/11/14 02:25:21 (permalink)
    0
    I don't know what to say, from your description what you see as a problem is what i have always seen in four years.
    In fact, what i do on my boards with bootloaders is that the bootloader is programmed with the code protect flags, but the firmware is not. (note that the only way to reset the memory protection bits is via a full chip erase with high voltage on MCLR, LVP can't reset the protection bits)
     
    This is because then i can test and debug the firmware on a blank pcb without having to erase all memory (takes more time) and having annoying warning at every debug session that the configuration will be changed.
    But if i take a board that was already programmed with the bootloader i have to manually erase it first, or select the correct programmer's settings.
     
    I wonder if this setting was already present in the project and something went wrong (copy/import/whatever) that deleted it
    #12
    Jump to:
    © 2019 APG vNext Commercial Version 4.5