MicroPython Forum (Archive)

Thank you very much Roberthh for your reply! That could indeed have been a problem, there is not too much space left for custom code. Fortunately, I checked that already before. Also, it appears in versions with binary size around 1.6M and around 1.9M. Most interestingly, it is always like that: the...

Update: There was a misunderstinge between the other person and me. So the binary that did produce the strange execution behaviour was actually compiled on a (third) different machine, which had the xtensa compiler version 1.22.0-80 installed. The versions that worked fine were built with 1.22.0-98,...

OK now I am lost and hopefully someone can put me in the right direction or has a hint about this. I compiled the untouched pycom 1.20.2.r6 with custom Python code under esp32/frozen/Custom. No submodules involved there. The version I compiled (Ubuntu Mate VM 21.10, GCC 11.2.0) shows the strange err...

Some new insights: Those erros can also occur after a freshly cloned pycom 1.20.2.r6 version without Bluetooth and CAN without any custom C code with frozen Python code but we also have compiled versions with 1.20.2.r6 that work without those errors. It does not seem to matter if Python code to be f...

Hi pythoncoder,

thanks for your fast reply! So do you think, that this might be more of a Pycom/ESP32 specific problem, than something that is related to Micropython itself?

Dear community, since a certain stage of commits in our development, we are facing strange errors: at seemingly random times, some of the try/except sections catch something like this: First type of error: Reason: unsupported types for __lt__: 'NoneType', 'int' Reason: unsupported types for __truedi...

Hi jimmo, thanks again a million for your suggestions and help! Yes, you are correct: I am using PyCom's MicroPython for my tests. I will try to test this again with a current version of MicroPython. I notice your code iterates from 0 to map->used -- unless they're ordered dicts, this won't work. Yo...

Hi jimmo, thank you very much for your reply! Yes, MicroPython is the one from the PyCom fork. I supposed that PyComs µPython version might not be very up to date...but it seemed to me that the issues I am facing rather come from a wrong approach on my side. dict to json should already be implemente...

Another update: I now skipped tabel entries, where table[ i ].key/value == NULL. Now I can repeat the key/value append test multiple times. This is what I observe: add new key value pair: JSON = {"key_string":"value1","test0":"value0"}. Key/Index Pointer of nested dict = NULL, index of nested dict m...

I did some additional tests. My original assumption was slightly wrong: The core dump seems to happen not when accessing the newly added key, but the one that got moved one in index higher. I printed out the addresses of the entries like this: for (int i = 0; i < map->used; i++) { printf("table entr...