summaryrefslogtreecommitdiff
path: root/.gitignore
Commit message (Collapse)AuthorAgeFilesLines
* chore: add dependency files generated by tools to .gitignoreManish V Badarkhe2023-04-051-0/+1
| | | | | | | | In order to avoid git tracking dependency files generated while compiling tools, the .gitignore list was updated with these files. Change-Id: I97f1ace40441353779f4f82051d66c478571df38 Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>
* chore: add encrypt_fw to gitignoreYann Gautier2023-02-021-0/+2
| | | | | | | | Add tools/encrypt_fw/encrypt_fw & tools/encrypt_fw/encrypt_fw.exe to .gitignore file, to avoid git listing those binary files. Signed-off-by: Yann Gautier <yann.gautier@foss.st.com> Change-Id: I2f4ddbe1c11848513fe20f7c8b448a041988cc4f
* fix(docs): prevent a virtual environment from failing a buildBoyan Karatotev2022-11-161-0/+6
| | | | | | | | | | | | sphinx-build is passed a blanket "." to build all docs. However, if a virtual environment is placed within the docs directory, sphinx will try to build it which will fail due to some weird files it has. This excludes the most common virtual environment directories from the build to prevent this. Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com> Change-Id: Ieeb14cfc5730d21c986611feb0ed379c58dfcae2
* feat(sptool): delete c version of the sptoolJ-Alves2022-05-041-2/+0
| | | | | Change-Id: I224762ef66624c78dd87729dac80b2c956ee50ba Signed-off-by: J-Alves <joao.alves@arm.com>
* feat(sptool): use python version of sptoolJ-Alves2022-05-041-0/+1
| | | | | Change-Id: I567ef0b977c69c38323740a592dd9451e261a407 Signed-off-by: J-Alves <joao.alves@arm.com>
* build(hooks): add Husky configurationChris Kay2021-04-191-0/+2
| | | | | | | | | | | | | | Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
* tools: renesas: Add tool support for RZ/G2 platformsBiju Das2021-01-131-0/+4
| | | | | | | | | Add tool support for creating bootparam and cert_header images for RZ/G2 SoC based platforms. Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> Change-Id: Iab8ba6eda442c8d75f23c5633b8178f86339e4c9
* Ignore the ctags fileDeepika Bhavnani2020-01-221-0/+4
| | | | | Signed-off-by: Deepika Bhavnani <deepika.bhavnani@arm.com> Change-Id: Ic78bda00aba0e350095c3dcd59f688f4a27ed1d4
* meson: Rename platform directory to amlogicCarlo Caione2019-09-051-1/+1
| | | | | | | | | Meson is the internal code name for the SoC family. The correct name for the platform should be Amlogic. Change the name of the platform directory. Signed-off-by: Carlo Caione <ccaione@baylibre.com> Change-Id: Icc140e1ea137f12117acbf64c7dcb1a8b66b345d
* meson/gxl: Add tool to create bl31 bootable imagesRemi Pommarel2019-04-021-0/+1
| | | | | | | | GXL platforms need to have a specific header at the beginning of bl31 image to be able to boot. This adds a tool to create that and calls it at build time. Signed-off-by: Remi Pommarel <repk@triplefau.lt>
* gitignore: Ignore sptool and doimage binariesAntonio Nino Diaz2018-12-181-1/+3
| | | | | Change-Id: I119b85179f68148e128cc194f11d2cccb1e33d6d Signed-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
* rcar-gen3: initial commit for the rcar-gen3 boardsJorge Ramirez-Ortiz2018-10-171-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reference code: ============== rar_gen3: IPL and Secure Monitor Rev1.0.22 https://github.com/renesas-rcar/arm-trusted-firmware [rcar_gen3] Author: Takuya Sakata <takuya.sakata.wz@bp.renesas.com> Date: Thu Aug 30 21:26:41 2018 +0900 Update IPL and Secure Monitor Rev1.0.22 General Information: =================== This port has been tested on the Salvator-X Soc_id r8a7795 revision ES1.1 (uses an SPD). Build Tested: ------------- ATFW_OPT="LSI=H3 RCAR_DRAM_SPLIT=1 RCAR_LOSSY_ENABLE=1" MBEDTLS_DIR=$mbedtls $ make clean bl2 bl31 rcar PLAT=rcar ${ATFW_OPT} SPD=opteed Other dependencies: ------------------ * mbed_tls: git@github.com:ARMmbed/mbedtls.git [devel] Merge: 68dbc94 f34a4c1 Author: Simon Butcher <simon.butcher@arm.com> Date: Thu Aug 30 00:57:28 2018 +0100 * optee_os: https://github.com/BayLibre/optee_os Until it gets merged into OP-TEE, the port requires Renesas' Trusted Environment with a modification to support power management. Author: Jorge Ramirez-Ortiz <jramirez@baylibre.com> Date: Thu Aug 30 16:49:49 2018 +0200 plat-rcar: cpu-suspend: handle the power level Signed-off-by: Jorge Ramirez-Ortiz <jramirez@baylibre.com> * u-boot: The port has beent tested using mainline uboot. Author: Fabio Estevam <festevam@gmail.com> Date: Tue Sep 4 10:23:12 2018 -0300 *linux: The port has beent tested using mainline kernel. Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Sun Sep 16 11:52:37 2018 -0700 Linux 4.19-rc4 Overview --------- BOOTROM starts the cpu at EL3; In this port BL2 will therefore be entered at this exception level (the Renesas' ATF reference tree [1] resets into EL1 before entering BL2 - see its bl2.ld.S) BL2 initializes DDR (and i2c to talk to the PMIC on some platforms) before determining the boot reason (cold or warm). During suspend all CPUs are switched off and the DDR is put in backup mode (some kind of self-refresh mode). This means that BL2 is always entered in a cold boot scenario. Once BL2 boots, it determines the boot reason, writes it to shared memory (BOOT_KIND_BASE) together with the BL31 parameters (PARAMS_BASE) and jumps to BL31. To all effects, BL31 is as if it is being entered in reset mode since it still needs to initialize the rest of the cores; this is the reason behind using direct shared memory access to BOOT_KIND_BASE and PARAMS_BASE instead of using registers to get to those locations (see el3_common_macros.S and bl31_entrypoint.S for the RESET_TO_BL31 use case). Depending on the boot reason BL31 initializes the rest of the cores: in case of suspend, it uses a MBOX memory region to recover the program counters. [1] https://github.com/renesas-rcar/arm-trusted-firmware Tests ----- * cpuidle ------- enable kernel's cpuidle arm_idle driver and boot * system suspend -------------- $ cat suspend.sh #!/bin/bash i2cset -f -y 7 0x30 0x20 0x0F read -p "Switch off SW23 and press return " foo echo mem > /sys/power/state * cpu hotplug: ------------ $ cat offline.sh #!/bin/bash nbr=$1 echo 0 > /sys/devices/system/cpu/cpu$nbr/online printf "ONLINE: " && cat /sys/devices/system/cpu/online printf "OFFLINE: " && cat /sys/devices/system/cpu/offline $ cat online.sh #!/bin/bash nbr=$1 echo 1 > /sys/devices/system/cpu/cpu$nbr/online printf "ONLINE: " && cat /sys/devices/system/cpu/online printf "OFFLINE: " && cat /sys/devices/system/cpu/offline Signed-off-by: ldts <jramirez@baylibre.com>
* fip_create: Remove fip_create compatibility scriptdp-arm2018-09-281-1/+0
| | | | | | | | A compatibility script has been provided for about 2 years. Users should have migrated to fiptool by now so remove the compat script. Change-Id: I643e0c40a9e3fb428bad3be04a82cb431aad74dc Signed-off-by: dp-arm <dimitris.papastamos@arm.com>
* tools: Add stm32image tool into TF-AYann Gautier2018-07-241-0/+3
| | | | | | | | This tools adds a specific header to ST TF-A binary. This header is used by STM32MP1 ROM code to check the bootloader. Signed-off-by: Yann Gautier <yann.gautier@st.com> Signed-off-by: Lionel Debieve <lionel.debieve@st.com>
* tools: add support for Marvell doimageKonstantin Porotchkin2018-07-181-0/+1
| | | | | | | | | | Add Marvell "doimage" utility support. The "doimage" utility allows to create flash images compatible with Marvell BootROM image format. Additionally this tool allows the flash image parsing and verification. Change-Id: Ie8d7ccd0cc2978684e7eecb695f375395fc749ee Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>
* fip: move headers shared between TF and fiptool to include/tools_shareMasahiro Yamada2017-05-231-4/+0
| | | | | | | | | | | | | | | | | | Some header files need to be shared between TF and host programs. For fiptool, two headers are copied to the tools/fiptool directory, but it looks clumsy. This commit introduces a new directory, include/tools_share, which collects headers that should be shared between TF and host programs. This will clarify the interface exposed to host tools. We should add new headers to this directory only when we really need to do so. For clarification, I inserted a blank line between headers from the include/ directory (#include <...>) and ones from a local directory (#include "..." ). Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
* gitignore: ignore GNU GLOBAL tag filesMasahiro Yamada2017-02-031-0/+6
| | | | | | | | GNU GLOBAL (https://www.gnu.org/software/global/) is source code tagging system. It creates 4 tag files (GTAGS, GRTAGS, GSYMS and GPATH) for the symbol cross-reference. Ignore them. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
* .gitignore: ignore editor backup filesMasahiro Yamada2016-10-251-0/+1
| | | | Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
* Replace fip_create with fiptooldp-arm2016-07-291-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fiptool provides a more consistent and intuitive interface compared to the fip_create program. It serves as a better base to build on more features in the future. fiptool supports various subcommands. Below are the currently supported subcommands: 1) info - List the images contained in a FIP file. 2) create - Create a new FIP file with the given images. 3) update - Update an existing FIP with the given images. 4) unpack - Extract a selected set or all the images from a FIP file. 5) remove - Remove images from a FIP file. This is a new command that was not present in fip_create. To create a new FIP file, replace "fip_create" with "fiptool create". To update a FIP file, replace "fip_create" with "fiptool update". To dump the contents of a FIP file, replace "fip_create --dump" with "fiptool info". A compatibility script that emulates the basic functionality of fip_create is provided. Existing scripts might or might not work with the compatibility script. Users are strongly encouraged to migrate to fiptool. Fixes ARM-Software/tf-issues#87 Fixes ARM-Software/tf-issues#108 Fixes ARM-Software/tf-issues#361 Change-Id: I7ee4da7ac60179cc83cf46af890fd8bc61a53330
* Make:Allow for extension in tool names.Evan Lloyd2016-04-011-0/+2
| | | | | | | | | | | | In some build environments executable programs have a specific file extension. The value of BIN_EXT is appended to the relevant tool file names to allow for this. The value of BIN_EXT is set, where appropriate, by the build environment specific make helper (to .exe for Windows build environments). .gitignore is updated to hide the new (.exe) files. Change-Id: Icc32f64b750e425265075ad4e0dea18129640b86
* Build:Replace soft links with file copy.Evan Lloyd2016-04-011-0/+4
| | | | | | | | | | | | | | | Some build environments do not support symbolic links. This patch removes the symlinks previously used to build fip_create and instead copies the relevant header files. The original motivation for using symlinks was to avoid Trusted Firmware library headers conflicting with headers in the compiler standard include path. Copying the header files instead has the same effect. Like other build artefacts, the copied files are listed in .gitignore. The distclean targets have also been updated to remove the copies. Change-Id: Ie8b67bcb133f7f1d660ae93b857950aa15e42b1e
* TBB: rework cert_create tool to follow a data driven approachJuan Castillo2015-07-161-0/+1
| | | | | | | | | | This patch reworks the certificate generation tool to follow a data driven approach. The user may specify at build time the certificates, keys and extensions defined in the CoT, register them using the appropiate macros and the tool will take care of creating the certificates corresponding to the CoT specified. Change-Id: I29950b39343c3e1b71718fce0e77dcf2a9a0be2f
* TBB: add tool to generate certificatesJuan Castillo2015-01-281-0/+2
| | | | | | | | | | | | | | | This patch adds a tool that generates all the necessary elements to establish the chain of trust (CoT) between the images. The tool reads the binary images and signing keys and outputs the corresponding certificates that will be used by the target at run time to verify the authenticity of the images. Note: the platform port must provide the file platform_oid.h. This file will define the OIDs of the x509 extensions that will be added to the certificates in order to establish the CoT. Change-Id: I2734d6808b964a2107ab3a4805110698066a04be
* Update .gitignoreJeenu Viswambharan2014-02-201-0/+12
| | | | | | | | | This patch updates .gitignore file to ignore potential build products, tool object files and binaries Also fixes issue ARM-software/tf-issues#35 Change-Id: I053dfba4ec8fecbcca081cad5b4bf94f8abfb15c
* Build system: Add cscope target to the MakefileJoakim Bech2014-01-301-0/+1
Fixes arm-software/tf-issues#15 Signed-off-by: Joakim Bech <joakim.bech@linaro.org>
View Lorry Controller Status