Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    pytrack dfu 0.0.7 no serial port

    Scheduled Pinned Locked Moved Issues & Bugs
    pytrackwindowsserialupdatefirmware
    4 Posts 2 Posters 1.4k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kanalizator
      last edited by

      Today I updated my pytrack to the latest firmware (pytrack_0.0.7.dfu) with status "Done!". After update I am able to login via telnet over Wi-fi, but there is no serial port any more, only pytrack device. What should I do to bring serial port back?

      I am using:

      • ATOM 1.21.1 x64
      • Microsoft Windows [Version 10.0.16299.19]
      • Pymakr 1.2.0
      • Python 3.6.3 (v3.6.3:2c5fed8, Oct 3 2017, 17:26:49) [MSC v.1900 32 bit (Intel)] on win32

      Update tools:

      • dfu-util 0.8
      • zadig-2.3.exe

      Thanks.

      C 1 Reply Last reply Reply Quote 0
      • C Offline
        crumble @kanalizator
        last edited by

        @kanalizator after installing the dfu driver, the PyTrack will be detected as a a dfu device and not as a COM device. You have to deinstall the dfu driver, so that PyTrack will be detected a COM device again. You can see this in the device manager. But only for a few seconds. If you plugin your device it will show up for a few second as such a device and will then disapear.

        C 1 Reply Last reply Reply Quote 0
        • K Offline
          kanalizator
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • C Offline
            crumble @crumble
            last edited by

            Every update seems to be different. This time, the PyTrack was detected as a COM device. With the same number as before :). But I was not able to connect. To fix it, I had to select show unconnected devices in the device manager, browsed for the usk driver and deleted the unknown and unconnected device.

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post

            Pycom on Twitter

            Pycom