VS code + Pymakr unable to connect to the LoPy4



  • Hello,

    I am trying to program a LoPy4 + Expansion Board v3.1. VS + Pymakr is not able to connect to the LoPy4.

    My setup is the following one:

    • OS: Ubuntu 18.04.
    • Virtual Studio Code 1.43.2
    • Pymakr 1.1.6

    I successfully upgraded the Expansion Board v3.1 with expansion31_0.0.11.dfu firmware.

    I successfully upgraded Lopy4 firmware at 1.20.2.rc6 firmware level.

    lsusb recognizes the device:

    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 008: ID 06cb:00bd Synaptics, Inc. 
    Bus 001 Device 005: ID 5986:114e Acer, Inc 
    Bus 001 Device 007: ID 1d5c:7102  
    Bus 001 Device 003: ID 14cd:8601 Super Top 
    Bus 001 Device 031: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
    Bus 001 Device 030: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230
    Bus 001 Device 029: ID 413c:a503 Dell Computer Corp. 
    Bus 001 Device 028: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
    Bus 001 Device 027: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
    Bus 001 Device 032: ID 04d8:ef98 Microchip Technology, Inc. 
    Bus 001 Device 010: ID 8087:0aaa Intel Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    

    The command screen /dev/ttyACM0 115200 hangs.

    When I use Pymakr > Extra > List Serial Ports, /dev/ttyACM0 (Pycom) (copied to clipboard) is detected.

    However, I'm unable to connect to the device using Pymakr > Connect. The connection is hanging.

    Additional remarks:

    • I get the same behavior with another LoPY4 device.
    • I get the same behavior when I connect the LoPY4 devices to PySense devices.
    • My LoPy4 devices are connected to a LoRa antenna.
    • I tried on another computer... with same results.
    • I tried with another USB cable... same results again.

    Any clue of what can be wrong?



  • Thanks to Pycom support, the issue was solved by a format of the whole Flash Memory using pycom-fwtool-cli -p <port> erase_all command and flashing again the firmware.


Log in to reply
 

Pycom on Twitter