| /rk3399_rockchip-uboot/tools/easylogo/ |
| H A D | easylogo.c | 149 int image_load_tga (image_t * image, char *filename) in image_load_tga() argument 170 image->width = header.ImageWidth; in image_load_tga() 171 image->height = header.ImageHeight; in image_load_tga() 175 image->yuyv = 0; in image_load_tga() 176 image->palette_size = 0; in image_load_tga() 177 image->palette = NULL; in image_load_tga() 185 image->bpp = header.ImagePixelSize; in image_load_tga() 186 image->pixel_size = ((image->bpp - 1) / 8) + 1; in image_load_tga() 187 image->pixels = image->width * image->height; in image_load_tga() 188 image->size = image->pixels * image->pixel_size; in image_load_tga() [all …]
|
| /rk3399_rockchip-uboot/tools/ |
| H A D | ifdtool.c | 49 static struct fdbar_t *find_fd(char *image, int size) in find_fd() argument 54 for (ptr = (uint32_t *)image, end = ptr + size / 4; ptr < end; ptr++) { in find_fd() 65 (char *)ptr - image); in find_fd() 386 static int dump_fd(char *image, int size) in dump_fd() argument 388 struct fdbar_t *fdb = find_fd(image, size); in dump_fd() 415 (image + ((fdb->flumap1 & 0xff) << 4)), in dump_fd() 417 dump_oem((uint8_t *)image + 0xf00); in dump_fd() 418 dump_frba((struct frba_t *)(image + (((fdb->flmap0 >> 16) & 0xff) in dump_fd() 420 dump_fcba((struct fcba_t *)(image + (((fdb->flmap0) & 0xff) << 4))); in dump_fd() 422 (image + (((fdb->flmap1 >> 16) & 0xff) << 4))); in dump_fd() [all …]
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.ti-secure | 4 Secure TI devices require a boot image that is authenticated by ROM 6 device is essentially useless. In order to create a valid boot image for 7 a secure device from TI, the initial public software image must be signed 10 Information on the details on the complete boot image format can be obtained 27 viable boot image. The build process will look for the environment 32 bootable image was not created. 34 Within the SECDEV package exists an image creation script: 36 ${TI_SECURE_DEV_PKG}/scripts/create-boot-image.sh 39 boot image formats and requirements differ between secure SOC from TI, 44 package for creating a bootable SPL image for secure TI devices. [all …]
|
| H A D | README.commands.spl | 1 The spl command is used to export a boot parameter image to RAM. Later 6 used. (kernel image, initrd-image, fdt-image etc.) 20 nand read 0x82000000 0x280000 0x400000 /* Read kernel image from NAND*/ 23 nand write 0x80000100 0x680000 0x20000 /* write the image - one page */ 27 nand read 0x82000000 0x280000 0x400000 /* Read kernel image from NAND*/
|
| H A D | README.nokia_rx51 | 8 NOLO is expecting a kernel image and will treat any image it finds in 11 appended to u-boot.bin at 0x40000. NOLO will load the entire image into 16 the appended kernel image will be booted using some generated and some 30 * 0. if keyboard is closed boot automatically attached kernel image 33 * 3. try boot from attached kernel image 53 * run attachboot - Boot attached kernel image (attached to U-Boot binary) 57 * run kernload - Load kernel image ${mmckernfile} 58 * run initrdload - Load initrd image ${mmcinitrdfile} 59 * run kernboot - Boot loaded kernel image 60 * run kerninitrdboot - Boot loaded kernel image with loaded initrd image [all …]
|
| H A D | README.nand-boot-ppc440 | 22 controller and the NAND controller so that the special U-Boot image can be 24 This special image is build in the directory "nand_spl". 36 Example: Build and install NAND boot image for Sequoia (440EPx): 41 b) Build image(s) 44 This will generate the SPL image in the "nand_spl" directory: 46 Also another image is created spanning a whole NAND block (16kBytes): 48 The main NAND U-Boot image is generated in the toplevel directory: 50 A combined image of u-boot-spl-16k.bin and u-boot.bin is also created: 53 This image should be programmed at offset 0 in the NAND flash:
|
| H A D | README.splashprepare | 7 image data before it is processed and sent to the frame buffer by 13 board specific splash image locations, routines for loading splash image from 24 formatted with a file system or a FIT image. In case of a filesystem, the splash 28 To enable loading the splash image from a FIT image, CONFIG_FIT must be 29 enabled. Struct splash_location field 'name' should match the splash image
|
| /rk3399_rockchip-uboot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
| H A D | README.qspi | 17 The difference between QSPI boot RCW image and NOR boot image is the PBI 21 RCW image should be written to the beginning of QSPI flash device. 26 => sf erase 0 +<size of rcw image> 28 => sf write <rcw image in memory> 0 <size of rcw image> 31 To get the QSPI image, build u-boot with QSPI config, for example, 32 <board_name>_qspi_defconfig. The image needed is u-boot-dtb.bin. 33 The u-boot image should be written to 0x10000(but 0x1000 for LS1043A, LS2080A). 37 => sf erase 10000 +<size of u-boot image> 39 => sf write <u-boot image in memory> 10000 <size of u-boot image>
|
| /rk3399_rockchip-uboot/tools/binman/ |
| H A D | control.py | 17 from image import Image 101 for image in images.values(): 106 image.GetEntryContents() 107 image.GetEntryPositions() 108 image.PackEntries() 109 image.CheckSize() 110 image.CheckEntries() 111 image.ProcessEntryContents() 112 image.BuildImage()
|
| H A D | README | 15 general way. Each SoC does what it needs to build an image, often packing or 26 required image layout. It uses this to work out what to place where. The 28 to read an image and extract its constituent parts. 36 place entries at a fixed location in the image, or fit them together with 46 Binman can also support incorporating filesystems in the image if required. 50 to be useful in other image-packaging situations. 57 parts. In many cases the various binaries which go into the image come from 60 in the firmware image, it is built elsewhere. 77 - Provides for a standard image description available in the build and at 79 - SoC-specific image-signing tools can be accomodated [all …]
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | command_syntax_extensions.txt | 26 1. bootm boot image at the current address, equivalent to 2,3,8 29 2. bootm <addr1> /* single image at <addr1> */ 30 3. bootm <addr1> /* multi-image at <addr1> */ 31 4. bootm <addr1> - /* multi-image at <addr1> */ 32 5. bootm <addr1> <addr2> /* single image at <addr1> */ 33 6. bootm <addr1> <addr2> <addr3> /* single image at <addr1> */ 34 7. bootm <addr1> - <addr3> /* single image at <addr1> */ 47 Ad. 1. This is equivalent to cases 2,3,8, depending on the type of image at 48 the current image address. 51 Ad. 2. Boot kernel image located at <addr1>. [all …]
|
| H A D | source_file_format.txt | 21 blob. Kernel image, FDT blob and possibly ramdisk image - all must be placed 58 .its - image tree source 59 .itb - flattened image tree blob 64 image source file (.its) and a set of data files. Image is created with the 66 compiler) to produce image tree blob (.itb). Resulting .itb file is the 80 - mkimage calls dtc to create .itb image and assures that 98 / o image-tree 99 |- description = "image description" 105 | o image@1 {...} 106 | o image@2 {...} [all …]
|
| H A D | howto.txt | 1 How to use images in the new image format 23 an image source file, which describes the contents of the image and defines 24 its various properties used during booting. By convention, image source file 27 the uImage (kernel, ramdisk, etc.) is specified in the image source file in the 28 form of paths to appropriate data files. The outcome of the image creation 37 - image source file (*.its) 38 - image data file(s) 41 Here's a graphical overview of the image creation and booting process: 43 image source file mkimage + dtc transfer to target 44 + ---------------> image file --------------------> bootm [all …]
|
| /rk3399_rockchip-uboot/scripts/ |
| H A D | avbtool.py | 1512 image = image_containing_descriptor 1515 image = ImageHandler(image_filename, read_only=True) 1521 root_digest, hash_tree = generate_hash_tree(image, self.image_size, 1533 image.seek(self.tree_offset) 1534 hash_tree_ondisk = image.read(self.tree_size) 1546 .format(self.partition_name, self.hash_algorithm, image.filename, 1680 image = image_containing_descriptor 1683 image = ImageHandler(image_filename, read_only=True) 1684 data = image.read(self.image_size) 1695 .format(self.partition_name, self.hash_algorithm, image.filename, [all …]
|
| /rk3399_rockchip-uboot/doc/SPL/ |
| H A D | README.spl-secure-boot | 13 The SPL image is responsible for loading the next stage boot loader, which is 14 the main u-boot image. For secure boot process on these platforms ROM verifies 15 SPL image, so to continue chain of trust SPL image verifies U-boot image using 17 (appended to U-boot image) to validate the U-boot binary just before passing
|
| /rk3399_rockchip-uboot/board/sbc8641d/ |
| H A D | README | 37 a recently installed non-functional image, to perform a recovery from 38 that non-functional image goes essentially as follows: 40 a) power down the board and jumper JP10 to select the functional image. 42 c) while on, using static precautions, move JP10 back to the failed image. 43 d) use "md fff00000" to confirm you are looking at the failed image 45 f) get new image, i.e. "tftp 200000 /somepath/u-boot.bin" 46 g) erase failed image: "erase FFF00000 FFF5FFFF" 47 h) copy in new image: "cp.b 200000 FFF00000 60000" 48 i) ensure new image is written: "md fff00000" 49 k) power cycle the board and confirm new image works.
|
| /rk3399_rockchip-uboot/tools/binman/etype/ |
| H A D | u_boot_ucode.py | 55 def __init__(self, image, etype, node): argument 56 Entry_blob.__init__(self, image, etype, node) 60 ucode_dest_entry = self.image.FindEntryType('u-boot-with-ucode-ptr') 66 ucode_dest_entry = self.image.FindEntryType('u-boot-spl-with-ucode-ptr') 72 fdt_entry = self.image.FindEntryType('u-boot-dtb-with-ucode')
|
| /rk3399_rockchip-uboot/arch/arm/mach-keystone/ |
| H A D | mon.c | 108 void *image = *p_image; in board_fit_image_post_process() local 110 if (strncmp(image + KS2_HS_SEC_TAG_OFFSET, "KEYS", 4)) { in board_fit_image_post_process() 115 result = k2_hs_bm_auth(KS2_AUTH_CMD, image); in board_fit_image_post_process() 127 memcpy(image, image + KS2_HS_SEC_HEADER_LEN, *p_size); in board_fit_image_post_process()
|
| /rk3399_rockchip-uboot/board/freescale/mpc8536ds/ |
| H A D | README | 10 The MPC8536E is capable of booting from NAND flash which uses the image 11 u-boot-nand.bin. This image contains two parts: a first stage image(also 12 call 4K NAND loader and a second stage image. The former is appended to 16 configure the L2SRAM, then copy the second stage image to L2SRAM and jump 17 to it. The second stage image is to configure all the hardware and boot up 25 second stage image. It's set in the board config file when boot from NAND 31 1. Building image 40 3. Flash image 50 initialize the eSPI/eSDHC controller, and loads the mian U-Boot image from 57 to find the image on the memory device, or where copy the main image to. The [all …]
|
| /rk3399_rockchip-uboot/board/freescale/p2041rdb/ |
| H A D | README | 14 1. Build image 18 2. Program image 42 1. Build image 47 Use PE tool to produce a image used to be programed to 48 SDCard which contains RCW and U-Boot image. 50 3. Program the PBL image to SDCard 65 1. Build image 70 Use PE tool to produce a image used to be programed to 71 SPI flash which contains RCW and U-Boot image. 73 3. Program the PBL image to SPI flash [all …]
|
| /rk3399_rockchip-uboot/drivers/video/drm/ |
| H A D | libnsbmp.c | 397 static bmp_result next_ico_image(ico_collection *ico, ico_image *image) { in next_ico_image() argument 398 bmp_create(&image->bmp, &ico->bitmap_callbacks); in next_ico_image() 399 image->next = ico->first; in next_ico_image() 400 ico->first = image; in next_ico_image() 453 ico_image *image; in ico_header_parse() local 454 image = calloc(1, sizeof(ico_image)); in ico_header_parse() 455 if (!image) in ico_header_parse() 457 result = next_ico_image(ico, image); in ico_header_parse() 460 image->bmp.width = read_uint8(data, 0); in ico_header_parse() 461 if (image->bmp.width == 0) in ico_header_parse() [all …]
|
| /rk3399_rockchip-uboot/board/freescale/mpc8349itx/ |
| H A D | README | 67 FE70_0000 Alternative U-Boot image 69 FEF0_0000 U-Boot image 74 FE00_0000 HRCW and U-Boot image 76 FE80_0000 Alternative HRCW and U-Boot image 81 FE00_0000 HRCW and U-Boot image 119 the U-Boot image. 127 the U-Boot image. 136 When the BMS bit in the HRCW is 0, the ITX will boot the U-Boot image 138 image at address FEF00000. 140 Therefore, just put a U-Boot image at both FE000000 and FEF00000 and [all …]
|
| /rk3399_rockchip-uboot/arch/arm/include/asm/mach-imx/ |
| H A D | imximage.cfg | 2 * i.MX image header offset values 17 /* Standard image header offset for NAND, SATA, SD, SPI flash. */ 19 /* Specific image header offset for booting from OneNAND. */ 21 /* Specific image header offset for booting from memory-mapped NOR. */
|
| /rk3399_rockchip-uboot/arch/arm/mach-omap2/ |
| H A D | sec-common.c | 90 static u32 find_sig_start(char *image, size_t size) in find_sig_start() argument 92 char *image_end = image + size; in find_sig_start() 97 while (--image_end > image) { in find_sig_start() 107 int secure_boot_verify_image(void **image, size_t *size) in secure_boot_verify_image() argument 115 rounddown((u32)*image, ARCH_DMA_MINALIGN), in secure_boot_verify_image() 116 roundup((u32)*image + *size, ARCH_DMA_MINALIGN)); in secure_boot_verify_image() 118 cert_addr = (uint32_t)*image; in secure_boot_verify_image() 119 sig_addr = find_sig_start((char *)*image, *size); in secure_boot_verify_image() 154 rounddown((u32)*image, ARCH_DMA_MINALIGN), in secure_boot_verify_image() 155 roundup((u32)*image + *size, ARCH_DMA_MINALIGN)); in secure_boot_verify_image()
|
| /rk3399_rockchip-uboot/board/rockchip/evb_rk3328/ |
| H A D | README | 21 * load and verify ATF image 22 * load and verify U-Boot image 54 Package image for miniloader 60 > mkdir image 61 > mv trust.img ./image/ 62 > mv uboot.img ./image/rk3328evb-uboot.bin 64 Flash image
|