When operating the respective development sandbox on LinuxOnWindows, @clemens experienced different kinds of flaky behavior, specifically with board communication stability. Mostly, the issues are manifesting as different kinds of timeout errors, most probably caused by inadvertently resetting the MCU during communication.
@tonke also was able to confirm the same erratic timeout behavior on Win10 altogether - even without WSL.
"make recycle" freezes
Windows 10 native and WSL
c:\Program Files (x86)\Pycom\Pycom Firmware Update>pycom-fwtool-cli.exe -v -p COM5 flash -t c:\temp\FiPy-1.20.0.rc9.tar.gz Running in PIC mode Product ID: 19 HW Version: 3 FW Version: 0.0.8 Connecting.... Uploading stub... Running stub... Stub running... Changing baud rate to 921600 Changed. Erasing 256 KiB at address 0x00001000 Erasing 256 KiB at address 0x00041000 Erasing 256 KiB at address 0x00081000 Erasing 256 KiB at address 0x000C1000 Erasing 256 KiB at address 0x00101000 Erasing 256 KiB at address 0x00141000 Erasing 256 KiB at address 0x00181000 Erasing 256 KiB at address 0x001C1000 Auto-detected Flash size: 8MB0 Flash params set to 0x023f Compressed 21456 bytes to 14957... Flash params set to 0x023f 0x00001000... (100 %) Compressed 21456 bytes to 14957... Flash params set to 0x023f Compressed 21456 bytes to 14957...
Exception: Write timeout
We started to investigate the issue and found out that other people also have become frustrated by this or similar problems.
So, we recognize running the development sandbox on LinuxOnWindows might not be the very best choice yet and will require more polishing. In the meanwhile, we will probably discourage the native usage of Win10 for running the development sandbox.
However, we will test whether programming the device through a VirtualBox machine running Debian works flawlessly.