Hi Javier,
I think it's a regression from the IOB rewrite.
The original implementation added the timestamp before calling either
devif_conn_event or can_data_event.
https://github.com/apache/nuttx/blob/55d9e5f7af05e75ca62f57863b880d723aa83c56/net/can/can_callback.c#L123-136
I think moving the c
Hi Nuttxaddicts,
After configuring the CAN socket with SO_TIMESTAMP, the application reading
the socket is sometimes getting an empty timestamp in some situations. I've
been debugging this issue and I this is what I found:
There are two paths when receiving a CAN frame from the interrupt, if ther
