liam-geotab commented on PR #20144: URL: https://github.com/apache/nuttx/pull/20144#issuecomment-5668622301
Hey @darrylring, The interesting differences in flexibility seem to be in the spirit of preventing faults. This PR: pro: detect written blocks by checking the lock status (although this won't help if interrupted between write and lock). con: write granularity (effective) is block sized con: I'm told that reading part of a block that wasn't programmed causes a fault Your branch: pro: write granularity is word sized pro: uses existing efuse driver interface con: writing the same OTP address twice is not prevented and is UB, I'm told. Or crash? Mykhailo may join the discussion. There may be a way to catch faults and return an error. Too bad developing this feature is literally expensive. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
