搜索结果

Some typical issues related to the management of a coprocessor are listed below. Solutions or debugging methods are proposed for these iss …x]], [[:Category:Coprocessor management STM32Cube | Coprocessor management STM32Cube]] or [[:Category:Troubleshooting grids|troubleshooting grids]] categories.

This article provides an overview of the management of the heterogeneous asymmetric architecture implemented in the STM32 MPU… …ndent firmwares on each CPU core. The below subsystems are involved in the management of the coexistence of the two CPU subsystems:

The resource table is a global variable declared as a structure in the coprocessor firmware. This table contains resources that the remote processor requires This table must be defined in a specific data section of the coprocessor firmware, parsed by the [[Linux remoteproc framework overview | RemoteProc]

…e tree]]. The [[Device tree|device tree]] can be either generated by the [[STM32CubeMX]] tool or edited manually. …]], [[STM32MP15 Linux kernel overview|Linux]], [[STM32CubeMP1 architecture|STM32Cube]] and [[OP-TEE overview|OP-TEE]]) must have a '''configuration''' that is…

…his fact introduces potential contentions that must be secured by a policy management. Refer to [[STM32MP15 peripherals overview]] for more information on periph The role of the resource management is to control the assignment of a peripheral to a dedicated core and to pro

The [[Coprocessor_management_overview|coprocessor]] firmware can be loaded and started by: This article explains how this coprocessor firmware is loaded by [[U-Boot_overview|U-Boot]] and started before the Lin

Further information on HAL can be found here: [[STM32CubeMP1 architecture]] The power HAL supports the following APIs related to power management:

…> startup, the boot chain also installs the secure monitor and may support coprocessor firmware loading. …e of a secure monitor are: user authentication, key storage, and tampering management.

…e of a secure monitor are: user authentication, key storage, and tampering management. * the <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;coprocessor&nbsp;</span> firmware, running on the Arm Cortex-M core. This can be used…

…nning. This is done by Linux [[Coprocessor management overview|coprocessor management]], by default. * Cortex-M4 STM32Cube firmware

…ifferences. In addition it offers services to monitor and debug the remote coprocessor. …these values in the [[STM32CubeMP1_Package#STM32CubeMP1 package overview | STM32Cube firmware]] linker script.

If some Cortex-M4 firmware logs have been output to the [[Coprocessor_resource_table#How_to_add_trace_for_the_log_buffer|trace buffer declared in [[Category:Coprocessor management STM32Cube]]

==Introduction to STM32Cube== '''STM32Cube&trade;''' provides comprehensive embedded software libraries and tools, sig