@robert-hh Many thanks for this detailed analysis and testing. The results are promising, based on your tests and also information from others I think it is clear that enabling wear-leveling does not have any significant negative effect.

Finally, my problem is Solved : With pygate, no need to register the device EUI, just create one from scratch ! (and edit config.json accordingly) as the doc says

See my Teensy 3.x/4.0 CoreMark, Temperature and Power Benchmark. With a simple black aluminium heatsink from Raspberry Pi the MCU temperturare of the Teensy 4.0 is up to 15 C lower. Other solution is to cover the case/box with reflective surface. I've had experienced 20-30 C lower temperature.

Hi, again. I have update 10 wipy and 2 gpy with the latest fw (1.20.2.rc6). With this fw I'm getting Guru Meditation Error. Some times the pycom became freeze on the Guru Meditation Error. Guru Meditation Error: Core 1 panic'ed (InstrFetchProhibited). Exception was unhandled. Core 1 register dump: PC : 0x3ffb624c PS : 0x00060630 A0 : 0x80095188 A1 : 0x3ffdcc00 A2 : 0x3ffb61dc A3 : 0x00060620 A4 : 0x3ffdabe8 A5 : 0x00000001 A6 : 0x000000fe A7 : 0x00000001 A8 : 0x800947bc A9 : 0x3ffdcbf0 A10 : 0x00000000 A11 : 0x3ffc9509 A12 : 0x00060620 A13 : 0x00000001 A14 : 0x000000fe A15 : 0x3ffb61dc SAR : 0x00000000 EXCCAUSE: 0x00000014 EXCVADDR: 0x3ffb624c LBEG : 0x40091ad4 LEND : 0x40091b02 LCOUNT : 0xffffffff ELF file SHA256: ets Jun 8 2016 00:22:57 But most of the times the guru meditation error do a core dump, and the cpu reset. Guru Meditation Error: Core 1 panic'ed (StoreProhibited). Exception was unhandled. Core 1 register dump: PC : 0x40096c29 PS : 0x00060533 A0 : 0x80095107 A1 : 0x3ffdcc00 A2 : 0x3ffb61ec A3 : 0x00060520 A4 : 0x3ffdabe8 A5 : 0x00000001 A6 : 0x000000fe A7 : 0x00000001 A8 : 0x3ffb6210 A9 : 0x3ffb61fc A10 : 0x00000001 A11 : 0x0000abab A12 : 0x3ffdabe8 A13 : 0x00000001 A14 : 0x000000fe A15 : 0x3ffb61e4 SAR : 0x00000000 EXCCAUSE: 0x0000001d EXCVADDR: 0x00000009 LBEG : 0x40091ad4 LEND : 0x40091b02 LCOUNT : 0xffffffff ELF file SHA256: 0000000000000000000000000000000000000000000000000000000000000000 Backtrace: 0x40096c29:0x3ffdcc00 0x40095104:0x3ffdcc20 0x400f31b8:0x3ffdcc40 0x400e0715:0x3ffdccd0 ================= CORE DUMP START ================= This guru meditations are random. Can happen on the first 5 min or after 5 days.

@jc_serg If you are looking for a ping.py script: there is one here: https://gist.github.com/91cc8979e33e82af6d99ec34c38195fb.git

@jc_serg That looks bad then. Since 3.3V is an output of the board, it means that the board is not working. Are you sure you plugged in the board in the right orientation?

well, right now I only have access to win10. Is there any solution for windows 10?

@paul-thornton Just did. :)

@robert-hh thanks. ill try and sort out some VM's and give that ago.

@robert-hh Es läuft jetzt. Ds Update ging nicht weil ich das Board für den Fipy überbrückt habe das es im batterie Modus läuft. nach entfernen des kabels ging auch das Update. Jetzt kann es weiter gehen. Danke für deine Mithilfe.

@brewnut The RTS pin is not used by the firmware, but driven by the UAB/UART bridge. But you can also use another pin, like P6.

@robert-hh Thanks, I'll try that.

@ldbm we don't publish schematics of our products, sorry.

@mci For coding the content of the pins.csv file is effective, because that file is used for mapping the Pxx and Gxx numbers to the GPIO port numbers,

@eric-waai Yes it was a typo I have 3 i2c devices

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