MicroPython Forum (Archive)

There is #define in mpconfigport.h I want to know the value of in my Python code. I know I can make a new C module to get access I want, but I was hoping there was some easier way.

kevinkk525 wrote: ↑

Mon Aug 26, 2019 2:21 pm

You are answering a 2 year old post...

Yup. Just because a thread hasn't been active for 2 years doesn't mean people don't read it. This particular thread has misleading information, and my reply directs people to the correct information.

Cool thanks for the update! I will investigate later why enabling the webrepl code makes a difference. I've gotta ask though, and sorry because I don't want to take away from the excellent work you've done tracking this down, but for the time you've invested in this, it's probably worth upgrading t...

I have committed a rollup of the changes I made into a fork in our micropython repo https://github.com/micropython/micropython/compare/master...ShrimpingIt:memorymax I attempted these changes to increase availability of storage for frozen modules and for availability of RAM as part of our Avatap pr...

I played around disabling some features I didn't need in mpconfigport.h and found several that, when disabled, allowed me to reclaim 8 bytes of BSS space each and found that commenting out the dupterm initialization code in main.c allowed me to gain back 32 bytes of BSS space. The big one to disable...

For others like myself who are unfamiliar with the terms text, data, and bss as they pertain to stack, heap, and general memory layout, here is a good Wikipedia page explaining the relationships: https://en.m.wikipedia.org/wiki/Data_segment

Thanks for the excellent explanation. Is this info in some hidden document or have you just surmised all of this through experimentation and code examination?

Sorry, my confusion came from two things. First, the documentation here mentions slots twice saying: MicroPython doesn’t maintain symbolic local environment, it is optimized to an array of slots Maybe the "slots" being referred to isn't the same as "__slots__"? Second, I incorrectly assumed the chan...

The speed in your putty config looks correct, but every time I've seen the writings of Cthulhu in a terminal when attempting a serial connection it was because I had the speed wrong.

I'm fairly sure the heap is fine tuned to match the available RAM of the target device, leaving enough space for stack, data, bss, etc. I'm less familiar with the non-STM32 ports (i.e. ESP*) which use an rtos. But I suspect the issues you're seeing are memory corruption (stack and bss) by overrunni...