• AVR Freaks

Hot!Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 (Solved)

Page: 12 > Showing page 1 of 2
Author
WaltR
Super Member
  • Total Posts : 3799
  • Reward points : 0
  • Joined: 2003/11/07 12:38:21
  • Status: offline
2020/02/15 08:32:20 (permalink)
0

Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 (Solved)

I have been using MPLAB X 5.30 for some time with a PICKit3 and all works perfectly.
 
Just bought a Curiosity PIC32MEF Dev Board 2.0 and can not get either X tool to connect.
Output:
Transmission on endpoint 2 failed
You have set the program speed to Normal. The circuit on your board may require you to slow the speed down. Please change the setting in the tool properties to low and try the operation again.

Failed to get Device ID. Please make sure the target device is attached and try the operation again.
Connection Failed.
Transmission on endpoint 2 failed
 
Then all the controls in the IPE go grey and can only close.
I have gone into the "Settings/Advanced/Settings" and changed "Curiosity/Starer Kits (PKoB4) Options(s)/Program Speed" from Normal to SLOW but still get this:
 
Transmission on endpoint 2 failed

Failed to get Device ID. Please make sure the target device is attached and try the operation again.
Connection Failed.
Transmission on endpoint 2 failed
 
Have tried three WORKING USB cables, Tried USB port on front and back of PC.
Have powered Curiosity with external power.
Have Re-booted PC.
Have disconnected/reconnect USB to Curiosity many times.
 
The Curiosity Board's LEDs are lite and the LEDs near the push buttons do a blinking pattern.
 
Device Manager shows "Microchip Tools/Microchip WinUSB Device"
The IPE shows the Tool as: Curiosity/Starter Kits (PKoB4) Serial number correctly.
 
Have done Google and Forum searches and tried everything suggest. Still get above ERROR.
 
Last thing I can think of is that this Curiosity Bd is BAD!!
 
Anyone have other suggestions???
 
post edited by WaltR - 2020/02/22 05:40:04
#1

27 Replies Related Threads

    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/15 13:44:14 (permalink)
    0
    Still NO happiness and still doing searches on issue.
    Found suggestion to click the "Refresh the debug tool status in MPLAB X IDE v5.30.
    No joy since this returned "Refreshing debug tool status...
    Refresh debug tool status could not be completed."
     
     
    #2
    Ken_Pergola
    Super Member
    • Total Posts : 2199
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/15 14:29:26 (permalink)
    0
    WaltR
    Anyone have other suggestions???



    Hello Walt,
    This may take a few minutes if you are willing to try it.
    Let's work together here to invoke the 'Hardware Tool Emergency Boot Firmware Recovery' (HTEBFR) option.
     
    This will re-program the Bootloader into the ATSAME70N21B MCU.
    Then MPLAB X IDE will sense the Bootloader and hopefully will bootload the Application successfully.
     
    1) Please MPLAB X IDE v5.30 for this.
    2) I attached some screen shots to guide you a bit.
    3) Follow the 'HTEBFR' "wizard" carefully in MPLAB X IDE v5.30 as you go through the steps.
     
    Let's see if this can help you. I'll check the MPLAB X IDE v5.30 help files to see if there are more details I can point you to.
     
    Best regards,
     
    Ken
    post edited by Ken_Pergola - 2020/02/15 14:49:10

    Attached Image(s)

    #3
    Ken_Pergola
    Super Member
    • Total Posts : 2199
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/15 14:30:31 (permalink)
    0
    The screen shots are showing out of order.
    Right-most screen shot is what you do first.
    #4
    Ken_Pergola
    Super Member
    • Total Posts : 2199
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/15 14:44:57 (permalink)
    0
    Screen shot showing MPLAB X IDE help:
    The procedure for the MPLAB Snap ICD shown in the MPLAB X IDE help is very similar to the MPLAB PKoB 4 procedure for your Curiosity board.
    I hope this helps.

    Attached Image(s)

    #5
    Ken_Pergola
    Super Member
    • Total Posts : 2199
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/15 14:47:48 (permalink)
    0
    Better still, the recovery procedure for your board is described in its User's Guide:
    http://ww1.microchip.com/downloads/en/DeviceDoc/Curiosity_PIC32MZEF2.0_Development_Board_Users_Guide_DS70005400A.pdf
     
     
    #6
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/16 07:51:55 (permalink)
    0
    Thanks for responding.
    Ok, I followed the 'HTEBFR' "wizard" instructions and after the the PKoB4 showed in Device Manager as an AT.. on COM5.This seems to indicate the loading of the AT boot loader.
    Unplug then replug the PKoB4 USB and now shows as Microchip WinUSB Device.
    So this proceedure seems to Work correctly.
     
    Then running the "Refresh Debug Tool Status" in MPLAB X IDE 5.30- got this:
     
    Connecting to MPLAB PKoB4...

    Currently loaded versions:
    Boot version...................01.01.00

    Now Downloading new Firmware for target device: PIC32MZ2048EFH144
    Updating firmware application...
    Transmission on endpoint 2 failed
    Transmission on endpoint 2 failed
    Transmission on endpoint 2 failed
    Transmission on endpoint 2 failed

    A communication error with the debug tool has occurred. The tool will attempt to recover momentarily.
    Connection Failed.
    Transmission on endpoint 2 failed


    Other info:
    OS: Windows 8.1 update.
    Driver: Microchip WinUSB Device 10-Sep-19 V1.0.2.0
     
    In the IDE under "Dashboard/Project Properties/PKoB4/Program Options/ Program Speed = Low.
    The IDE does Save and restore this upon closing and re-opening.
    However, the IPE DOES NOT and I will get in Both the IDE & IPE the message:
     
    You have set the program speed to Normal. The circuit on your board may require you to slow the speed down. Please change the setting in the tool properties to low and try the operation again.
     
    1st-Why does it need LOW SPEED?
    2nd- Why does the IPE not save and restore?
     
    Should I have tried the "Refresh Debug Tool Status"?
    Or can I just open the IPE and try "connect"?
     
    I appreciate all help on this.
    post edited by WaltR - 2020/02/16 07:58:06
    #7
    Ken_Pergola
    Super Member
    • Total Posts : 2199
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/16 14:15:17 (permalink)
    0
    WaltR
    ...So this proceedure seems to Work correctly....
     
    Then running the "Refresh Debug Tool Status" in MPLAB X IDE 5.30- got this:
     
    Connecting to MPLAB PKoB4...

    Currently loaded versions:
    Boot version...................01.01.00

    Now Downloading new Firmware for target device: PIC32MZ2048EFH144
    Updating firmware application...
    Transmission on endpoint 2 failed
    Transmission on endpoint 2 failed
    Transmission on endpoint 2 failed
    Transmission on endpoint 2 failed

    A communication error with the debug tool has occurred. The tool will attempt to recover momentarily.
    Connection Failed.
    Transmission on endpoint 2 failed



    Hello Walt,
     
    As you have reported, you have successfully executed the 'Hardware Tool Emergency Boot Firmware Recovery' (HTEBFR) option. Thank you for going through that procedure.
     
    I have a few things for you to try if you are willing:
     
    1) You should not have to do this but when you get those 'Transmission on endpoint 2 failed' errors I would suggest:
    a) Shutting down MPLAB X IDE v5.30.
    b) USB un-plug your Curiosity PIC32MEF Dev Board 2.0 from your computer.
    c) Launch MPLAB X IDE v5.30 and load up your MPLAB X IDE project you are working with.
    d) Plug you Curiosity PIC32MEF Dev Board 2.0 back into the USB port of your computer.
    e) Invoke the 'Refresh Debug Tool Status' button in the 'Dashboard'.
     
    I would try step #1 (a through e) a few times.
    If you are still seeing MPLAB X IDE v5.30 not able to update the Curiosity PIC32MEF Dev Board 2.0's firmware I would try:
     
    2) Again, you should not have to do this but do you have a Windows 7 or Windows 10 PC available that you could try?
     
    Best regards,
     
    Ken
    #8
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/16 15:13:16 (permalink)
    0
    1) trying this procedure steps a-e.  4 times and all gave:
    in "PKob4" output:
    *****************************************************

     
    Transmission on endpoint 2 failed

    Failed to get Device ID. Please make sure the target device is attached and try the operation again.
    Connection Failed.
    Transmission on endpoint 2 failed
     
    In Curiosity20_test (Refresh Debug Toll Status):
    Refreshing debug tool status...
    Refresh debug tool status could not be completed.
     
    Also trying the IPE 'connect':
    Tool: "Curiosity/Starter Kit (PKoB4) S No..."  then get-
    *****************************************************



    Transmission on endpoint 2 failed
    You have set the program speed to Normal. The circuit on your board may require you to slow the speed down. Please change the setting in the tool properties to low and try the operation again.

    Failed to get Device ID. Please make sure the target device is attached and try the operation again.
    Connection Failed.
    Transmission on endpoint 2 failed
     
    I do have a Window 7 PC at work with MPLAB X 5.30 installed. I was planning to try this tomorrow morning.
     
     
    #9
    ibbro
    Starting Member
    • Total Posts : 87
    • Reward points : 0
    • Joined: 2015/10/22 07:34:56
    • Location: 0
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/16 16:00:02 (permalink)
    0
    I communicated with one person on the forums that was having similar issues with 2 different Curiosity 2 MZ boards. He was told by Microchip on a support ticket that MPLAB 5.30 has a problem with them which will be corrected in the next release. I am developing on two of them under windows 10 and have not had any major problems. I did brick them a couple of times when I connected UART6 to the Pk04 virtual port. There is a known problem there (mentioned in the forums) which required doing the hardware emergency procedure you have done to get them running again. Once I removed the UART6 connection they have behaved. So no answers, just minor confirmation they can be finicky. I'd probably try windows 10.
    #10
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/16 18:35:02 (permalink)
    0
    Thanks for suggestion. I currently have no intention to go to Win 10 since 8.1 has been working fine.
     
    Would down grading MPLAB X to a previous version be a better idea until Microchip fixes this?
    I did search this forum but never saw those posts. Could you please post links to those posts.
     
    I did order 4 more different USB cables hoping the USB cables I have a marginal with the Curiosity bd.
    I should have the new USB cables later this week.
    I will try win 7 tomorrow at work.
    post edited by WaltR - 2020/02/16 18:37:23
    #11
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 07:08:44 (permalink)
    0
    Ok, now on a Win 7 PC. I had MPLAB X V5.15 installed which seems NOT to support the Curiosity bd.
    Downloaded V5.30 and installed.
    Looked at what drivers came with V5.30 and there is an additional directory under 64bit!!!
    "C:\Program Files (x86)\Microchip\MPLABX\v5.30\Switcher\64Bit\winusb\amd64_unsigned"
    Then drives in these directories also have different Dates than what was installed on my Win8.1 PC.
     
    Plugged in the Curiosity bd and the PKoB4 showed in device manager.
    Started the V5.30 IPE and in Device Manager it changed to Microchip WinUSB...the driver auto installed upon opening the IPE. This did NOT happen on Win8.1
    Selected the PIC32 on the Curiosity bd, clicked connect and all good.
    Connecting to MPLAB PKoB4...

    Currently loaded versions:
    Application version............00.03.33
    Boot version...................01.01.00
    Script version.................00.03.33
    Script build number............0540a22e50
    Target voltage detected
    Target device PIC32MZ2048EFM144 found.
    Device Revision Id  = 0xB2
    Serial Number:
    Num0 = 6218c28b
    Num1 = 7e2a6bc4
     
    My next step is to uninstall the MPLAB X5.30, delete the installer and download a fresh copy of the 5.30 installer then re-install.
    I'll post the results of this tonight.
     
    #12
    Jim Nickerson
    User 452
    • Total Posts : 6584
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 07:15:03 (permalink)
    0
    do remember to remove the User and Cache directory as displayed in MpLab X Help, About as well
    I have found removing these  dirs is often as good as re installing.
    #13
    ibbro
    Starting Member
    • Total Posts : 87
    • Reward points : 0
    • Joined: 2015/10/22 07:34:56
    • Location: 0
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 07:36:21 (permalink)
    0
    Here is the thread I was referring to:
    https://www.microchip.com/forums/m1121298.aspx
    #14
    Ken_Pergola
    Super Member
    • Total Posts : 2199
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 08:51:07 (permalink)
    0
    Hello Walt,
     
    Is your Windows 8.1 OS 32- or 64-bit?
     
    Best regards,
     
    Ken
    #15
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 09:04:09 (permalink)
    0
    ibbrowning
    Here is the thread I was referring to:
    https://www.microchip.com/forums/m1121298.aspx


    Thanks for the link. That thread has other interesting discussions that will be handy when I get to do coding.
    I do not to use Harmony or even MCC but code all from scratch so the config and other details are helpful.
     
    #16
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 09:04:33 (permalink)
    0
    Ken_Pergola
    Hello Walt,
     
    Is your Windows 8.1 OS 32- or 64-bit?
     
    Best regards,
     
    Ken


    64 bit
    #17
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 09:07:39 (permalink)
    0
    JANickerson
    do remember to remove the User and Cache directory as displayed in MpLab X Help, About as well
    I have found removing these  dirs is often as good as re installing.


    Ok, I do see in 'help/about' the path to the user and cache directories.
     
    Do I delete just the v5.30 directories or all the way up to the mplab_ide directories?
    Should I first try to just delete these then start MPLAB and plug in the Curiosity bd?
     
    post edited by WaltR - 2020/02/17 09:09:51
    #18
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 16:29:21 (permalink)
    0
    Unistalled MPLAB and deleted all the cache in Users.
    Downloaded fresh MPLAB X and installed.
    No change- still fails exactly as in posts above.
     
    Details from the IDE Help/About:
    Product Version: MPLAB X IDE v5.30
    Java: 1.8.0_181; Java HotSpot(TM) 64-Bit Server VM 25.181-b13
    Runtime: Java(TM) SE Runtime Environment 1.8.0_181-b13
    System: Windows 8.1 version 6.3 running on amd64; Cp1252; en_US (mplab)
    User directory: C:\Users\waltr\AppData\Roaming\mplab_ide\dev\v5.30
    Cache directory: C:\Users\waltr\AppData\Local\mplab_ide\Cache\dev\v5.30\var
     
    Details from the IPE Help/About:

    Product Version: MPLAB X IPE v5.30
    Java: 1.8.0_181; Java HotSpot(TM) 64-Bit Server VM 25.181-b13
    Runtime: Java(TM) SE Runtime Environment 1.8.0_181-b13
    System: Windows 8.1 version 6.3 running on amd64; Cp1252; en_US (mplab_ipe)
    User directory: C:\Users\waltr\AppData\Roaming\mplab_ipe\dev\v5.30
    Cache directory: C:\Users\waltr\AppData\Local\mplab_ipe\Cache\dev\v5.30\var
     
    Driver installed:
    Microchip Tecnology, Inc
    10-Sep-19
    V 1.0.2.0
     

    Is there Something in Win8.1 that can 'block' USB port access from Apps?
     
     Should I open a Trouble Ticket on this issue??
     
    post edited by WaltR - 2020/02/17 16:39:10

    Attached Image(s)

    #19
    WaltR
    Super Member
    • Total Posts : 3799
    • Reward points : 0
    • Joined: 2003/11/07 12:38:21
    • Status: offline
    Re: Curiosity PIC32MEF Dev Board 2.0 NOT connecting to MPLAB X IPE or IDE V5.30 2020/02/17 16:48:56 (permalink)
    0
    Interesting:
    I just 'disabled' the WinUSB drive in Device Manager.
    Then opened the IDE and clicked Refresh tools-
    Got the SAME ERROR as when driver in enabled.
    post edited by WaltR - 2020/02/17 17:17:45
    #20
    Page: 12 > Showing page 1 of 2
    Jump to:
    © 2020 APG vNext Commercial Version 4.5