stbenn opened a new issue, #16170: URL: https://github.com/apache/nuttx/issues/16170
### Description I will limit this discussion to STM32 architecture, as I am not familiar with other architectures. I have been working on a progmem flash driver for the STM32H5, and noticed inconsistent terminology for "block" and "page" across other STM32 driver implementations (mainly `stm32h743xx_flash.c` and `arch/arm/src/stm32u5/stm32_flash.c`). A quick google search for the generally accepted meanings: * Block = smallest unit of flash that can be erased. * Page = smallest unit that can be programmed (written) The H7 driver appears to mostly adhere to the generally accepted meanings, but the U5 uses "page" to refer to what is actually a block, and does not implement pages (referring to smallest unit that can be programmed). Additionally, `drivers/mtd/mtd_progmem.c::progmem_bwrite()` appears to use "block" to refer to both blocks and pages. Am I misunderstanding the implementations or am I correct that there doesn't seem to be consistent usage of "block" and "page"? ### Verification - [x] I have verified before submitting the report. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
