MicroPython Forum (Archive)

@pythoncoder Very fair point, and the wiki would make more sense. It is unfortunate that the documentation, forums, and wiki are not always the easiest to search, but it could easily be argued that eventually any body of knowledge gets hard to keep track of and fully utilize. I am also guilty of not...

You are correct, I was worried when cross compiling did not benefit me at all, and bytes objects alone did not help. Then I realized that of course it is optimization during when freezing and building the firmware. Your libraries also noted and confirmed this. One downside of the forums is that valu...

I was able to use the same method as Peter to minimally use RAM and read binary information from flash using bytes object in a python source file. Similar I also have asset build scripts. It is an extra step with including assets in DFU build, but luckily assets do not change too often and I can use...

I am working now to utilize something that @pythoncoder did for his font utilities. I realize one thing I did wrong when evaluating is the difference between cross compiling and actually freezing the code into the DFU. https://github.com/peterhinch/micropython-font-to-py Hopefully this yield better ...

Sorry I meant external RAM, this is what the chip that actually uses the bitmap and font data reads from. The micropython based device is really just providing assets and commands over SPI. I cannot easily get around writing to the external device. My main issue is not so much taking up space in fla...

When doing some testing with just cross compiled modules I do get the size significantly smaller, but the import does seem to live in RAM. I have tried to "del" the module but I never could get that to work and free up memory. Luckily I am using the F7 chip right now and have about 307k RAM free bef...

I am trying to store raw binary data efficiently but in a way that is easy to compile into my DFU for bootloading. The data can and will change frequently enough that it should be treated almost like application source code. It will hold font and bitmap information. My current implementation is stor...

Thank you for clarifying, and that makes a lot of sense. I knew that only a certain portion of the sector could be used but did not realize that it could not jump over that, which now seems obvious. It also makes sense now why I kept seeing the additional filesystem segment, and why it was typically...

It would seem that even when trying to utilize the 128k DTCM RAM and a max sector size of 128k, it does not seem to utilize more than 64k. I am wondering if there is somewhere else that is limiting what is usable in each sector. What I used for testing but it did not appear to provide more space tha...

Okay I think this is making more sense now. #elif defined(STM32F746xx) || defined(STM32F765xx) || defined(STM32F767xx) || defined(STM32F769xx) // The STM32F746 doesn't really have CCRAM, so we use the 64K DTCM for this. #define CACHE_MEM_START_ADDR (0x20000000) // DTCM data RAM, 64k #define FLASH_SE...