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
The response contains information like the number of physical partitions/LUNs, the available commands, the chip serial. We should use this information instead of hardcoded values.
Example device log
[Device] Device Programmer Entry: pbl_shared = 0x148a7038
[Device] Binary build date: Jun 22 2023 @ 13:20:29
[Device] Binary build date: Jun 22 2023 @ 13:20:29
[Device] Chip serial num: 3595145395 (0xd64990b3)
[Device] Supported Functions (16):
[Device] program
[Device] read
[Device] nop
[Device] patch
[Device] configure
[Device] setbootablestoragedrive
[Device] erase
[Device] power
[Device] firmwarewrite
[Device] getstorageinfo
[Device] benchmark
[Device] peek
[Device] poke
[Device] emmc
[Device] ufs
[Device] fixgpt
[Device] End of supported functions 16
[Device] Calling handler for configure
[Device] Storage type set to value UFS
parse available commands (to switch between fast erase and flashing zeroes, for example)
store the serial number (we currently only get the chip serial from sahara, but if the device is already in firehose mode we can't use sahara commands)
The text was updated successfully, but these errors were encountered:
The response contains information like the number of physical partitions/LUNs, the available commands, the chip serial. We should use this information instead of hardcoded values.
Example device log
The text was updated successfully, but these errors were encountered: