-
hi, experts:
if i run "make DEBUG=1 V=1", and then run "make dump".
It will tip me:
......
Built build/fvp/debug/bl31.bin successfully
Including bl1.mk
Including bl2.mk
Including bl31.mk
OBJDUMP
/…
-
hi, experts:
After review trusted firmware code, i found the execution level change flow is:
1. BL1 ---- EL3 and in secure state
2. BL2 ---- EL1 and in seucre state
3. BL31---- EL3 and in secure sta…
-
hi, experts:
I found:
BL2 will call smc instruction to let BL1 to run BL31 code with EL3 level.
But i have some questions about exception table .
1. BL2 will setup exception table for EL1.
This e…
-
hi, experts:
I have a question about stack setting for BL1/BL2 etc.
Take BL1 code as an example:
**STACKS_START** = 0x0400 0000
**STACKS_END** = 0x0400 4000
platform_normal_stacks array points to…
-
The 'clean' rule is supposed to clean the build for the selected platform. That means that the 'PLAT' environment variable must be defined, otherwise it should complain and fail.
It correctly complai…
-
hi, experts:
For the bare-metal SOC bringup, PSCI related code seems redundant.
So:
Is there any simple method to exclude psci related code when compiling ATF code?
Not call runtime_svc_init() is eno…
-
Commit f58ad36f2f51798b093d282b56a3a311fdc78ca9 (Add Firmware Image Package creation tool) added three uses of the command `make -C ${FIPTOOLPATH}` following usual makefile practice, these should be `…
tixy updated
10 years ago