Using the promiscuous callback, I can sniff on beacon frames and I get the beacon timestamp (at +24 offset) as expected: ... I (35263) ESPNOW_REC: Beacon timestamp 17893982617990 (rx = 35260724, diff = 17893947357266) I (35468) ESPNOW_REC: Beacon timestamp 17893982822802 (rx = 35465537, diff = 17893...

In the Wifi stack, why, oh why, is the timestamp in rx_ctrl.timestamp not set with esp_timer_get_time(), so that the received message can be related to other stuff happening in the app?? It is based on a APB timer but not esp_timer_get_time().

Using the WiFi promiscuous callback (for beacon/probe) I can see that the relation between the TSF and the rx_ctrl.timestamp is very stable, so with that, I can deduce a difference between those and then use the TSF value to start a secondary (APB based) usec timer which has (very close to) the same...

Just a thought: The polarity of the bit clock, making the sampling of the data line on the "wrong" edge?

Already tried that, and it doesn't cut it. I need the *same* timer as that used for the wifi_pkt_rx_ctrl_t.timestamp field, or a similar APB based timer within microseconds.

Let me ask the digital team; will get back to you. Edit: I asked: the PTP uses the internal 80MHz APB clock as a clock source for a 64-bit counter. Can't tell why you can't get anything working out of it, though. I am at the same position, almost 5 years (!!!) later. So basically I am trying to do ...

The ESP-NOW timestamp in the esp_now_recv_info struct is 32 bit (usec resolution). How is this timestamp related to the TSF counter of the WiFi interface? ESP-NOW comes without any sources so there's no way to check how the timestamp is acquired. I need to be able to create a timestamp in the same m...

I need to nudge the rate +/- 2% roughly, is it possible to do this? Using an ESP32-S3.

Ok, so I changed the clock setting macro from I2S_PDM_TX_CLK_DEFAULT_CONFIG to I2S_PDM_TX_CLK_DAC_DEFAULT_CONFIG, and then I get: I (21542) i2s_cb: Min interval (us): 2660 I (21542) i2s_cb: Max interval (us): 2665 I (21542) i2s_cb: Avg interval (us): 2662 I (22562) i2s_cb: Min interval (us): 2658 I ...

To send or receive data asynchronously, callbacks can be registered by i2s_channel_register_event_callback(). Users are able to access the DMA buffer directly in the callback function instead of transmitting or receiving by the two blocking functions. Yes, got this working, but I cannot even call m...