Hi,
We are using the FTL driver over a MTD device (flash memory at45db641e).
When we write something to flash, eventually the ftl_flush function is
called and it does an erase (MTD_ERASE) and then the write (MTD_BWRITE).
But in the at45db driver (at45db.c) the write uses command 0x82 ("Main
Memory
outube.com/user/MyGeotab> | LinkedIn
<https://www.linkedin.com/company/geotab/>
On Mon, Mar 24, 2025 at 9:49 AM Javier Casas Marin
wrote:
>
> In AT45DB161D chip, the Opcode 82H = Main Memory Page Program Through
> Buffer *also performs a built-in erase.*
>
> From the datas
In AT45DB161D chip, the Opcode 82H = Main Memory Page Program Through
Buffer *also performs a built-in erase.*
>From the datasheet, section 7.8:
"This operation is a combination of the Buffer Write and Buffer to Main
Memory Page Program with Built-in Erase operations."
So the double erases are al
ssion.
>
> Feel free to send in a PR I'll review it.
>
> Yours sincerely,
>
> Peter van der Perk
>
> -Original Message-
> From: Javier Casas Marin
> Sent: Thursday, March 6, 2025 5:25 PM
> To: dev@nuttx.apache.org
> Subject: Re: Re: socket CAN timestamp mi
sincerely,
>
> Peter van der Perk
>
> -Original Message-
> From: Javier Casas Marin
> Sent: Thursday, March 6, 2025 2:59 PM
> To: dev@nuttx.apache.org
> Subject: Re: socket CAN timestamp missing
>
> Caution: This is an external email. Please take care when clicking
f57863b880d723aa83c56/net/can/can_callback.c#L123-136
>
> I think moving the code up would fix it.
>
> Yours sincerely,
>
> Peter van der Perk
>
> -Original Message-
> From: Javier Casas Marin
> Sent: Wednesday, March 5, 2025 2:27 PM
> To: dev@nuttx.apache.org
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
Hi,
I'm implementing the CAN statistics in Nuttx but I have some doubts about
where to increase the drop counter. The data that is not accepted by the
application is handled in the `can_datahandler` function. As the function
documentation says, this function may be called either from the data
rece
