@sandipg Make sure you have the device in DFU mode...
I tryied this many times sometimes It took me like 10 try to get the code in... also make sure you are in the right folder but it looks like you are in the right folder...
Using DFU-util with Pytrack and Pysense
In order to put Pyrack or Pysense in DFU mode, press and hold the button on the Pytrack/Pysense board whilst powering on the board (connecting the USB cable).
Press the button and keep it held
Next plug-in the USB cable to the host computer and wait 1 second before releasing the button.
After this you will have approximately 7 seconds to run the DFU-util tool. -> This step you might have to do many times for it to work...
@seb Ok, Thank you for the prompt reply. Is there any easy way to find the know problems of a certain board and when it is sheduled to be fixed? Will there be an easy way to find the firmware file?
I would be very helpfull if you could reply here if the new firmware is available and post a direct download link for the firmware file. So people who find this problem in the forum (because they might have the same issue) get the solution right away.
only the firmware :-)
I did not touch anything in my code because I was pretty sure it was working as is.
Now I am patiently waiting for the death (hope not) of two WiPy 3 with the very latest firmware that are running since 47 hours.
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 firstname.lastname@example.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
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.
Hi @xykon thanks for the info and quick response :-) ...
I've not really studied udev rules on my Linux mint machines. However adding dialout did not effect the behavior of 'cutecom'.
Changing the read write permissions on the USB device survives reboot. I'm sure if I have a different device take USB0 then I will be stuck again.
Any info on how files are copied to and from the device or is anyone in the community looking at a plugin for pycharm?
That's correct, the ack will only be sent with the next uplink
Where is a gotcha (at least it was to me): once the data is received, typically LoPy goes to deepsleep. Once it does, it forgets the previous session and starts the new one without confirmation.
Indeed this was a problem, but from the upcoming firmware release on it won't - we now save the pending ack status of downlinks as well when using nvram_save(), so if you use nvram_restore after restarting from deepsleep the LoPy will know to send the acknowledgement with the next uplink.
This is already in our internal code and will be public on the next release.
You can get the wake reason using ds.get_wake_status().
I think the default is that there are no other wake-up sources configured, but you may try to disable_wake_on_fall(['P10','P17', 'P18']) and disable_wake_on_raise(['P10','P17', 'P18']) just to be sure.