You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the memory-25x, you have the ability to set the sector size, using the -S parameter.
However setting this value does not update the command that's actually sent to the flash.
By default the opcode 0x20 is sent, which (on common flashes) is a 4kB sector erase.
Most flash devices supports the 64kB sector erase, which typically executes faster, but in order to make use of this the opcode sent will need to change based on the -S parameter.
The text was updated successfully, but these errors were encountered:
@gregdavill In case SFDP is available this is easy to handle. What is to be done if there's no SFDP data available? Should an option to specify the exact erase opcode be mandatory in this case?
Using SFDP makes the most sense when it's available as a default option, it can pick the largest erase sector size based on the amount of data to write.
If an opcode is presented it should take precedence over the SFDP. (But show a WARN/INFO if SFDP is available and the opcode is not present in the SFDP)
If no SFDP is available, requiring the opcode to be provided is a good option.
When using the memory-25x, you have the ability to set the sector size, using the
-S
parameter.However setting this value does not update the command that's actually sent to the flash.
By default the opcode
0x20
is sent, which (on common flashes) is a 4kB sector erase.Most flash devices supports the 64kB sector erase, which typically executes faster, but in order to make use of this the opcode sent will need to change based on the
-S
parameter.The text was updated successfully, but these errors were encountered: