Skip to content

Conversation

@laurensvalk
Copy link
Member

This was missed in 65d5196 when upgrading MicroPython. This would lead to programs being copied to RAM before running. How it was found: If all slots were full, then the program would not run as there would not be enough heap to load yet another program.

Also, MicroPython has a hardcoded test for mp_reader_mem_readbyte in mp_reader_try_read_rom, so it would ignore our reader even with MICROPY_VFS_ROM enabled.

Fixes pybricks/support#2382

This was missed in 65d5196 when upgrading MicroPython. This would lead to programs being copied to RAM before running. How it was found: If all slots were full, then the program would not run as there would not be enough heap to load yet another program.

Also, MicroPython has a hardcoded test for mp_reader_mem_readbyte in mp_reader_try_read_rom, so it would ignore our reader even with MICROPY_VFS_ROM enabled.

Fixes pybricks/support#2382
@coveralls
Copy link

Coverage Status

coverage: 59.794%. remained the same
when pulling 560988e on work
into 4cc7241 on master.

@laurensvalk laurensvalk merged commit 560988e into master Oct 8, 2025
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] mpy appears copied, not run from RAM storage

4 participants