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.
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 email@example.com
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
mode:QIO, clock div:2
ho 0 tail 12 room 4
rtc v134 Oct 20 2016 12:36:18
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.
@marto Hi thanks for pointing that you, you are correct the updater tool only shows instructions for the expansion board at the moment. I have passed this on and it should hopefully be changed soon. I will now remove the text about carefully reading the updater instructions because that clearly caused confusion.
I will also pass on your OS details so make sure it gets investigated at the same time as the Mac OS issues.
@robert-hh hello robert, thanks for all the great help - it's really awesome!!
I managed to figure out, when booting in safe mode - that i can temporarily connect via ftp again (because the boot.py is bypassed).. and thus make changes to the boot.py.
soo.. the thing is though, that it seems the lopy does not care AT ALL about what I put into the boot.py script now, even after unplugging the short between G28 and 3v (which I assume should make it go back to loading boot and main).
tinkering more about, it turned out I had to set the heartbeat to false in order to use the rgbled onboard the lopy. well done soren. anyway, it is indeed responding now, but setting up the thing with custom wlan configuration is really difficult. this topic has become pretty messy. I tried to change the topic name, but got a message that i couldn't.. it is pretty misleading atm. are there any admins on here?