-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Memory Allocation Fail with Neo Trinkey #9088
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I reproduced this with 9.0.2 and 9.1.0-beta.0. I tried this recent change to MicroPython, which allows some compilation garbage to be collected more reliably: micropython#14136. But it didn't help. If I comment out the last four or so routines in If I use from TOS3 import * then the program works. So I think it is probably fragmentation from code compilation. This makes sense given that we removed long-lived objects in 9.0.0. @mrklingon So you could:
|
Super, thanks for the update. I’ll try the mpy route - I’ve never used that before! |
I'm impressed by what you've been able to squeeze onto this tiny board. You might consider an RP2040 Trinkey if you want more room. |
Thanks, I get a kick out of squeezing as much as possible out of The NeoTrinkey. I do have one of the rp2040s - but I really like the NeoTrinkey’s four pixels for output and two pads for input :) |
Thanks again! I tried mpy-cross and got it working! As silly as my project may seem, I appreciate getting it to work with current CP, and as a bonus learning to use mpy-cross!! |
Great! |
I am going to close this, but thank you for the report -- it helps us understand how much the change for 8.x to 9.x affected programs on small boards. |
CircuitPython version
Code/REPL
Behavior
MemoryError: memory allocation failed, allocating 1016 bytes
]0;🐍1@code.py MemoryError | 9.0.0\
Description
Code:
code.py: https://github.com/mrklingon/neotrinkey/blob/main/TOS3.py
Uses these modules:
https://github.com/mrklingon/neotrinkey/blob/main/morse.py
https://github.com/mrklingon/neotrinkey/blob/main/prt.py
Additional information
No response
The text was updated successfully, but these errors were encountered: