@Thosch42 I'm working on this https://github.com/buzzware/pycom-docker-firmware-build I can't vouch for it being correct or the output being functional or running on Windows, but it does complete the build on my Mac.

@ingframin Did you manage to modify the firmware? I would like to have a Wi-Fi advertising per 100 milliseconds; default LoPy-4 seem to send an advertising only if requested by a station.

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 .

@geoff-white : guess we'll find out.

Hi there, we learned only recently that native code generation indeed would be coming to MicroPython for ESP32 [1]. After MicroPython 1.12 arrived a few weeks ago, this even became a real thing: The esp32 port has the following new features: native code generation [2] However, Pycom just upgraded to MicroPython 1.11 a few months ago so we will probably have to wait a bit to see the upgrade to MicroPython 1.12. With kind regards, Andreas. [1] https://community.hiveeyes.org/t/native-modules-in-micropython/2709/2 [2] https://github.com/micropython/micropython/releases/tag/v1.12

@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.

Dear @tanmay07 and @Martinnn, if you feel lucky, you might want to try our custom build just released on [1]. More background about this is available through [2]. Please be aware that when upgrading from a lower firmware version to this custom build based on 1.20.1.r1, you will have to erase your device completely before flashing in order to keep things straight. You will find respective references to this on the forum. Hint: Use pycom-fwtool-cli --port /dev/ttyUSB0 erase_all, see also [3]. With kind regards, Andreas. [1a] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/GPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [1b] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/FiPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [2] https://community.hiveeyes.org/t/investigating-random-core-panics-on-pycom-esp32-devices/2480 [3] https://community.hiveeyes.org/t/installing-the-recent-pycom-firmware-1-20-1-r1-requires-erasing-the-flash-memory-completely/2688

@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,