MicroPython Forum

After some more debugging we realized that this object contains pointers to previously allocated object and the next object in line - but when the object is removed from the list its "prev" and "next" pointers are not zeroed - this implementation is in the external library. Sinc...

@Capstan: are you using pre-built firmware from micropython.org/download, or are you compiling it yourself?

This issues has been fixed in the latest version of the code.

When a script finishes (either it runs to the end or has an uncaught exception) then the MicroPython runtime will go to the REPL. If you want to catch any exception and handle that (eg reset the device) then do as suggested above, run your outer-most code in a try/except block, and do the error hand...

2. Something I wanted to ask for a long time: Damien , why did you decide to write parser in such way, as LR(n) automaton at all? Did you consider LL(n=~1), recursive-descent parser? The parser/compile was the very first thing I wrote and it was a while ago and I don't remember the details of my de...

Yes, this problem was discovered recently by others and has been solved in the most recent version of the firmware code. The problem was that Windows 10 (the Creators update) changed the way it queried USB mass storage devices (like USB flash drives), and it now sends a "SCSI cache synchronize&...

If you are compiling from a vstr (paste mode) then you will need to have enough heap available for the entire script. Much less heap memory is needed if you instead compile from some other source, eg from a file. In the case of compiling from a file, characters that are fed into the lexer are read o...

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.

Thanks for the report, but in this case I'd say it's better to require the individual board config to define MICROPY_HW_FLASH_LATENCY. Otherwise the main code has too many automagic configuration selections.

Building with cygwin has some difficulties, like: 1) symlinks don't work in cygwin; 2) command-line lengths can overflow; 3) any "strange" characters (eg parenthesis) in path/filenames might break the build. The lcd160cr.py error is related to symlinks not working. The best option is to in...