• AVR Freaks

Hot!MPLAB X 5.25 problem with PKOB for PIC32MZ board D320010

Author
boatbodger
Starting Member
  • Total Posts : 47
  • Reward points : 0
  • Joined: 2011/03/27 15:39:07
  • Location: 0
  • Status: offline
2019/10/13 10:13:20 (permalink)
0

MPLAB X 5.25 problem with PKOB for PIC32MZ board D320010

This (Microchip) Eval board has its own built in PIC24-based debugger.
I struggled to get the correct device drivers to install.
Windows (7/64) was INSISTING it was a "USB Input Device" in Device Manager
I fixed that by editing the .inf file at:
C:\Program Files (x86)\Microchip\MPLABX\v5.25\Switcher\64Bit\winusb\amd64\...
adding in the line
%DESCRIPTION%=USB_Install,USB\VID_04d8&PID_8107
Now, when plugged in, it appears as a Microchip Tools/Microchip WinUSB Device.
However, MPLAB X 5.25 still refuses to let me use it - claiming it is "Unsupported"
I closed MPLAB X IDE 5.25 and opened MPLAB X IPE 5.25.
Here, I was able to identify the device as "“Starter Kits (PKOB) S.N. BUR nnnn"
I selected the correct microcontroller (in my case PIC32MZ2064DAR169 ) and clicked Connect.
At that point, IPE pushed many firmware updates to the board, and finally said "yes, there's a microcontroller there":
Target voltage detected
Target device PIC32MZ2064DAR169 found.
Device ID Revision = B1
DEVSN0 = ffffffff
DEVSN1 = ffffffff

Hurrah!
BUT... MPLAB X IDE is still saying "Not Supported", even though it is detecting the presence of the board.
Me? Grumpy? Yes. You betcha.
To keep moving, I can of course create the hex file in IDE then use IPE to blow it in to the board, but then I don't get any debugging facilities.

Anybody got any ideas on how to get round this?
Is it possible to use a PicKit3 or 4 with this chip instead? I have both, and could probably hook it up - there is a 6-pin connector which I suspect would work.

Dead frustrating...
Chris
#1

3 Replies Related Threads

    Mysil
    Super Member
    • Total Posts : 3421
    • Reward points : 0
    • Joined: 2012/07/01 04:19:50
    • Location: Norway
    • Status: offline
    Re: MPLAB X 5.25 problem with PKOB for PIC32MZ board D320010 2019/10/13 18:57:16 (permalink)
    +2 (2)
    Hi,
    There may seem that development board DM320010 hardware have been updated,
    Without PKOB software been updated correspondingly! 
    In the webpage for DA starter kit:
    "For starter kits populated with the PIC32MZ2064DAH (older) on the daughter card, please visit the MPLAB Harmony 2 Framework site for information about software, demos, and board support packages.
    For starter kits populated with the PIC32MZ2064DAS (newer) on the daughter card, please visit the MPLAB Harmony 3 Framework site for information about software, demos, and board support packages. "
     
    For starter kits without Crypto hardware, the corresponding chips seem to be:
    PIC32MZ2064DAG169 (older) on the daughter card,
    PIC32MZ2064DAR169 (newer).
     
    While the PIC24 on board debugger mainly use PICkit 3 firmware and tables, 
    there are some tables hidden inside MPLAB installation listing which PIC chips are expected to work with the on-board debugger.
     
    It is possible to update this table yourself,
    but since it is inside a compressed .jar archive, it may be somewhat tricky:
    In windows installation on my development computer is:
        C: / Program Files (x86) / Microchip / MPLABX / v5.25 / mplab_platform / mdbcore / modules
    Among the files is:
        com-microchip-mplab-mdbcore-pkobskde.jar
    I make a backup copy of this file, and then open the original archive using WinZip
    Inside this file is: pkobskde.platformTool.xml
    I open the file inside WinZip, for editing using Notepad++ editor,
    copy and paste the nessesary additional lines, and save the updates.
                <mp:device mp:name="PIC32MZ2064DAR169" mp:support="beta"/>    
                <mp:device mp:name="PIC32MZ2064DAS169" mp:support="beta"/>

    When the editor is completed, WinZip will ask to update the archive with the modified file.
    Before starting MPLAB X again, delete the mplab cache directory.
    Location of the cache directory is revealed by 'Help' 'About' menu item in MPLAB X.
    See also this thread: https://www.microchip.com/forums/FindPost/974175
     
    Until Microchip make the nessesary update, you will have to repeat such update for each new release of MPLAB.
     
    Another possibility is to remove the jumper J17 on edge of the board, see schematics 4 of 5, page 38.
    and connect PICkit 3 or PICkit 4, to the 6 pin connector J12, ICSP HDR, see schematics 2 of 5, page 36,
    in User's guide for the board.
     
        Mysil
     
    post edited by Mysil - 2019/10/13 19:45:47
    #2
    boatbodger
    Starting Member
    • Total Posts : 47
    • Reward points : 0
    • Joined: 2011/03/27 15:39:07
    • Location: 0
    • Status: offline
    Re: MPLAB X 5.25 problem with PKOB for PIC32MZ board D320010 2019/10/15 02:24:48 (permalink)
    0
    That worked.
    I am finding, however, that the onboard programmer seems MUCH slower than the PicKit4 - which in the end, I had connected, as you suggest.
    Bit of a shame, as it would be useful in my test situation to just have the one USB connection for power and programming.
    To other readers, please note that in addition to telling MPLAB about the PKOB capability, I previous had to hack the device list to include the DevID for the PKOB (8017)
     
    Still, its progress.
    Thanks again,
    Chris
    #3
    JPortici
    Super Member
    • Total Posts : 820
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X 5.25 problem with PKOB for PIC32MZ board D320010 2019/10/15 03:37:22 (permalink)
    0
    It is. It is also way more prone to bug out than PK3.
    Let's hope the new devboards with PK4OB (which us mortal still has to see) will be immune to this problem, aka let's hope they will use the same firmware.
    #4
    Jump to:
    © 2019 APG vNext Commercial Version 4.5