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
cbfstool coreboot.rom add -f IVB_BIOSAC_PRODUCTION.bin -n txt_bios_acm.bin -t raw
cbfstool coreboot.rom add -f SNB_IVB_SINIT_20190708_PW.bin -n txt_bios_acm.bin -t raw
Above, the EC firmware and BIOS ACM file file paths include whitespaces which screws up pasting the lines. This might be intended, but I don't see why it would be?! 🤔
Expected behavior
Different values for the -n parameter should be provided
Actual behavior
Same values are disencouraging to try this
Screenshots
No response
Additional context
Not much to say about this, sorry.
Solutions you've tried
Thought about using -n txt_bios_snb.bin for the second rom, but being unable to find good documentation about this step I was too afraid of bricking my device and instead decided to ask for your help.
The text was updated successfully, but these errors were encountered:
thanks for your quick response and action. You actually found two whitespace misses I didn't see 😅 The ones I meant which are in lines 134 and 140, look for "-3fe3- 42a0-". Might be a markup rendering error, but in the final document you cannot copy and paste those lines without getting an error.
Component
Dasharo documentation
Device
Dell OptiPlex 7010, Dell OptiPlex 9010
Dasharo version
No response
Dasharo Tools Suite version
No response
Test case ID
No response
Brief summary
cbfstool command has identical -n txt_bios_acm.bin for both vendor roms
How reproducible
No response
How to reproduce
https://docs.dasharo.com/variants/dell_optiplex/initial-deployment/#firmware-preparation has a potential copy&paste error at the
-n
parameter (bothtxt_bios_acm.bin
):Above, the
EC firmware
andBIOS ACM file
file paths include whitespaces which screws up pasting the lines. This might be intended, but I don't see why it would be?! 🤔Expected behavior
Different values for the
-n
parameter should be providedActual behavior
Same values are disencouraging to try this
Screenshots
No response
Additional context
Not much to say about this, sorry.
Solutions you've tried
Thought about using
-n txt_bios_snb.bin
for the second rom, but being unable to find good documentation about this step I was too afraid of bricking my device and instead decided to ask for your help.The text was updated successfully, but these errors were encountered: