MicroPython Forum (Archive)

Hi!
I am working on a custom board based on the stm32f405 and a SPI flash. Everything was working great.
After upgrading to the windows 10 creator update a few weeks ago I've encountered some issues, wondering if anyone else is experiencing this. It manifests across multiple computers, and doesn't happen at all on PCs without the creators update or on windows 7.

Issue 1. When plugging in the board, there is no trace of the mass storage device. After 5 minutes or so, repeatably, it shows up.

Issue 2. The REPL locks up randomly and displays no new information, although control-D and control-C commands can still be sent successfully, presumably all inputs work as well. This is tested across multiple terminal emulators. Restarting the terminal emulator seems to fix this. This problem seems to go away after the board has been plugged in for a few hours.

Any ideas or similar experience?

I am seeing the delay in drive letter issue, but have no issue with REPL.

These problems are common across all three of my pyboards (v1.0, V1.0 LITE and v1.1)

[quote="Neil"]I am seeing the delay in drive letter issue, but have no issue with REPL.

These problems are common across all three of my pyboards (v1.0, V1.0 LITE and v1.1)[/quote]


Thanks for confirming this. It's been driving me a bit crazy. I suspect it is caused by the new windows feature of supporting partitions on USB mass storage drives.

Hi, all OpenMV Cam boards are suffering from this issue too. Not sure what to do about this...

Does anyone have a microbit (or any generic mbed-enabled board) that they could try with Windows Creator? It has a USB MSC and knowing if it worked or not would help work out where the issue lies.

[quote="Damien"]Does anyone have a microbit (or any generic mbed-enabled board) that they could try with Windows Creator? It has a USB MSC and knowing if it worked or not would help work out where the issue lies.[/quote]
I tried MSC in my msp430f6638 launchpad(designed by myself), it works well.

Hi Damien,

A Freescale KL27 board works fine. So does the embedded ST-LINK on an L476 Discovery board. Both install VCP and MSC correctly.

Problem seems to be only with Micropython. Com port is also unreliable. Sometimes usbser driver fails. I tried changing boot.py to VCP and HID. Now after resetting the filesystem the pyboard randomly appears in device manager as COM5 & MSC or COM13 and HID when unplugged and plugged in again.

I am setting up USBlyser on an Anniversary and Creator systems and will compare and post the results​, probably this weekend.

Same problem with me,I use a custom board by me based on STM32F405.

And the board is still work fine with other computer that didn't install creator update.

This has been fixed here.
https://github.com/micropython/micropyt ... -306066109

You can either merge Damien's PR or wait until it is released into mainline.

This is great, I'm glad it's been fixed, thanks.