I have built wxWidgets-3.0.0 and usbpicprog-0.6.0 on my fedora 20 system. usbpicprog starts and displays the default PIC2550 device. All good so far.
When I insert my usbpicprog hardware my /var/log/messages shows:
May 6 12:30:36 corona kernel: [18651.387514] usb 2-5: new full-speed USB device number 8 using ohci-pci
May 6 12:30:36 corona kernel: usb 2-5: new full-speed USB device number 8 using ohci-pci
May 6 12:30:36 corona kernel: [18651.586487] usb 2-5: New USB device found, idVendor=04d8, idProduct=000e
May 6 12:30:36 corona kernel: [18651.586499] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 6 12:30:36 corona kernel: [18651.586507] usb 2-5: Product: usbpicprog.org
May 6 12:30:36 corona kernel: [18651.586512] usb 2-5: Manufacturer: usbpicprog.org
May 6 12:30:36 corona kernel: usb 2-5: New USB device found, idVendor=04d8, idProduct=000e
May 6 12:30:36 corona kernel: usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 6 12:30:36 corona kernel: usb 2-5: Product: usbpicprog.org
May 6 12:30:36 corona kernel: usb 2-5: Manufacturer: usbpicprog.org
May 6 12:30:36 corona mtp-probe: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:02.0/usb2/2-5"
May 6 12:30:36 corona mtp-probe: bus: 2, device: 8 was not an MTP device
So the usbpicprog hardware is being detected by the kernel. Again everything is good.
The problem then follows when systemd attempts to activate a service to manage the newly inserted device:
May 6 12:30:42 corona dbus-daemon: dbus[692]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
May 6 12:30:42 corona dbus-daemon: dbus[692]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
I don't believe the 26-microchip.rules is applicable to systemd-managed Linux like fedora. As a result, the usbpicprog program does not detect the hardware and issues a "Programmer not connected" dialog when the IO Test is attempted.
Has anyone overcome this problem?
Regards,
Neil Darlow
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As a first try you could run usbpicprog as root (sudo).
Then you do indeed have to make some udev rules that are compatible with udev, I will have a look for you on how to do this, but I can't test it.
Frans
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK. some progress. I silenced the dbus-daemon errors by enabling the ModemManager service for systemd.
The problem seems to be that ModemManager is really designed for mobile device modems and does not have a plugin suitable for communicating with usbpicprog.
Bypassing systemd somehow will have to be the solution.
Regards,
Neil Darlow
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The default 26-microchip.rules are good. I ran usbpicprog as root and it worked. I needed to add my user to the plugdev group after which the usbpicprog hardware was detected. At least I learned what was necessary to silence the systemd/dbus noise in the process.
Thank you for your patience.
Regards,
Neil Darlow
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have built wxWidgets-3.0.0 and usbpicprog-0.6.0 on my fedora 20 system. usbpicprog starts and displays the default PIC2550 device. All good so far.
When I insert my usbpicprog hardware my /var/log/messages shows:
May 6 12:30:36 corona kernel: [18651.387514] usb 2-5: new full-speed USB device number 8 using ohci-pci
May 6 12:30:36 corona kernel: usb 2-5: new full-speed USB device number 8 using ohci-pci
May 6 12:30:36 corona kernel: [18651.586487] usb 2-5: New USB device found, idVendor=04d8, idProduct=000e
May 6 12:30:36 corona kernel: [18651.586499] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 6 12:30:36 corona kernel: [18651.586507] usb 2-5: Product: usbpicprog.org
May 6 12:30:36 corona kernel: [18651.586512] usb 2-5: Manufacturer: usbpicprog.org
May 6 12:30:36 corona kernel: usb 2-5: New USB device found, idVendor=04d8, idProduct=000e
May 6 12:30:36 corona kernel: usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 6 12:30:36 corona kernel: usb 2-5: Product: usbpicprog.org
May 6 12:30:36 corona kernel: usb 2-5: Manufacturer: usbpicprog.org
May 6 12:30:36 corona mtp-probe: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:02.0/usb2/2-5"
May 6 12:30:36 corona mtp-probe: bus: 2, device: 8 was not an MTP device
So the usbpicprog hardware is being detected by the kernel. Again everything is good.
The problem then follows when systemd attempts to activate a service to manage the newly inserted device:
May 6 12:30:42 corona dbus-daemon: dbus[692]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
May 6 12:30:42 corona dbus-daemon: dbus[692]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
I don't believe the 26-microchip.rules is applicable to systemd-managed Linux like fedora. As a result, the usbpicprog program does not detect the hardware and issues a "Programmer not connected" dialog when the IO Test is attempted.
Has anyone overcome this problem?
Regards,
Neil Darlow
Dear Neil Darlow,
As a first try you could run usbpicprog as root (sudo).
Then you do indeed have to make some udev rules that are compatible with udev, I will have a look for you on how to do this, but I can't test it.
Frans
OK. some progress. I silenced the dbus-daemon errors by enabling the ModemManager service for systemd.
The problem seems to be that ModemManager is really designed for mobile device modems and does not have a plugin suitable for communicating with usbpicprog.
Bypassing systemd somehow will have to be the solution.
Regards,
Neil Darlow
The default 26-microchip.rules are good. I ran usbpicprog as root and it worked. I needed to add my user to the plugdev group after which the usbpicprog hardware was detected. At least I learned what was necessary to silence the systemd/dbus noise in the process.
Thank you for your patience.
Regards,
Neil Darlow