failed to set dtr/rts

[on4aa]

@xykon

I could update the firmware of the Pysense & Pytrack boards, but still no luck with the ESP32 firmware.

$ sudo dfu-util -D pysense_0.0.8.dfu
$ sudo dfu-util -D pytrack_0.0.8.dfu

The sudo should be added to the documentation.

[on4aa]

@xykon
At last, success! The ESP32 firmware update (GUI-version) succeeded now, after creating /etc/udev/rules.d/77-mm-pycom.rules containing:

# All devices from Pycom LTD
# Since Pycom is not producing any modems, it is safe to blacklist all Pycom LTD devices.
ATTRS{idVendor}=="04d8", ENV{ID_MM_DEVICE_IGNORE}="1"

and rebooting! (I probably forgot to do so late last night.)

I am not sure whether first upgrading the firmware of the Pysense or Pytrack board with sudo dfu-util is a necessary preceding step, but that is what I did first.

Anyhow, I filed a ModemManager bug report so that fellow Pycom developers on GNU/Linux will no longer be bothered with this issue in the future.

[jmarcelino]

@on4aa
Hi,

Thanks a lot for your investigation but I have to say 0x04d8 is Microchip's vendor ID (Pycom uses a Microchip PIC micro for the USB-serial interface and we sublicense their VID) so it's probably unwise to add it as a general rule for all ModemManager installs.

[Xykon]

@on4aa said in failed to set dtr/rts:

I could update the firmware of the Pysense & Pytrack boards, but still no luck with the ESP32 firmware.

$ sudo dfu-util -D pysense_0.0.8.dfu
$ sudo dfu-util -D pytrack_0.0.8.dfu

The sudo should be added to the documentation.

A better solution is to use sudo usermod -a -G dialout $USER once and then logout or reboot your PC. Then you can use dfu-util without sudo.

I will make sure this gets added to the documentation.

[on4aa]

@jmarcelino
Well, then a list of all of Pycom's current (and planned?) idProduct values is needed. See examples below.
Any future additions will have to be reported to freedesktop.org ModemManager maintainers.

[on4aa]

@xykon Oddly enough, I have been a member of the dialout group long before this. This is why it also surprised me.

Either the python script is not getting full privileges or I was not trained at the beginning with pressing the buttons. This needs more testing.

PS: A reputation point or so is more than welcome. As a newbee I have nada ;-)

[on4aa]

@jmarcelino The ModemManager bug report has been amended for the Pysense & Pytrack; which is all I have.

Can some good soul look up the idVendor and idProduct for the other boards (Expansionboard v1&2 etc.)?
Doing so allows the ModemManager maintainers to be correctly informed.

@xykon Today's new pycom_firmware_update_1.1.4.b1 GUI updater also works flawlessly!

PS: Reputation points, please, I have to wait 10 minutes between every post…

[jmarcelino]

@on4aa
Thanks a lot! That should cover all the current boards - the Expansion board (v1,v2) is based on the super popular FTDI USB-Serial chip - it's not PIC based - so it should have no problem.

I'll make a note to submit new IDs to ModemManager as new products arise.

[on4aa]

@jmarcelino Because of the Microchip VID sublicensing, it will be not always clear if Pycom products are being dealt with. For this reason, the ModemManager maintainer has added the Pysense and Pytrack rules to 77-mm-usb-serial-adapters-greylist.rules.

Neither is this bad, because ModemManager will try to make a connection only when run manually. Automatic annoyances will be a thing of the past over a month of 2­—3, when the ModemManager updates will roll into stable GNU/Linux releases.

[on4aa]

What	Removed	Added
Resolution	---	FIXED
Status	REOPENED	RESOLVED

Comment # 5 on bug 104320 from Aleksander Morgado

I've pushed the 2 blacklisted devices with rules including vid:pid, but I've
also added the whole vid to the "usb adapters greylist", which are only probed
if manually requested to do so, so should help to avoid interference with other
Microchip-vid-tagged devices.

https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=c2b956aefce495865cbdcb9971e2b3cd99cd0e99

All fine & dandy in the end…