Giter Club home page Giter Club logo

arm-trusted-firmware's People

Contributors

achingupta avatar alexeifedorov avatar ambroise-arm avatar andre-arm avatar athoelke avatar danh-arm avatar davidcunado-arm avatar etienne-lms avatar glneo avatar hadi-asyrafi avatar hzhuang1 avatar jcastillo-arm avatar jwerner-chromium avatar laurenw-arm avatar lmayencourt avatar madhukar-arm avatar manish-pandey-arm avatar manishvb-arm avatar masahir0y avatar odeprez avatar pali avatar pangupta avatar pbeesley-arm avatar robertovargas-arm avatar sandrine-bailleux-arm avatar smaeul avatar soby-mathew avatar sorenb-xlnx avatar yann-lms avatar yatharth-arm avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

arm-trusted-firmware's Issues

How to build TF-A for Rcar V3H condor board

I am trying to build ATF for Rcar V3H condor board referring to below.

https://trustedfirmware-a.readthedocs.io/en/latest/plat/rcar-gen3.html#tf-a-build-procedure

But it describes only Rcar H3 build options does not describe V3H condor's one. Could you tell me V3H options I have to set.

25.3. How to build
The TF-A build options depend on the target board so you will have to refer to those specific instructions. What follows is customized to the H3 SiP Salvator-X development system used in this port.

25.3.1. Build Tested:
RCAR_OPT=”LSI=H3 RCAR_DRAM_SPLIT=1 RCAR_LOSSY_ENABLE=1” MBEDTLS_DIR=$mbedtls_src

$ MBEDTLS_DIR=$mbedtls_src_tree make clean bl2 bl31 rcar_layout_tool PLAT=rcar ${RCAR_OPT} SPD=opteed

Build failing While doing ATF build

make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rcar LSI=H3
Including services/spd/opteed/opteed.mk
Building rcar
AS common/aarch64/early_exceptions.S
common/aarch64/early_exceptions.S: Assembler messages:
common/aarch64/early_exceptions.S:27: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:33: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:39: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:45: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:55: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:61: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:67: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:73: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:83: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:89: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:95: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:101: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:111: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:117: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:123: Error: non-constant expression in ".if" statement
common/aarch64/early_exceptions.S:129: Error: non-constant expression in ".if" statement
Makefile:546: recipe for target 'build/rcar/release/bl2/early_exceptions.o' failed
make: *** [build/rcar/release/bl2/early_exceptions.o] Error 1

Can't Modify U-Boot Environment Variables on Updated Firmware

I am trying to get up and running with the R-Car H3 Starter Kit Premier Board (h3ulcb). I first followed the instructions here http://elinux.org/R-Car/Boards/Yocto-Gen3 to build Yocto 2.19 for the board. When I attempted to run the built Yocto image on the board, I received a kernel panic message. The limited resources on the internet indicated this was likely due to outdated firmware. I then followed the instructions here http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware to update the firmware on the board. Now when I turn the board on, I am not given the option of cancelling autoboot. The board simply attempts to read from the specified boot file and I am not able to follow the usual process of cancelling autoboot and changing U-Boot's environment variables. Any help would be greatly appreciated!

Output of boot sequence is below:

user@user-linux:~$ sudo picocom -b 115200 --send-cmd "ascii-xfr -vvs" /dev/ttyUSB0
[sudo] password for user:
picocom v1.7

port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : ascii-xfr -vvs
receive_cmd is : rz -vv
imap is :
omap is :
emap is : crcrlf,delbs,

Terminal ready
[ 0.000194] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.14
[ 0.005761] NOTICE: BL2: PRR is R-Car H3 Ver2.0
[ 0.010335] NOTICE: BL2: Board is unknown Rev0.0
[ 0.015006] NOTICE: BL2: Boot device is HyperFlash(80MHz)
[ 0.020445] NOTICE: BL2: LCM state is CM
[ 0.024423] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52
[ 0.030611] NOTICE: BL2: DDR3200(rev.0.22)NOTICE: [COLD_BOOT]NOTICE: ..0
[ 0.091270] NOTICE: BL2: DRAM Split is 4ch
[ 0.095155] NOTICE: BL2: QoS is default setting(rev.0.14)
[ 0.100655] NOTICE: BL2: Lossy Decomp areas
[ 0.104832] NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[ 0.111917] NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[ 0.118829] NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[ 0.125743] NOTICE: BL2: v1.3(release):4eef9a2
[ 0.130233] NOTICE: BL2: Built : 17:35:56, Jul 13 2017
[ 0.135420] NOTICE: BL2: Normal boot
[ 0.139062] NOTICE: BL2: dst=0xe6320190 src=0x8180000 len=512(0x200)
[ 0.145608] NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[ 0.152070] NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[ 0.159295] NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
[ 0.169775] NOTICE: BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)

BL2: Failed to DRAM initialize (-1) on H3SK 8GB Single Rank

Hi,
I am working on an H3SK No.25844. After flashing a new firmware applied this patch, I got this error

[    0.000148] NOTICE:  BL2: R-Car H3 Initial Program Loader(CA57)
[    0.004585] NOTICE:  BL2: Initial Program Loader(Rev.2.0.7)
[    0.010117] NOTICE:  BL2: PRR is R-Car H3 Ver.3.0
[    0.014786] NOTICE:  BL2: Board is Starter Kit Rev.1.0
[    0.019899] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.025326] NOTICE:  BL2: LCM state is CM
[    0.029367] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.035342] NOTICE:  BL2: CH0: 0x400000000 - 0x47fffffff, 2 GiB
[    0.041204] NOTICE:  BL2: CH1: 0x500000000 - 0x57fffffff, 2 GiB
[    0.047079] NOTICE:  BL2: CH2: 0x600000000 - 0x67fffffff, 2 GiB
[    0.052954] NOTICE:  BL2: CH3: 0x700000000 - 0x77fffffff, 2 GiB
[    0.058869] NOTICE:  BL2: DDR3200(rev.0.41)
[    0.068627] NOTICE:  BL2: [COLD_BOOT]
[    0.307251] NOTICE:  BL2: Failed to DRAM initialize (-1).
[    4.999796] ERROR:   
[    5.000589] ERROR:   BL2: System WDT overflow, occured address is 0xe6304780

But another H3SK No.25845 (also Single Rank) is bootable after flashing the same firmware. It's log

[    0.000154] NOTICE:  BL2: R-Car H3/M3/M3N Initial Program Loader(CA57)
[    0.005198] NOTICE:  BL2: Initial Program Loader(Rev.2.0.4)
[    0.010731] NOTICE:  BL2: PRR is R-Car H3 Ver.3.0
[    0.015399] NOTICE:  BL2: Board is Starter Kit Rev.2.1
[    0.020512] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.025938] NOTICE:  BL2: LCM state is CM
[    0.029978] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.035953] NOTICE:  BL2: CH0: 0x400000000 - 0x47fffffff, 2 GiB
[    0.041814] NOTICE:  BL2: CH1: 0x500000000 - 0x57fffffff, 2 GiB
[    0.047689] NOTICE:  BL2: CH2: 0x600000000 - 0x67fffffff, 2 GiB
[    0.053564] NOTICE:  BL2: CH3: 0x700000000 - 0x77fffffff, 2 GiB
[    0.059455] NOTICE:  BL2: DDR3200(rev.0.40)
[    0.074752] NOTICE:  BL2: [COLD_BOOT]
[    0.083508] NOTICE:  BL2: DRAM Split is 4ch(DDR f)
[    0.086807] NOTICE:  BL2: QoS is default setting(rev.0.11)
[    0.092250] NOTICE:  BL2: DRAM refresh interval 1.95 usec
[    0.097607] NOTICE:  BL2: Periodic Write DQ Training
[    0.211354] NOTICE:  BL2: Lossy Decomp areas
[    0.214134] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[    0.221219] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[    0.228131] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[    0.313299] ERROR:   Image magic is wrong!
[    0.315906] ERROR:   Bootloader partition 2 corrupted, setting unbootable
[    0.325393] NOTICE:  BL2: v1.5(release):5da4beea3-dirty
[    0.329124] NOTICE:  BL2: Built : 13:17:38, Apr 15 2021
[    0.334312] NOTICE:  BL2: Normal boot
[    0.337947] NOTICE:  BL2: eMMC boot from partition 1
[    0.342864] NOTICE:  BL2: Load dst=0xe632c100 src=(p:1)0x30000(384) len=0x200(1)
[    0.350377] NOTICE:  BL2: Load dst=0x43f00000 src=(p:1)0x30400(386) len=0x1800(12)
[    0.358023] NOTICE:  BL2: Load dst=0x44000000 src=(p:1)0x40000(512) len=0x10000(128)
[    0.367006] NOTICE:  BL2: Load dst=0x44100000 src=(p:1)0x80000(1024) len=0x100000(2048)
[    0.396199] NOTICE:  BL2: Load dst=0x50000000 src=(p:1)0x200000(4096) len=0x200000(4096)
[    0.448100] NOTICE:  BL2: Booting BL31

I would appreciate any help here
Thanks

How to load fip.bin on Slavtor-XS

I am going to implement Secure Boot on Salvator-XS by enable TBB in the ATF, the cert file for verify image is include in the fip.bin, but I do not know how to load the fip.bin by bl2

IPL fail to initialize DRAM on Salvator-XS

I can confirm the issue with BL2 Rev1.0.23 on Salvator-XS board (Y-R-CAR-H3-SIP-BOARD-SKT-WS30 with SN 3041 (07.10.18))

NOTICE: [ 0.000155] BL2: R-Car H3 Initial Program Loader(CA57)
NOTICE: [ 0.005352] BL2: Initial Program Loader(Rev.1.0.23) <-- latest IPL build as advised in elinux wiki
NOTICE: [ 0.010978] BL2: PRR is R-Car H3 Ver.3.0
NOTICE: [ 0.015650] BL2: Board is Salvator-XS Rev.1.0
NOTICE: [ 0.020756] BL2: Boot device is HyperFlash(80MHz)
NOTICE: [ 0.026208] BL2: LCM state is CM
NOTICE: [ 0.030189] BL2: AVS setting succeeded. DVFS_SetVID=0x53
NOTICE: [ 0.036247] BL2: CH0: 0x400000000 - 0x480000000, 2 GiB
NOTICE: [ 0.042131] BL2: CH1: 0x500000000 - 0x580000000, 2 GiB
NOTICE: [ 0.048016] BL2: CH2: 0x600000000 - 0x680000000, 2 GiB
NOTICE: [ 0.053900] BL2: CH3: 0x700000000 - 0x780000000, 2 GiB
NOTICE: [ 0.059785] BL2: DDR3200(rev.0.34)NOTICE: [COLD_BOOT]NOTICE: ..1 <-- tried all 3 possible frequencies no change
NOTICE: [ 0.553548] BL2: Failed to DRAM initialize (-1).
ERROR: [ 5.007793]
ERROR: [ 5.009356] BL2: System WDT overflow, occured address is 0xe63047d8

With the yocto:

Build Configuration:
BB_VERSION = "1.38.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "salvator-x"
DISTRO = "poky"
DISTRO_VERSION = "2.5.1"
TUNE_FEATURES = "aarch64 cortexa57-cortexa53"
TARGET_FPU = ""
SOC_FAMILY = "rcar-gen3:r8a7795"
meta
meta-poky
meta-yocto-bsp = "sumo:3b8dc3a88e28546100a6b0b2f2cc37f44e619371"
meta-rcar-gen3 = "sumo-dev:276e6ae724d7e604e0d28e4670b8c9edea2957e3"
meta-oe = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
meta-optee = "sumo:282b47a10940c26854c1cca0ec40950192af16fc"

BL2: Failed to initialize DRAM after flashing firmware

Hi,

I am working with a M3 StarterKit No. 0065 (RTP0RC7796SKB00010SA03). It was booting fine with the original firmware, but just after flashing a new firmware I get the following error:

NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.12
NOTICE:  BL2: PRR is R-Car M3 ES1.0
NOTICE:  BL2: Boot device is HyperFlash(80MHz)
NOTICE:  BL2: LCM state is CM
NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x52
NOTICE:  BL2: DDR3200(rev.0.20)[WARM_BOOT]ERROR:
Warm booting...
 The potential of GP-1-8 did not switch to Low.
 If you expect the operation of cold boot,
 check the board configuration (ex, Dip-SW) and/or the H/W failure.
[BOOT_STATUS_UPDATE_ERROR]..1
NOTICE:  BL2: Failed to DRAM initialize (-1).
ERROR:
ERROR:   BL2: System WDT overflow, occured address is 0xe630d354

I am compiling with: make PLAT=rcar LSI=M3 all dummytool

If I reset the board by pressing SW9, or pressing SW8 twice or repluging the source power and pressing SW8 I sill get warm boot detected.

I don't believe it is a hardware issue as it stopped working just after flashing the firmware using these instructions.

I would appreciate any help here
Thanks

fail to build ATF for FVP in BL1 and BL31

i tried to build ATF for FVP platform and got this error
lib/cpus/aarch64/cortex_a75.S:48: Error: constant expression required at operand 3 -- `ubfx x0,x0,#ID_AA64PFR0_CSV2_SHIFT,#ID_AA64PFR0_CSV2_LENGTH'
Makefile:556: recipe for target 'build/fvp/release/bl31/cortex_a75.o' failed

[RcarE3] How to compile arm-trusted-firmware code under windows?

Hello ,
I am using RcarE3 platform.
And for convenience , Project need to change arm-trusted-firmware to the win OS to compile due to all project code compile under win system.
So could you shared the method how to compile under win OS, for example mingw

BR,
Jeken ZHUANG

Rev.1.0.20 DDR initialize fails on salvator-x

I just built the latest version
(Rev.1.0.20) fromhttps://github.com/renesas-rcar/arm-trusted-firmware.git

and initializing DDR fails:

[ 0.000283] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20
[ 0.005843] NOTICE: BL2: PRR is R-Car H3 Ver1.1
[ 0.010426] NOTICE: BL2: Board is Salvator-X Rev1.0
[ 0.015368] NOTICE: BL2: Boot device is HyperFlash(80MHz)
[ 0.020793] NOTICE: BL2: LCM state is CM
[ 0.024838] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53
[ 0.030887] NOTICE: BL2: DDR2400(rev.0.31)NOTICE: [COLD_BOOT]NOTICE: ..1
[ 0.162859] NOTICE: BL2: Failed to DRAM initialize (-1).

Using Rev.1.0.19 (commit: 3f4912a) is working.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.