Lines Matching +full:secure +full:- +full:firmware

1 .. SPDX-License-Identifier: GPL-2.0
13 The ``iosm`` driver implements the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
18 * - Name
19 - Type
20 - Mode
21 - Description
22 * - ``erase_full_flash``
23 - u8
24 - runtime
25 - erase_full_flash parameter is used to check if full erase is required for
26 the device during firmware flashing.
35 ``devlink-flash`` interface.
41 firmware image that need to be flashed as requested by user space application.
42 Supported firmware image types.
44 .. list-table:: Firmware Image types
47 * - Name
48 - Description
49 * - ``PSI RAM``
50 - Primary Signed Image
51 * - ``EBL``
52 - External Bootloader
53 * - ``FLS``
54 - Modem Software Image
57 device is in BOOT ROM stage. Once this is successful, the actual modem firmware
59 each having one secure bin file and at least one Loadmap/Region file. For flashing
64 If the device has to be fully erased before firmware flashing, user application
84 4) Once EBL is injected successfully, then the actual firmware flashing takes
85 place. Below is the sequence of commands used for each of the firmware images.
87 a) Flash secure bin file.
100 In case a firmware encounters an exception, a snapshot will be taken by the
103 .. list-table:: Regions implemented
106 * - Name
107 - Description
108 * - ``report.json``
109 - The summary of exception details logged as part of this region.
110 * - ``coredump.fcd``
111 - This region contains the details related to the exception occurred in the
113 * - ``cdd.log``
114 - This region contains the logs related to the modem CDD driver.
115 * - ``eeprom.bin``
116 - This region contains the eeprom logs.
117 * - ``bootcore_trace.bin``
118 - This region contains the current instance of bootloader logs.
119 * - ``bootcore_prev_trace.bin``
120 - This region contains the previous instance of bootloader logs.