Kristofer Jonsson | 7422610 | 2022-05-25 16:55:24 +0200 | [diff] [blame] | 1 | @startuml |
| 2 | |
| 3 | skinparam { |
| 4 | BackgroundColor #EEEBDC |
| 5 | DefaultFontColor black |
| 6 | } |
| 7 | |
| 8 | skinparam component { |
| 9 | BackgroundColor #0091BD |
| 10 | BorderColor black |
| 11 | ArrowColor black |
| 12 | } |
| 13 | |
| 14 | skinparam note { |
| 15 | BackgroundColor #00C1DE |
| 16 | BorderColor black |
| 17 | } |
| 18 | |
| 19 | [ethosu_target_init] --> [ethosu_target_startup] |
| 20 | |
| 21 | [ethosu_target_startup] --> [ethosu_target_link] |
| 22 | |
| 23 | [ethosu_target_link] --> [ethosu_target_common] |
| 24 | |
| 25 | note right of ethosu_target_init |
| 26 | Links drivers and calls targetSetup() to initialize the target. |
| 27 | end note |
| 28 | |
| 29 | note right of ethosu_target_startup |
| 30 | Links CMSIS Device and Core libraries. |
| 31 | |
| 32 | CMSIS Device provides startup and system files that are used to initialize |
| 33 | the CPU, configure CPU extensions and setup the interrupt vector table. |
| 34 | |
| 35 | CMSIS Core provides an interface to the CPU, for example configuring |
| 36 | caches, systick or interrupt handling. |
| 37 | |
| 38 | Some RTOSes provide their own startup files. Those applications should |
| 39 | link ethosu_target_link instead. |
| 40 | end note |
| 41 | |
| 42 | note right of ethosu_target_link |
| 43 | Adds scatter file or linker script, describing the memory layout of the target. |
| 44 | end note |
| 45 | |
| 46 | note right of ethosu_target_common |
| 47 | All applications should depend on this library. It is used to export definitions |
| 48 | from the target to the application. |
| 49 | end note |
| 50 | |
| 51 | @enduml |