Store default firmware dump path in a variable. This makes logical
connection on which file flashroom shall create and which file is
actualy used by psptool.
Signed-off-by: Mateusz Kusiak <mateusz.kusiak@3mdeb.com>
Add note that for psptool to return valid "Success" status in the HCL
report, it must be fixed at sources. Current limitations that cause
"UNKNOWN" status:
* All warnings are directed to sterr
* The tool mostly print warnings, not errors. This includes non-AMD
binaries or just files full of zeros.
* The tool almos allways returns sucess status code, including the
situtations described above.
Signed-off-by: Mateusz Kusiak <mateusz.kusiak@3mdeb.com>
This commit adds psptool support to HCL reports. The psptool is either
run on dumped firmware if available, but users can also place firmware
binaries from elsewhere in /firmware/external. This is a workaround as
on some platforms flashrom does not work under stock firmware.
Signed-off-by: Mateusz Kusiak <mateusz.kusiak@3mdeb.com>
Multiple changes:
- ask if user wants to continue if smmstore migration fails
- stop update if `flashrom` can't read flash in `set_flashrom_update_params`
- rework send_dts_logs function
- fix visible error when no network interface
- print link to docs if sending logs fails
- send logs to public hcl if DPP credentials don't work
- print path to created archive in case user wants to copy them manually
- add recovery/brick warnings and contact information in case flashing fails
- replace MinIO text displayed for users with 3mdeb server
- add fix for multiple FUM updates starting. Ask user if they want to start automatic update or go to main menu.
Less code duplication, add recovery information, in the future we can
add automatic recovery attempt (try to flash backup)
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>
- Print path to archive with logs
- Print docs link on how to share logs if function failed
- Refactoring
- Fix cat error print when no network
Signed-off-by: Michał Iwanicki <michal.iwanicki@3mdeb.com>