PySense not recognised as DFU device

[philwilkinson]

Very similar problem to that previously discussed on the PyTrack
Re: PyTrack not recognised as DFU device
The thread for the PyTrack did not seem to find a resolution.

I am using a RasPi3 and trying to upgrade the firmware on my PySense to pysense_0.0.8.dfu.
On initially connecting the PySense to the RasPi I ran
dmesg | grep ttyUSB
and it picked up the PySense

I then followed the instructions on the Pycom website. Reconnecting the PySense with the button pressed; wait for 1 second, then release and then ran
dfu-util -D pysense_0.0.8.dfu

this returned

dfu-util 0.8

Match vendor ID from file: 04d8
Match product ID from file: f011
dfu-util: Cannot open DFU device 04d8:f011
dfu-util: No DFU capable USB device available

the previous thread had some discussion about drivers. I am supposed to install something to allow me to upgrade the firmware?

[Ali Bakir]

@jmarcelino Thank, with sudo It works !!

[Tombee]

Just received Pysense 1718001136 from Digikey today and connected LoPy 1711004932.
Identical problem with dfu-util not recognizing the Pysense.
Installed on Windows10 the driver using Zadig and selected libusbK as the driver. Successful.
opened Cmd window and ran dfu-util -D pysense_0.0.8.dfu
the identical 5 line response as above.

F:\Development\LoPy>dfu-util-static.exe -D pysense_0.0.8.dfu
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Match vendor ID from file: 04d8
Match product ID from file: f011
Cannot open DFU device 04d8:f011
No DFU capable USB device available

I loaded Atom 1.23.3 x64 and it won't connect with 192.168.4.1 - Connection error: Error: Login timed out

I was able to connect to LoPy through the Pysense USB using Tera-Term on Com11 and run micropython.

Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:2
load:0x3fff9010,len:8
load:0x3fff9018,len:812
ho 0 tail 12 room 4
load:0x40078000,len:3692
load:0x4009f000,len:944
entry 0x4009f1f0
rtc v134 Oct 20 2016 12:36:18
XTAL 40M
I (818) phy: phy_version: 246, Nov 18 2016, 17:30:07, 0, 0

tcpip_task_hdlxxx : 3ffe800c, prio:18,stack:2048
frc2_timer_task_hdl:3ffe9a24, prio:22, stack:2048
I (1514) wifi: pp_task_hdl : 3ffec27c, prio:23, stack:8192
mode : softAP(24:0a:c4:02:5b:bd)
dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)
MicroPython v1.8.6-237-g9d21f17 on 2016-12-15; LoPy with ESP32

I noticed that the Zadig driver indicates the USB-ID is 04D8 F012 - Not the F011 that dfu is looking for.

What next?

[regines]

@jmarcelino No, this line doesn't show up here. I only get the first two plus the fourth line.

[jmarcelino]

@regines
Are also seeing “dfu-util: Cannot open DFU device 04d8:f011”?

[regines]

I'm having the same problem but for me using sudo doesn't help.

[philwilkinson]

Oh yes, that would be a good idea...!
Sorry about that. Rather basic error. Apologies but thanks @jmarcelino for responsing.
Phil

[jmarcelino]

@philwilkinson
Sounds like a permissions problem, you probably need to run dfu-util with sudo.

sudo dfu-util -D pysense_0.0.8.dfu

should work after you enter your password.