At the end it works. Things to know: - only the release 4.2 informs that we have to configure as 'unicore'... but once the config done, it works even with esp-idf 4.1 - the error message about the wrong crystal frequency has to be ignored. - the max accepted baudrate is 115200. The default 460kb doe...

New test: if we lower the baud rate (115200Hz), we can program the 'Hellow World' program but the execution fails within the 'RTC calibration'...
We are now wondering whether the crystal is really @38MHz.

We manufactured some boards based on the ESP32-MINI-1 module. When we try to program them, we get the following error: <<A fatal error occurred: Timed out waiting for packet header>>. A strange warning message is: WARNING: Detected crystal freq 38.36MHz is quite different to normalized freq 40MHz. U...

Found out the source of the problem: there is a conditional statement
#ifdef USE_CLASS_B_NET
....
in add_offer_options (dhcpserver.c) that forces the subnet mask what ever the value defined in ip_info.

Modifying this par allows to use the specified subnet mask.

Hello,
I need to set a netmask == (255,255,0,0) in AP mode. The initialization is ok, and if I read back the current netmask, it is correct (255,255,0,0). But when I connect a WiFi client, it gets (255,255,255,0) as netmask. Any idea to workaround this problem?
Thanks,
Francis

Sorry for the very long delay. Yes, the code is working fine. What you need to do: 1. Assign for the length a multiple of 64 bit. For example, if you are supposed to receive 80 clocks, write 128 into the registers. 2. After get the N clocks from your 'master', complement virtuatually up to 128 (see ...

Thanks for your answer. It seems that the problem was not at the ESP32 side (master) but within the slave device...
Everything works fine with the ESP32! Issue is closed.
Francis

We made some boards with ESP32 + I2C device. We tested our firmware on 20 prototypes without encountering any problem. We launched this week a first production, and tested the final boards...and we are now encountering some strange problems with I2C communication (master with a close single slave): ...

Hello, The situation looks quite confusing: do we have to connect an external 32,768 oscillator onto 32K_XN or 32K_XP? The 'menuconfig' options still looks in conflict with the hardware guidelines document.. In this case (external oscillator connected to the right pin), is the other pin available as...

I found a workaround for the 'last byte issue: I generate internally dummy clock pulses to push the last 32 bit word to the DMA: ret = spi_slave_simple_transmit_dma ( host, trans_desc); for ( i = 0; i < ticks_to_wait; i++) { vTaskDelay(1); if ( spihost[host]->hw->slave.trans_done ) break; //Manage E...