BEE USER KEYS boot+app

acallamp — Sat, 07 Dec 2024 04:32:30 GMT

hi:

I refactored app.bin with the command and generated app-2.bin. After burning it in, the code couldn't run. I don't know where the problem lies?

# =========== BEE configuration ===========
# ----------------------------------------------------------------------------------------------------
# == Basic Settings ==
# ----------------------------------------------------------------------------------------------------
output_folder: "../bootable_images" # [Required], BEE output folder; Folder name to store generated BEE output
input_binary: "../bootable_images/boot_hab.bin" # [Required], Input binary file; Path to input binary file
output_name: "../bootable_images/Position.bin" # [Optional], Output binary file name; File name of the encrypted file, output_folder/output_name
header_name: "bee_ehdr" # [Optional], File name of the exported BEE region headers; output_folder/header_name + index will be prepended

output_folder: "../bootable_images" # [Required], BEE output folder; Folder name to store generated BEE output
input_binary: "../bootable_images/app.bin" # [Required], Input binary file; Path to input binary file
output_name: "../bootable_images/app-2.bin" # [Optional], Output binary file name; File name of the encrypted file, output_folder/output_name
# ----------------------------------------------------------------------------------------------------
# == BEE Settings ==
# ----------------------------------------------------------------------------------------------------
engine_selection: engine0 # [Required], Engine selection; BEE Engine Selection, engine0, engine1 or both engines; Possible options:['engine0', 'engine1', 'both']
engine_key_selection: zero # [Required], Engine Key selection; Random Key or Zero key; Possible options:['random', 'zero']
base_address: '0x60001000' # [Required], Base address of the image
bee_engine: # [Required], Bee engines; Configuration of BEE engines
# # # Engine 0 # # #
- bee_cfg: # [Required], Engine Config; BEE engine configuration
user_key: 0x64847E37868D2391B95A6D54DAB19DC2 # [Required], User AES-128 key; AES key for encryption
protected_region: # [Optional], Protected region; List of protected regions, up to four regions
- start_address: '0x60001000' # [Required], Start address of protected region, it should be aligned to 1 KB (1024 B)
length: '0x0000A800' # [Required], Length of protected region, it should be aligned to 1 KB (1024 B)
protected_level: 0 # [Required], Protected level (0/1/2/3), 0 is default
- start_address: '0x60020000' # [Required], Start address of protected region, it should be aligned to 1 KB (1024 B)
length: '0x0000B800' # [Required], Length of protected region, it should be aligned to 1 KB (1024 B)
protected_level: 0 # [Required], Protected level (0/1/2/3), 0 is default

Re: BEE USER KEYS boot+app

liborukropec — Mon, 09 Dec 2024 16:09:23 GMT

Hello,

it is not clear what you have exactly did. If you put all into one bee_config.yaml file, then it won't work, because you cannot have multiple input_binary, output_name attributes, only one will be used. It is not an array.

May be either:

first encrypt app.bin as it is main application (Source input image on Build tab) and after encryption use it as an additional image,
or create a separate BEE YAML file just for app.bin and create manually in a command line.

Regards,

Libor

MCUXpresso Secure Provisioning ToolのトピックBEE USER KEYS boot+app

BEE USER KEYS boot+app

Re: BEE USER KEYS boot+app