Dear Pycom community!
We're happy to announce the release of stable version 1.20.2
The most important changes are:
Add support for EU433 region
Improve support for different firmware "types" (Pybytes, Pymesh, Pygate)
LTE: add PSM Power Saving Mode
IDF recompiled with v98 compiler
Ctrl-D works if pybytes is disabled (pycom.pybytes_on_boot(False))
update.py supports additional pybytes options
Sigfox: finalizing certification RCZ1, 2, 4
BLE: Allow static passwords, remove bonded when pin changes
Support Sigfox registration for Pybytes
MDNS advertisement works
Adding libmdns.a to esp32/lib
Adding scripts for PyJTAG and short Readme
BLE characteristic update messages are lost if they sent too frequently
add bands=() parameter to lte.attach()
PYFW-391: Add changes needed for esp-idf v3.3.1
Functionally this is the same as the last Release Candidate 1.20.2.rc10. As usual, you can
install this update with the Firmware Updater
find the source code in branches v1.20 and Dev
download the firmware packages (.tar.gz) the docs
and find the .elf files in the github release
@Gijs My issue seems to be related to ethernet communication. I don't seem to have the same issue using wifi for communication (and power from POE). Have tried two different brands of switch (ubnt + cisco) with same results with eventual ethernet drop out.
I believe both switches saw the POE module as 10FDX if that makes any difference.
Is access to the DMA exposed in the API? If yes, could you provide an example?
I am specifically wanting to sample at 48KHz on a sweep across 4 ADC inputs for a communication application.
I have done it on the nrf52832 and 40 in C++ in the Arduino environment, and will be willing to beta test if you have a rough library.
ulab Samples is a repository with links, examples, benchmarks, etc, about ulab module, a NumPy-like array manipulation library for MicroPython and CircuitPython.
Most interesting is the ulab FFT benchmark for 1024 points, where you can see, among other boards, the performance of LoPy v1 and LoPy4 in single precision (SP/FP32) and double precision (DP/FP64). It would be similar to other ESP32 boards with mainline MicroPython v1.12 if the clock could be increased from 160 to 240 MHz. Notice that the performance of LoPy4 is 26% worse than LoPy v1 because the 4 MB of external PSRAM/SPIRAM (using QSPI bus) is slower than the 520 kB of internal RAM.
So it would be very useful to have Pycom MicroPython firmwares supporting 'machine.freq()' able to select the main clock frequency, like 40, 80, 160 and 240 MHz.
Thanks, I'll fix this! If you want to get involved, you can submit a Pull Request on our GitHub documentation repo! https://github.com/pycom/pycom-documentation
I know there are more errors and mistakes out there, just cannot get to all of them