• AVR Freaks

Bricked Curiosity HPC

Author
dwegscheid
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2019/07/25 05:20:53
  • Location: 0
  • Status: offline
2019/11/19 14:36:58 (permalink)
0

Bricked Curiosity HPC

I just started MPLAB IPE with my Curiosity HPC connected; IPE went to update the firmware, the firmware update failed, and now the Curiosity HPC appears bricked. It shows up in 'lsusb' output, I can select it in MPLABX IDE, but whenever I go to deploy code, I get "The last tool user for this project is unavailable. Please select the tool that you want to use to debug or program from the following list of available tools:".
 
But the Curiosity/Starter Kits (PKOB4) shows up with two green dots, and can be selected.
 
Is there a way to recover from this?
#1

5 Replies Related Threads

    ric
    Super Member
    • Total Posts : 24638
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: Bricked Curiosity HPC 2019/11/19 14:40:40 (permalink)
    0
    Are the IPE and IDE both the same version?
    In the IDE, under the settings for the PKOB4, is there an option to force update the firmware?
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #2
    dwegscheid
    New Member
    • Total Posts : 10
    • Reward points : 0
    • Joined: 2019/07/25 05:20:53
    • Location: 0
    • Status: offline
    Re: Bricked Curiosity HPC 2019/11/19 15:08:07 (permalink)
    0
    IPE and IDE are same version.
     
    There is a "Firmware Pulldown" that shows "Firmware update options", but there does not seem to be a way to force a firmware update.
     
    There *is* the "Hardware Tool Emergency Boot Recovery", which appears to be what I want, but it requires me to short a couple of pins or pads on the board to put it into boot recovery mode. Unfortunately, I can not find any documentation on where the boot recovery pads/holes/jumpers are on a Curiosity HPC.
    #3
    NKurzman
    A Guy on the Net
    • Total Posts : 18060
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    NKurzman
    A Guy on the Net
    • Total Posts : 18060
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: Bricked Curiosity HPC 2019/11/19 16:47:14 (permalink)
    5 (1)
    Or 
    http://ww1.microchip.com/downloads/en/DeviceDoc/Curiosity-High-Pin-Count-Dev-Board-User-Guide-40001856A.pdf
     
    That is not a PKOB4, but looks like a PKOB3.  And has a note about LVP.
    #5
    dwegscheid
    New Member
    • Total Posts : 10
    • Reward points : 0
    • Joined: 2019/07/25 05:20:53
    • Location: 0
    • Status: offline
    Re: Bricked Curiosity HPC 2019/11/19 18:18:10 (permalink)
    0
    it is a HPC. Not a shred of doc on Emergency bootloader.....
     
    It's a PKOB3, not a PKOB4; that was my problem. I eventually got IPE to get a good load of firmware in there, and once I had the correct target set up in the IDE, I can load code just fine.
    #6
    Jump to:
    © 2019 APG vNext Commercial Version 4.5