@jcaron Yes, and it works! Now I am trying to figure out where to put my module. In the ESP8266 version there is a file called ESP8266.ld which contains the list of C files. Where is the equivalent for ESP32? If there is no equivalent, what shall I look for?

I'm going to let someone who actually works at pycom answer licensing related questions other than pointing you at https://pycom.io/licensing/ . Hey @Paul-Thornton .

@peterson79 MicroPython.org does not support @micropython.native in the ESP32 port. It is supported for ESP8266 and STM32.

@fedesilvi Just to give you an impression how bad the esp32 ADC is, I collected 10000 samples with the ESP32 ADC and an ADS7818 ADC taking values the same LM385 voltage reference. The absolute values differ, because of the different ranges (5V vs. 3.3V). The histograms are below: Edit: Adding a 10 nF capacitor close to the ESP32 ADC input and switching off WiFi improved the picture. The one above was WITH the capacitor. Without, the capacitor, it was worse (avg +/-100 readings)

@martinnn lib_imu is a library that I wrote and in this function give only data from IMU and there aren't any delay. if I wrote data immediately on a file.txt in SD card it employ 0,2 s so the sample became 0,4. but if I collect data and insert them in a list to save data at the end of acquisition it gives me the error 'Memory allocation'.

@joseph I'm afraid I can't give you a timeline. The BT mesh is developed by Espressif, once they release it, we can start working on the implementation. We'll update the forum when we have a development version ready.

@protean As long as I tan into it, there are two main reason for unstable systems and two depending on the type of preoject. Python: You have to test all paths, so you will not run into typical python problems which you find only during runtime. i2c problems with the pycom extension boards. You have to run a lot of long time tests. Otherwise you may run into i2c exceptions. Maybe the deepsleep problem is related to this. Sometimes deepsleep does not go to sleep on my pytrack and so the device never wakes up and start your code again. But since 1.20.rc4 I have not run into this problem. memory fragmentation maybe a problem on larger projects. RAM is limitted. Especially on the old devices. So you cannnot code in the same way as on your PC. You have to keep in mind that the compiler, string and float methods will fragment your memory a lot. You can get around the compiler issue by using a cross compiler on the PC. For the remaining part you have to keep an eye on system. If it need huge buffers, allocate them on an eraly stage and reuse them instead of allocating new ones. Avoid floats and strings. Don't import somewhere during runtime. Import your needed modules in the same way as your huge buffers. some developers don't see the limits of the radio systems. There seems to be no feedback when they are too noisy and the radio submodule forces them to be silent. Sadly there is no option to log erros onto SD card. So it's hard to see, that most problems are related to typos, forgotten self. and memory fragmentation. I have seen a project which started to build a GC which was able to reorganize the allocated objects. Would be great to have these two features as an option in micopython.

@pedrofelipest said in nrf24l01: Please verify a) the intended connection as below CE on P6 -> GPIO27 CSN on P21 ->GPIO26 SCK on P22 ->GPIO25 MISO on P12 -> GPIO21 MOSI on P20 -> GPIO33 b) The semantics of the SPI method may be different between the poerts. Please compare the different ports (Pycom and micropython) by printing the results and self.buf content from write_register and read_register.

Hi @catalin Sorry I couldn't answer before. If the esp32 frequency is 160MHz the pysense timer works fine, it only has trouble when the frequency is changed. I am going to measure the error better to see if there is a clear relation between the frequency change and the timer error. Thanks,

@robert-hh This is not working well. During make skdconfig.h is replaced by make GENCONFIG (that is using wifi/scan/sdkconfig). The best is to modify that config. However moving the freq from 160 to 80 -> it saves only 7mA ... I expected to be more. So LoPY+shield with Wifi disable is consuming 35mA.

@dhblumenfeld1989 This cannot be the full script. At least a two lines are missing upfront, like: from network import WLAN wlan = WLAN(mode=WLAN.STA) And as a side note: The flash size you get with uos.getfree() is not relevant for memory errors. These are caused by RAM shortage. The size of free RAM is told by gc.mem_free(). And for all people trying to help it is useful to know the firmware version, which can be obtained by uos.uname().

@robert-hh Thanks I already know these aspects!