-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RcarE3] How to compile arm-trusted-firmware code under windows? #10
Comments
Hi Jeken,
For R-Car H3 board I was doing:
set GCC8_AARCH64_PREFIX=D:\gcc-arm-8.2-2018.08-i686-mingw32-aarch64-elf\bin\aarch64-elf-
set BUILD_DEBUG=1
if /I "%1" equ "RELEASE" set BUILD_DEBUG=0
make bl2 bl31 rcar_layout_tool PLAT=rcar LSI=H3 RCAR_GEN3_ULCB=1 RCAR_SYSTEM_SUSPEND=1 RCAR_SYSTEM_RESET_KEEPON_DDR=1 RCAR_GEN3_ULCB=1 SPD=opteed RCAR_DRAM_SPLIT=1 RCAR_LOSSY_ENABLE=1 PMIC_LEVEL_MODE=0 BL31_CON_LOG=1 RCAR_BL33_EXECUTION_EL=1 DEBUG=%BUILD_DEBUG% MBEDTLS_DIR=E:\SCM\mbedtls CROSS_COMPILE=%GCC8_AARCH64_PREFIX%
make rcar_srecord PLAT=rcar LSI=H3 DEBUG=%BUILD_DEBUG% MBEDTLS_DIR=E:\SCM\mbedtls CROSS_COMPILE=%GCC8_AARCH64_PREFIX%
Hope it helps.
Alexei
…________________________________
From: jeken <[email protected]>
Sent: 22 February 2019 09:52:36
To: renesas-rcar/arm-trusted-firmware
Cc: Subscribed
Subject: [renesas-rcar/arm-trusted-firmware] [RcarE3] How to compile arm-trusted-firmware code under windows? (#10)
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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#10>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKd5n-JkgmS4Zm9l12vd-svRJmavVVBtks5vP73kgaJpZM4bJPWe>.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
|
Hello Alexei, D:\nio_tmp\tools\IPL\arm-trusted-firmware>set GCC7_AARCH64_PREFIX=D:/toolschain/ D:\nio_tmp\tools\IPL\arm-trusted-firmware>set BUILD_DEBUG=1 if /I "" equ "RELEAS D:\nio_tmp\tools\IPL\arm-trusted-firmware>make CROSS_COMPILE=D:/toolschain/mingw D:\nio_tmp\tools\IPL\arm-trusted-firmware> BR, |
Hi Jeken,
I was using make for Windows:
GNU Make 4.2.1
Built for Windows32
Regards.
Alexei
…________________________________
From: jeken <[email protected]>
Sent: 25 February 2019 05:25:57
To: renesas-rcar/arm-trusted-firmware
Cc: Alexei Fedorov; Comment
Subject: Re: [renesas-rcar/arm-trusted-firmware] [RcarE3] How to compile arm-trusted-firmware code under windows? (#10)
For more easy to see, add one screenshot picture
[build]<https://user-images.githubusercontent.com/19191005/53315971-dce09600-3900-11e9-9266-fa9850f76330.JPG>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKd5n3t2WOAHoDF7p0WYbsASy6-Cx7iRks5vQ3PlgaJpZM4bJPWe>.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
|
Hi Alexei, Can you share your email ? And for this issue, I think that it maybe using error tools on the Win OS , Can you share your tools via packages ? and fast locate problems. BR, |
Hi Xueqin / Jeken
Put
set GCC8_AARCH64_PREFIX=D:\gcc-arm-8.2-2019.01-i686-mingw32-aarch64-elf\bin\aarch64-elf-
in file called smth. like "set_env.bat" & call it just once in your command prompt session.
GCC toolchain can be found in
https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads
Put
set BUILD_DEBUG=1
if /I "%1" equ "RELEASE" set BUILD_DEBUG=0
make bl2 bl31 rcar_layout_tool PLAT=rcar LSI=H3 RCAR_GEN3_ULCB=1 RCAR_SYSTEM_SUSPEND=1 RCAR_SYSTEM_RESET_KEEPON_DDR=1 RCAR_GEN3_ULCB=1 SPD=opteed RCAR_DRAM_SPLIT=1 RCAR_LOSSY_ENABLE=1 PMIC_LEVEL_MODE=0 BL31_CON_LOG=1 RCAR_BL33_EXECUTION_EL=1 DEBUG=%BUILD_DEBUG% MBEDTLS_DIR=E:\SCM\mbedtls CROSS_COMPILE=%GCC8_AARCH64_PREFIX%
make rcar_srecord PLAT=rcar LSI=H3 DEBUG=%BUILD_DEBUG% MBEDTLS_DIR=E:\SCM\mbedtls CROSS_COMPILE=%GCC8_AARCH64_PREFIX%
in "my_build.bat" & call it with "my_build.bat DEBUG" or "my_build.bat RELEASE"
Alexei
[email protected]
…________________________________
From: jeken <[email protected]>
Sent: 26 February 2019 06:07:45
To: renesas-rcar/arm-trusted-firmware
Cc: Alexei Fedorov; Comment
Subject: Re: [renesas-rcar/arm-trusted-firmware] [RcarE3] How to compile arm-trusted-firmware code under windows? (#10)
Hi Alexei,
Can you share your email ? And for this issue, I think that it maybe using error tools on the Win OS , Can you share your tools via packages ? and fast locate problems.
BR,
Xueqin ZHUANG
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKd5n5mB056TZV9AmzUnma_LcbJQDPBrks5vRM8xgaJpZM4bJPWe>.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
|
Hello Alex, I have sent email to you, and github upload file limited type. BR, |
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
The text was updated successfully, but these errors were encountered: