MicroPython Forum (Archive)

My boot.py file contained the line: pyb.usb_mode('VCP') i.e., only the virtual serial port. My understanding was that was recommended(?) for rshell/rsync(?) but I can't recall for sure why I switched to that. I just now changed it to: pyb.usb_mode('VCP+MSC') ...and I can copy files manually using a ...

Yes, listing the files on /flash is how I got the 54K number. Also even though I can fix it by re-writing the firmware and doing a mass-erase, I recently had the issue start again after just using rshell a couple of times to tweak one or two files w/o changing their size signficantly. I'll try an SD...

And I assume FAT, whatever the default is.

Yes, the one on github by dhylands. Version 1.1 pyboard, latest firmware (1.12).

rsync displays a message "timed out or error in transfer to remote" message when I attempt to update files on /flash. I have about 10 or so total *.py files that potentially could be updated. It often gets 2 or 3 or more copied but then it bombs. This symptom has only recently cropped up (as in the ...

Those 3 numbers are all I'm looking for. Thanks

I have been using mem_info() to look at memory usage, but that prints to the USB connection. Is there a way to access the same info from within my code?

So my code for a pyboard v1.1 has been growing bigger and bigger. I have a class defined that deals with external SPI flash memory, so naturally it has a lot of attributes and methods in it. Its code size is "gigantic" relative to all other classes I have defined for other uses. Today I added yet an...

Thanks, I'll use your flag suggestion.

I am using the <schedule> method to make an interrupt append an "event number" to a list. Works fine, no problem. My question is when I later on in the top-level code pop an event number off this "stack" do I need to globally disable/re-enable interrupts while I do this? I am suspecting that I don't...