Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firehose: parse response from configure command #94

Open
2 tasks
incognitojam opened this issue Mar 14, 2025 · 0 comments
Open
2 tasks

Firehose: parse response from configure command #94

incognitojam opened this issue Mar 14, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@incognitojam
Copy link
Member

incognitojam commented Mar 14, 2025

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)
@incognitojam incognitojam added the enhancement New feature or request label Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant