]>
Commit | Line | Data |
---|---|---|
261d2760 DR |
1 | /* |
2 | * Copyright 2014 Broadcom Corporation. | |
3 | * | |
4 | * SPDX-License-Identifier: GPL-2.0+ | |
5 | */ | |
6 | ||
7 | Semihosting is ARM's way of having a real or virtual target communicate | |
8 | with a host or host debugger for basic operations such as file I/O, | |
9 | console I/O, etc. Please see | |
10 | http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0471c/Bgbjjgij.html for more information. | |
11 | ||
12 | For developing on armv8 virtual fastmodel platforms, semihosting is a | |
13 | valuable tool since it allows access to image/configuration files before | |
14 | eMMC or other NV media are available. | |
15 | ||
16 | There are two main ARM virtual Fixed Virtual Platform (FVP) models, | |
17 | Versatile Express (VE) FVP and BASE FVP (See | |
18 | http://www.arm.com/products/tools/models/fast-models/foundation-model.php) | |
19 | The initial vexpress64 u-boot board created here runs on the VE virtual | |
20 | platform using the license-free Foundation_v8 simulator. Fortunately, | |
21 | the Foundation_v8 simulator also supports the BASE_FVP model which | |
22 | companies can purchase licenses for and contain much more functionality. | |
23 | So we can, in u-boot, run either model by either using the VE FVP (default), | |
24 | or turning on CONFIG_BASE_FVP for the more full featured model. | |
25 | ||
26 | Rather than create a new armv8 board similar to armltd/vexpress64, add | |
27 | semihosting calls to the existing one, enabled with CONFIG_SEMIHOSTING | |
28 | and CONFIG_BASE_FVP both set. Also reuse the existing board config file | |
29 | vexpress_aemv8a.h but differentiate the two models by the presence or | |
30 | absence of CONFIG_BASE_FVP. This change is tested and works on both the | |
31 | Foundation and Base fastmodel simulators. | |
32 | ||
202a674b | 33 | The semihosting code adds a command: |
261d2760 | 34 | |
202a674b | 35 | smhload <image> <address> [env var] |
261d2760 | 36 | |
202a674b LW |
37 | That will load an image from the host filesystem into RAM at the specified |
38 | address and optionally store the load end address in the specified | |
39 | environment variable. |