| /u-boot/tools/ |
| A D | imx8m_image.sh | 25 …objcopy -I binary -O binary --pad-to 0x8000 --gap-fill=0x0 lpddr4_pmu_train_1d_imem.bin lpddr4_pmu…
26 …objcopy -I binary -O binary --pad-to 0x4000 --gap-fill=0x0 lpddr4_pmu_train_1d_dmem.bin lpddr4_pmu…
27 …objcopy -I binary -O binary --pad-to 0x8000 --gap-fill=0x0 lpddr4_pmu_train_2d_imem.bin lpddr4_pmu…
35 objcopy -I binary -O binary --pad-to 0x8000 --gap-fill=0x0 ddr4_imem_1d.bin ddr4_imem_1d_pad.bin
36 objcopy -I binary -O binary --pad-to 0x4000 --gap-fill=0x0 ddr4_dmem_1d.bin ddr4_dmem_1d_pad.bin
37 objcopy -I binary -O binary --pad-to 0x8000 --gap-fill=0x0 ddr4_imem_2d.bin ddr4_imem_2d_pad.bin
|
| /u-boot/arch/powerpc/cpu/mpc8xx/ |
| A D | immap.c | 142 binary("PA_DIR", in_be16(l++), PA_NBITS); in do_iopinfo()
143 binary("PB_DIR", in_be32(R++), PB_NBITS); in do_iopinfo()
144 binary("PA_PAR", in_be16(l++), PA_NBITS); in do_iopinfo()
145 binary("PB_PAR", in_be32(R++), PB_NBITS); in do_iopinfo()
148 binary("PA_DAT", in_be16(l++), PA_NBITS); in do_iopinfo()
149 binary("PB_DAT", in_be32(R++), PB_NBITS); in do_iopinfo()
159 binary("PC_DIR", in_be16(l++), PC_NBITS); in do_iopinfo()
160 binary("PD_DIR", in_be16(r++), PD_NBITS); in do_iopinfo()
161 binary("PC_PAR", in_be16(l++), PC_NBITS); in do_iopinfo()
162 binary("PD_PAR", in_be16(r++), PD_NBITS); in do_iopinfo()
[all …]
|
| /u-boot/board/Marvell/db-xc3-24g4xg/ |
| A D | README | 1 To generate binary.0 from Marvell's bin_hdr.elf use the following command
3 arm-softfloat-linux-gnueabi-objcopy -S -O binary bin_hdr.elf \
4 board/Marvell/db-xc3-24g4xg/binary.0
|
| /u-boot/ |
| A D | .gitattributes | 3 # Denote all files that are truly binary and should not be modified
4 *.bmp binary
5 *.ttf binary
|
| /u-boot/doc/board/intel/ |
| A D | galileo.rst | 7 Only one binary blob is needed for Remote Management Unit (RMU) within Intel
8 Quark SoC. Not like FSP, U-Boot does not call into the binary. The binary is
11 You can get the binary blob from Quark Board Support Package from Intel website:
|
| A D | crownbay.rst | 7 U-Boot support of Intel `Crown Bay`_ board relies on a binary blob called
13 install it on your host and locate the FSP binary blob. Note this platform
14 also requires a Chipset Micro Code (CMC) state machine binary to be present in
15 the SPI flash where u-boot.rom resides, and this CMC binary blob can be found
27 binary using any hex editor (eg: bvi). Go to the offset 0x1fcd8 of the FSP
28 binary, change the following five bytes values from orginally E8 42 FF FF FF
|
| /u-boot/tools/patman/ |
| A D | tools.py | 331 binary = kwargs.get('binary')
347 env=env, raise_on_error=False, binary=binary)
396 def ReadFile(fname, binary=True): argument
405 with open(Filename(fname), binary and 'rb' or 'r') as fd:
411 def WriteFile(fname, data, binary=True): argument
420 with open(Filename(fname), binary and 'wb' or 'w') as fd:
480 binary=True)
487 data = Run('gzip', '-c', fname, binary=True)
520 data = Run('lz4', '-dc', fname, binary=True)
524 data = ReadFile(outfname, binary=True)
[all …]
|
| A D | command.py | 35 def ToOutput(self, binary): argument
36 if not binary:
52 raise_on_error=True, cwd=None, binary=False, **kwargs): argument
104 return result.ToOutput(binary)
116 return result.ToOutput(binary)
|
| /u-boot/arch/x86/cpu/queensbay/ |
| A D | Kconfig | 29 bool "Add a Chipset Micro Code state machine binary"
31 Select this option to add a Chipset Micro Code state machine binary
42 binary in the board directory.
45 hex "Chipset Micro Code state machine binary location"
49 The location of the CMC binary is determined by a strap. It must be
52 The default base address of 0xfffb0000 indicates that the binary must
|
| /u-boot/board/mikrotik/crs3xx-98dx3236/ |
| A D | README | 20 Getting binary.0
22 binary.0 (DDR3 init phase) can be retrieved/extracted from the integrated bootloader on the SPI fla…
23 Then binary.0 can be replaced with the extracted blob.
|
| /u-boot/board/imgtec/boston/ |
| A D | config.mk | 5 $< -binary \
6 -fill 0x00 -within $< -binary -range-pad 16 \
|
| /u-boot/arch/x86/cpu/quark/ |
| A D | Kconfig | 26 bool "Add a Remote Management Unit (RMU) binary"
29 Select this option to add a Remote Management Unit (RMU) binary
36 string "Remote Management Unit (RMU) binary filename"
41 binary in the board directory.
44 hex "Remote Management Unit (RMU) binary location"
48 The location of the RMU binary is determined by a strap. It must be
51 The default base address of 0xfff00000 indicates that the binary must
|
| /u-boot/board/freescale/imx8qm_mek/ |
| A D | README | 6 - Build the ARM Trusted firmware binary
9 - Flash the binary into the SD card
45 Flash the binary into the SD card
48 Burn the flash.bin binary to SD card offset 32KB:
|
| /u-boot/doc/board/google/ |
| A D | chromebook_link.rst | 7 First, you need the following binary blobs:
14 You can get these binary blobs by::
27 Make sure all these binary blobs are put in the board directory.
|
| /u-boot/doc/board/freescale/ |
| A D | imx8qxp_mek.rst | 11 - Build the ARM Trusted firmware binary
14 - Flash the binary into the SD card
55 Flash the binary into the SD card
58 Burn the flash.bin binary to SD card offset 32KB:
|
| /u-boot/arch/arm/mach-k3/ |
| A D | config_secure.mk | 8 ifneq ($(wildcard $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh),)
9 cmd_k3secureimg = $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh \
|
| /u-boot/doc/board/toradex/ |
| A D | apalix-imx8x.rst | 9 - Build the ARM trusted firmware binary
12 - Load U-Boot binary using uuu
13 - Flash U-Boot binary into the eMMC
66 Burn the ``u-boot-dtb.imx`` binary to the primary eMMC hardware boot area
|
| A D | colibri-imx8x.rst | 9 - Build the ARM trusted firmware binary
12 - Load U-Boot binary using uuu
13 - Flash U-Boot binary into the eMMC
75 Burn the ``u-boot-dtb.imx`` binary to the primary eMMC hardware boot area partition:
|
| A D | apalix-imx8.rst | 9 - Build the ARM trusted firmware binary
12 - Load U-Boot binary using uuu
13 - Flash U-Boot binary into the eMMC
74 Burn the ``u-boot-dtb.imx`` binary to the primary eMMC hardware boot area
|
| /u-boot/doc/board/advantech/ |
| A D | imx8qm-rom7720-a1.rst | 9 - Build the ARM Trusted firmware binary
14 - Flash the binary into the SD card
63 Flash the binary into the SD card
66 Burn the flash.bin binary to SD card offset 32KB:
|
| /u-boot/doc/ |
| A D | README.ti-secure | 8 and combined with various headers, certificates, and other binary images.
125 The output binary images should be used in place of the standard
126 non-secure binary images (see the platform-specific user's guides
149 loader binary file (only u-boot.bin is currently supported on
153 The output binary images should be used in place of the standard
154 non-secure binary images (see the platform-specific user's guides
184 and CONFIG_SPL_LOAD_FIT). With these configurations the binary
201 an input binary image:
203 ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh
219 Invoking the secure-binary-image script for Secure Devices
[all …]
|
| A D | README.rockusb | 40 to flash U-Boot image use below command. U-Boot binary is made by mkimage.
41 see doc/README.rockchip for more detail about how to get U-Boot binary.
43 sudo rkdeveloptool wl 64 <U-Boot binary>
|
| /u-boot/arch/arm/mach-keystone/ |
| A D | config.mk | 23 OBJCOPYFLAGS_u-boot-spi.gph = -I binary -O binary --pad-to=$(CONFIG_SPL_PAD_TO) \
|
| /u-boot/doc/usage/ |
| A D | fdt_overlays.rst | 28 Building a binary device-tree overlay follows the same process as building a
29 traditional binary device-tree. For example:
94 2. Load the base binary device-tree and the binary device-tree overlay.
101 3. Set the base binary device-tree as the working fdt tree.
|
| /u-boot/board/freescale/mx7ulp_evk/ |
| A D | Makefile | 8 $(OBJCOPY) -O binary --gap-fill 0xff $< $@
|