When 'bfcfg' cannot be executed from Arm operating system, an alternative would be to run the command on external host to convert the config file to a binary format.
Example of usage:
$ bfcfg -c bf.cfg
16+0 records in
16+0 records out
4096 bytes (4.1 kB) copied, 0.000513951 s, 8.0 MB/s
bfcfg: configuration blob written to bf.cfg.bin
The output binary filename consist of the input filename with a the extension '.bin'. In this example, the output filename is 'bf.cfg.bin'.
The binary file can be used to create an EFI capsule. The capsule file can be appended to a BFB file and applied from external host. Once applied, the configuration is processed by the platform firmware. As of now only MFG configuration is supported.
When 'bfcfg' cannot be executed from Arm operating system, an alternative would be to run the command on external host to convert the config file to a binary format.
Example of usage:
$ bfcfg -c bf.cfg 16+0 records in 16+0 records out 4096 bytes (4.1 kB) copied, 0.000513951 s, 8.0 MB/s
bfcfg: configuration blob written to bf.cfg.bin
The output binary filename consist of the input filename with a the extension '.bin'. In this example, the output filename is 'bf.cfg.bin'.
The binary file can be used to create an EFI capsule. The capsule file can be appended to a BFB file and applied from external host. Once applied, the configuration is processed by the platform firmware. As of now only MFG configuration is supported.