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 also an issue with that chip when the FTL driver is used, so my questions remain the same. Thanks, Javier Casas Marín Geotab Senior Embedded Systems Developer Direct Toll-free Visit +34 900 535 371 www.geotab.com/es Twitter <https://twitter.com/geotab> | Facebook <https://www.facebook.com/Geotab> | YouTube <https://www.youtube.com/user/MyGeotab> | LinkedIn <https://www.linkedin.com/company/geotab/> On Sat, Mar 22, 2025 at 2:43 PM Dmitri Shilov <dshi...@cthru.xyz> wrote: > Hmm, I wonder if AT45DB161D does an undocumented erase, and the vendor > added additional opcode for at45db641e but did not change the behavour of > the old opcode (82H), just documented what actually happens? > > Regards, > Dmitri Shilov. > > > -------- Original Message -------- > On 2025-03-21 1:25 p.m., Lwazi Dube <lwa...@gmail.com> wrote: > > > The problem is your chip and not the driver :) > > > > The at45db driver was written for the AT45DB161D. > > Opcode 82H = Main Memory Page Program Through Buffer 1 > > > > For your chip (at45db641e) > > Opcode 82H = Main Memory Page Program through Buffer 1 with Built-In > Erase > > Opcode 02H = Main Memory Byte/Page Program through Buffer 1 without > > Built-In Erase > > >
