• AVR Freaks

Hot!DM164136 HPC-Curiosity Board is broken by MPLABX v5.45

Author
dan1138
Super Member
  • Total Posts : 4242
  • Reward points : 0
  • Joined: 2007/02/21 23:04:16
  • Location: 0
  • Status: offline
2020/12/18 17:54:09 (permalink)
5 (2)

DM164136 HPC-Curiosity Board is broken by MPLABX v5.45

After MPLABX v5.45 updates the PKoB4 in the DM164136 with Tool pack version 1.2.293 the virtual COM port no longer functions.

The COM port is enumerated by the Windows host system. Terminal application can open the COM port but no data is received.

Using the MPLABX project properties for the PKoB4 to use Tool pack version 1.1.166 or 1.0.36 will make the virtual COM port work as expected.

Without the virtual COM port all of the UART dependent labs from the DM164136 HPC Curiosity Board demo code will fail.

<EDIT>

Add more details about what PKoB4 firmware is bad and how to workaround it.
post edited by dan1138 - 2020/12/18 23:46:14
#1

4 Replies Related Threads

    judd
    Starting Member
    • Total Posts : 57
    • Reward points : 0
    • Joined: 2019/04/15 22:30:22
    • Location: 0
    • Status: offline
    Re: DM164136 HPC-Curiosity Board is broken by MPLABX v5.45 2021/01/12 15:40:49 (permalink)
    2 (1)
    Thanks for the feedback.
    This issue has been reported to the product developers who are working on a fix...
    #2
    ashdash
    Starting Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2021/01/13 12:22:55
    • Location: 0
    • Status: offline
    Re: DM164136 HPC-Curiosity Board is broken by MPLABX v5.45 2021/01/14 16:37:23 (permalink)
    3 (1)
    I concur that the virtual com port is not working in MPLABX v5.45. I can't confirm that it worked with earlier versions.  I confirmed with an oscilloscope that the target is outputting, but nothing on CoolTerm or others.
     
    I tried jumpering TX to RX on the VCOM header. I guess if the com port of the debugger was working, that should echo to the terminal, but nothing.
     
    It's disappointing when a tool lets you down because you waste so much time scratching your head trying to figure out what you have done wrong!
    #3
    dan1138
    Super Member
    • Total Posts : 4242
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: DM164136 HPC-Curiosity Board is broken by MPLABX v5.45 2021/01/14 22:08:13 (permalink)
    2 (2)
    @ashdash,
     
    MPLABX v5.45 installs the PKoB4 tool pack version 1.2.293 and to get the the virtual COM port working you will need to install a down rev version of the PKoB4 tool pack manually. Tool pack version 1.1.166 does work.
     
    There's no Microchip documentation to walk you through this process step by step. I am too disappointed with Microchip efforts (or lack there of) at documenting anything to write out the steps for you. If you want to make your DM164136 work sooner you will need to become more of an expert at using the MPLABX IDE.
    #4
    ashdash
    Starting Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2021/01/13 12:22:55
    • Location: 0
    • Status: offline
    Re: DM164136 HPC-Curiosity Board is broken by MPLABX v5.45 2021/01/25 12:31:39 (permalink)
    5 (3)
    Thanks dan1138 for your help.

    I can confirm tool pack 1.1.166 for MPLABX v5.40 restores the com port functionality.  This is a rough guide what to do.

    Plug the dev board into the usb port.

    Open MPLABX v5.45
    Tools menu
        >Packs (3rd option down)
            Click Tab "Tool Packs"
            Scroll down to PKOB4_TP (list alphabetic)
            Locate 1.1.166 Release for 5.40
            Click "Install" link
    Close

    Go to project dashboard
    Click Project properties icon
        Categories pane
        Click PKoB4
            Option categories dropdown: "Tool pack selection" (last option)

            Specifically selected version
                Select 1.1.166
                Apply

    Programme the device. This will force firmware 1.1.166 to be loaded as part of the process. There may be a way to just load the firmware but I don't see it.

    Make sure all your comms settings (baud rate, etc) are the same everywhere.
    As a test, if you jumper TX to RX on header, CoolTerm will echo the keyboard.

    Jumper whichever pin has the uart output to TX. You should now see your output on CoolTerm or whichever terminal programme you prefer.


    Rough guide. Some steps may have been missed, but you should get the idea.
     
    Hope it helps.
    post edited by ashdash - 2021/01/25 12:42:38
    #5
    Jump to:
    © 2021 APG vNext Commercial Version 4.5