Difference between revisions of "AXEL ULite SOM/AXEL ULite Hardware/Power and Reset/Boot process and bootstrap configuration"
| Line 2: | Line 2: | ||
NXP iMX6UL processor implements a very flexible boot process. This versatility comes at the price of a non trivial bootstrap configuration scheme. Typical system-on-module (SOM for short) adopter does not want/need to deal with such complexity. In other words he/she expects to manage few - virtually none! - boot configuration issues because it is assumed they are handled by the SOM itself. Nevertheless, there are specific applications where the system integrator needs full control of all the bootstrap configuration options, even if the design is built upon a SOM. | NXP iMX6UL processor implements a very flexible boot process. This versatility comes at the price of a non trivial bootstrap configuration scheme. Typical system-on-module (SOM for short) adopter does not want/need to deal with such complexity. In other words he/she expects to manage few - virtually none! - boot configuration issues because it is assumed they are handled by the SOM itself. Nevertheless, there are specific applications where the system integrator needs full control of all the bootstrap configuration options, even if the design is built upon a SOM. | ||
| − | These two needs - ease of use and configurability - clearly push in opposite directions. During the conception of the product AXELULite, specific attention has been addressed to find a viable trade off to satisfy such requirements. This effort has led to the options that are detailed in the section | + | These two needs - ease of use and configurability - clearly push in opposite directions. During the conception of the product AXELULite, specific attention has been addressed to find a viable trade off to satisfy such requirements. This effort has led to the options that are detailed in the section [[#Options for AXELULite users]]. Before skipping to it, it is recommended to read the following section that depicts an overview of the processor's boot process. |
| − | |||
| − | |||
==Overview of NXP iMX6UL bootstrap process== | ==Overview of NXP iMX6UL bootstrap process== | ||
==Options for AXELULite users== | ==Options for AXELULite users== | ||
Revision as of 14:54, 7 June 2016
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Introduction[edit | edit source]
NXP iMX6UL processor implements a very flexible boot process. This versatility comes at the price of a non trivial bootstrap configuration scheme. Typical system-on-module (SOM for short) adopter does not want/need to deal with such complexity. In other words he/she expects to manage few - virtually none! - boot configuration issues because it is assumed they are handled by the SOM itself. Nevertheless, there are specific applications where the system integrator needs full control of all the bootstrap configuration options, even if the design is built upon a SOM.
These two needs - ease of use and configurability - clearly push in opposite directions. During the conception of the product AXELULite, specific attention has been addressed to find a viable trade off to satisfy such requirements. This effort has led to the options that are detailed in the section #Options for AXELULite users. Before skipping to it, it is recommended to read the following section that depicts an overview of the processor's boot process.
