• AVR Freaks

on board programmer

Page: 12 > Showing page 1 of 2
Author
tcross
Super Member
  • Total Posts : 281
  • Reward points : 0
  • Joined: 2006/09/09 07:57:22
  • Location: 0
  • Status: offline
2017/02/10 21:36:25 (permalink)
5 (1)

on board programmer

Just received my new explorer 16/32 board  and  PIX32MZ PIM today. Everything works with my ICD3 but nothing happens when I try using the on board programmer (J18). Nothing shows up in device manager. I have used switcher and changed everything over to X. MPLAB 3.50 does not show the board attached either. I tried with another PIC3MX360 PIM with the same results. What am I doing wrong?
 
Thanks in advance.
#1

35 Replies Related Threads

    NKurzman
    A Guy on the Net
    • Total Posts : 18061
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/11 00:22:02 (permalink)
    3 (1)
    Is the board powered?
    Are the jumpers set for The onboard programmer?
    #2
    tcross
    Super Member
    • Total Posts : 281
    • Reward points : 0
    • Joined: 2006/09/09 07:57:22
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/11 09:48:06 (permalink)
    0
    Yep on power and I am not seeing any jumpers that would help.
     
    I think the answer is that the processors in my two PIM don't support the PK08 programming as that option is not coming up green in the hardware section of MPLAB. Thats OK, I can use my ICD3.
     
    Thanks
     
    #3
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/11 16:33:43 (permalink)
    4.33 (3)
    this is the supported pic32MZ list in the PKOB xml file in com-microchip-mplab-mdbcore-pkobskde.jar
    <mp:device mp:name="PIC32MZ2048ECM144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048ECH144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048EFH144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048EFM144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2064DAB288" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2064DAA288" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2064DAG169" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2064DAH169" mp:support="beta"/>
    <mp:device mp:name="PIC32MK1024GPE100" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2048EFM100" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048ECH100" mp:support="yes"/>

     
    I think the guy who created this xml file is a little bit lazy, so only a few is put into the list.  You can try to add your PIC32MZ into it and rejar(rezip) the file.   I tried it with the other PIC16, and it works.
     
    I will try it later with my PIC32MZ2048EFH100...
     
    post edited by timijk - 2017/02/11 17:21:09
    #4
    NKurzman
    A Guy on the Net
    • Total Posts : 18061
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/11 17:11:07 (permalink)
    0
    I assume you removed the ICD3.
    if it is not showing up in device Manager, even as unknown, it , the port, or the cable is bad.
    Do you have rights to install drivers on that PC?
    #5
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/11 17:16:49 (permalink)
    5 (2)
    I am able to add it to the list and read the device memory from it.  Just a couple of notices here.
     
    1. At first, copy the jar file to another folder and change the *.jar to *.zip.
    2. Copy pkobskde.platformTool.xml to another folder for editing, and add you PIC into the list.
    3. Copy the xml file into the zipped folder (you may have to delete the original xml file first).  Originally,  I tried to unzip the file and rezip it with the new xml, but it seems my Windows default zip does not match the jar's standard.  So it fails.  Then I tried to just copy-paste it into the zip folder, and it works.
    4. Rename the new zip file to *.jar and copy it back.
    5. Clean up the MPLAB X IDE cache, the cache location is shown in the HELP about menuitem.
    Here is the result
    *****************************************************
    Connecting to Starter Kit on Board...
    Currently loaded firmware on Starter Kit on Board
    Firmware Suite Version.....01.42.18 *
    Firmware type..............dsPIC33F/24F/24H
    Now Downloading new Firmware for target device: PIC32MZ2048EFH100
    Downloading bootloader
    Bootloader download complete
    Programming download...
    Downloading RS...
    RS download complete
    Programming download...
    Downloading AP...
    AP download complete
    Programming download...
    Currently loaded firmware on Starter Kit on Board
    Firmware Suite Version.....01.46.14
    Firmware type..............PIC32MZ
    Target voltage detected
    Target device PIC32MZ2048EFH100 found.
    Device ID Revision = A1
    The following memory area(s) will be read:
    program memory: start address = 0x0, end address = 0x1fffff
    boot config memory
    configuration memory
    Reading...
    Read complete

     
    #6
    tcross
    Super Member
    • Total Posts : 281
    • Reward points : 0
    • Joined: 2006/09/09 07:57:22
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/11 19:58:17 (permalink)
    3 (1)
    Thanks for the reponces.....
     
    Yes I may have two problems. Since nothing is showing up in device manager a may have a bad cable. I should have the correct access rights since my ethernet starter board shows up when I plug that in .....but I might have used a different cable. Don't have it here now to test.
     
    I do think I need to edit my JAR file to include that processor as mentioned above.  I will try that ASAP.
     
    Thanks again!
    #7
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/11 23:35:16 (permalink)
    4.33 (3)
    Just some update...
     
    Originally I made a mistake to zip the root folder com-microchip-mplab-mdbcore-pkobskde, so it didn't work.  I should zip the two sub folders (com and META-INF) then change the file name to com-microchip-mplab-mdbcore-pkobskde.jar
    #8
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/15 14:26:15 (permalink)
    0
    I noticed my explorer 16/32 show up in the HID section of device manager, as a generic HID device, nothing else. Maybe that's the way its supposed to be? I don't know. The only other thing I read that might have to do with it was not to have another programmer connected if you connect usb cable to J18. 
     
    I have two chips, an mz2048efh100 and a mx360f512L. Neither show up in the listing window as supported with pkob. I ordered a picKit3 yesterday, would be good, yet bad if the suggestion above worked.
     
    However, I look in C:\Program Files (x86)\Microchip\MPLABX\v3.51\mplab_ide\mdbcore\config\Modules and the pkobskde.xml file doesn't list any chips at all.
    #9
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/15 14:49:17 (permalink)
    0
    Ah, I found this here: C:\Program Files (x86)\Microchip\MPLABX\v3.51\mplab_ide\mdbcore\modules in ...skobskde.jar:
     
    </mp:family>
    <mp:family mp:family="32x">
    <mp:device mp:name="PIC32MX220F032B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX230F064B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX130F064B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX120F032B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX210F016B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX110F016B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX150F128B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX220F032C" mp:support="yes"/>
    <mp:device mp:name="PIC32MX220F032D" mp:support="yes"/>
    <mp:device mp:name="PIC32MX250F128B" mp:support="yes"/>
    <mp:device mp:name="PIC32MX250F128C" mp:support="yes"/>
    <mp:device mp:name="PIC32MX250F128D" mp:support="yes"/>
    <mp:device mp:name="PIC32MX430F064L" mp:support="yes"/>
    <mp:device mp:name="PIC32MX450F256L" mp:support="yes"/>
    <mp:device mp:name="PIC32MX470F512L" mp:support="yes"/>
    <mp:device mp:name="PIC32MX795F512L" mp:support="yes"/>
    <mp:device mp:name="PIC32MX270F256D" mp:support="yes"/>
    <mp:device mp:name="PIC32MX570F512L" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048ECM144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048ECH144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048EFH144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048EFM144" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2064DAB288" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2064DAA288" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2064DAG169" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2064DAH169" mp:support="beta"/>
    <mp:device mp:name="PIC32MK1024GPE100" mp:support="beta"/>
    <mp:device mp:name="PIC32MZ2048EFM100" mp:support="yes"/>
    <mp:device mp:name="PIC32MZ2048ECH100" mp:support="yes"/>
    <mp:device mp:name="PIC32MK1024MCF100" mp:support="beta"/>
    <mp:device mp:name="PIC32MX470F512H" mp:support="yes"/>
    <mp:device mp:name="PIC32MM0064GPL036" mp:support="beta"/>
    <mp:device mp:name="PIC32MM0256GPM064" mp:support="beta"/>
     
    So my chips aren't on this list, I guess I'll have to use picKit3.
     
    #10
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/15 14:50:03 (permalink)
    4.33 (3)
    the xml list is in ..\mplab_ide\mdbcore\modules\com-microchip-mplab-mdbcore-pkobskde.jar
     
    ++ the guy who created the list is just lazy... you can add your PIC into that list and try it. I have shown it in my previous post.
    post edited by timijk - 2017/02/15 14:52:11
    #11
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/15 15:00:00 (permalink)
    0
    Thanks I see it now, I'll try editing with notepad++ I'll get really confused if I have to start zipping and unzipping things...
    #12
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/15 15:25:05 (permalink)
    0
    Edited the file, but nogo, in the Hardware tool list, Starter kit (pkob) is still red. I can get the pic24FJ32MC102 to come up green though, so I didn't ruin the file :)
    #13
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/15 15:40:14 (permalink)
    5 (1)
    Have you cleaned the cache for the MPLAB X IDE?
    #14
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/15 16:16:35 (permalink)
    0
    Yeah.... about that... No I haven't... looked online because the other guy said do it, and looked in the help file... didn't find anything on how to do it.
    #15
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/15 16:22:55 (permalink)
    4.33 (3)
    the cache location is shown in the MPLAB X IDE menu <HELP/about>.
    #16
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/15 16:41:04 (permalink)
    0
    Still a no go, that didn't help :(
    #17
    timijk
    Super Member
    • Total Posts : 1216
    • Reward points : 0
    • Joined: 2007/11/26 00:30:07
    • Location: Taiwan
    • Status: offline
    Re: on board programmer 2017/02/15 17:22:49 (permalink)
    4 (2)
    I am not sure how you updated the xml file in the zipped jar.  You can double check if the xml file in the new jar does include your updated xml file.
     
    I attached the jar file I was using with the PIC32MZ2048EFH100 in MPLAB X IDE v3.50.  Rename zip to jar.
    #18
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/16 10:08:52 (permalink)
    0
    I zipped, then renamed the file .jar, now in the hardware tools listing window the "starter kit (pkob)" (previously it was red, now it is gone) has disappeared. Now it shows SKDE PIC32 and several different options that didn't appear before but they are all red. I tried selecting SKDE PIC32 and it didn't work. I'mm try your file and see if it works with the mx.
     
    #19
    brian46
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2016/12/12 18:17:55
    • Location: 0
    • Status: offline
    Re: on board programmer 2017/02/16 10:28:10 (permalink)
    0
    So your file works with the MZ chip and pkob is visible and green. I edited my .jar file with notepad++ and then zipped it, then renamed it to .jar. I will try editing the file with notepad or something else and then zip and rename it.
    #20
    Page: 12 > Showing page 1 of 2
    Jump to:
    © 2019 APG vNext Commercial Version 4.5