U-Boot

Uncompressing is not happening with zImage while booting up with u-boot

女生的网名这么多〃 提交于 2019-12-13 03:23:32
问题 I am working on microzed 7010 board, I have manualy compiled kernel, u-boot, fsbl, and .bit (vivado). Board is booting well with all setup (without using petalinux). But i have noticed that kernel is not Uncompressing kernel... with zImage nor uImage. whereas i can see bootlogs with that of petalinux's images. INPUT : 1 . zImage env is zImage=tftpboot 0x3000000 zImage && tftpboot 0x2A00000 system.dtb && bootz 0x3000000 - 0x2A00000 2 . Boot log is => Zynq> run zImage [2017-10-25 15:57:11

How to recover Intel Edison board

♀尐吖头ヾ 提交于 2019-12-13 02:48:44
问题 I had flashed Intel's pre-built src images on board by replacing u-boot.elf compiled with buildroot(having support for Edison board). But the board is stuck on FSBL(FSBL watchdog is continuously rebooting the board). I tried to flash on board, but on board no listener is present to serve flash operation (usually done by dfu utility in u-boot). So that I am not able to flash pre-built images again. By this present conditions, how can I bring my board up? How can I flash images again? INPUT :

Android firmware image components explanation

走远了吗. 提交于 2019-12-13 00:23:07
问题 Consider unpacking an android firmware image made for a Media box using for example the C code in this post or by 'Amlogic customization tool'. When I use the compiled C code with an android 7.1 image, I get these files: _aml_dtb.PARTITION aml_sdc_burn.ini aml_sdc_burn.UBOOT boot.PARTITION bootloader.PARTITION DDR.USB logo.PARTITION manifest.xml mesonl.dtb platform.conf recovery.PARTITION system.PARTITION UBOOT.USB Excluding some minor config files here, I know each of these images are a

u-boot flash probing not working(sf probe 0)

非 Y 不嫁゛ 提交于 2019-12-12 04:46:46
问题 I am trying to replace flash memory blocks however, i could not probe any flash: device>sf probe 0 SF: Unsupported flash IDs: manuf ff, jedec ffff, ext_jedec ffff Failed to initialize SPI flash at 0:0 Do you know how to handle this or any possible reasons or workaround? Thanks. 来源: https://stackoverflow.com/questions/46585542/u-boot-flash-probing-not-workingsf-probe-0

u-boot script to allow choosing between which rootfs part to boot (RAUC)

青春壹個敷衍的年華 提交于 2019-12-11 14:30:16
问题 I've managed to create an image with two rootfs partitions to run on my jetson nano with yocto/poky. I've followed the meta-rauc layer README and rauc user manual, to create the system.conf file and rauc_%.bbappend file and I am able to create bundles successfully. As I understand, I need some sort of u-boot script: In order to enable RAUC to switch the correct slot, its system configuration must specify the name of the respective slot from the bootloader’s perspective. You also have to set

Why u-boot can put global data's address into r9 register?

▼魔方 西西 提交于 2019-12-11 13:42:04
问题 When i look through u-boot source code, i found that it pass global data through r9 register like this register volatile gd_t *gd asm ("r9") So, i'm curious, how does u-boot ensure further codes won't use r9 register and corrupt the global data. Is there an options to tell compiler not to use specific register? 回答1: From Procedure Call Standard for the ARM Architecture: The role of register r9 is platform specific. A virtual platform may assign any role to this register and must document this

S5P4418开发板android源码下uboot和内核缺省文件的配置

久未见 提交于 2019-12-11 11:01:59
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> uboot 需要配置缺省文件,进入解压的源码目录 android,然后进入 u-boot 目录,如下 图所示。 如上图所示,如果是 1G 核心板,则使用“cp nsih-1G16b-4418.txt nsih.txt”命令,用 “nsih-1G16b-4418.txt ”文件覆盖“nsih.txt”;如果是 2G 核心板,则使用“cp nsih-2G16b-4418.txt nsih.txt”命令,用“nsih-2G16b-4418.txt ”文件覆盖“nsih.txt”。 内核需要配置缺省文件,进入解压出来的源码目录 android,然后进入 kernel 目录,使用 命令“cp -r config_for_iTOP4418_android_AR8031 .config”配置缺省文件。如果网卡芯 片是 RTL8211,则使用“cp -r config_for_iTOP4418_android_RTL8211 .config”,如下图 所示。 特别注意,如果用户想使用 menuconfig 配置缺省文件,请先在控制台输入“export ARCH=arm”,再使用 menuconfig 工具。否则默认配置的是 x86 平台,如下图所示。 另外,如果是 2G 核心板,则打开 kernel 目录下“vim arch

U-Boot之磁盘格式化分区命令实现

空扰寡人 提交于 2019-12-10 18:56:28
我的linux学习是建立在讯为的iTop-4412开发板上的,讯为开发板使用手册里面有教我们怎么利用U-Boot命令进行EMMC格式化分区,以前照着做是为了快速上手,但现在不行了,现在我要搞清楚它们到底是怎么实现的,下面开始我们的探索。 先看看格式化命令长什么样 fdisk -c 0 fatformat mmc 0:1 ext3format mmc 0:2 ext3format mmc 0:3 ext3format mmc 0:4 第一个命令 fdisk -c 0 ,我利用vscode的全局搜索功能搜索 fdisk ,在 cmd_mmc_disk.c 这个文件中找到了一个相关的函数,如下所示 int do_fdisk(cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]) { if ( argc == 3 || argc ==6 ) { if ( strcmp(argv[1], "-c") == 0 ) return create_mmc_fdisk(argc, argv); else if ( strcmp(argv[1], "-p") == 0 ) return print_mmc_part_info(argc, argv); } else { printf("Usage:\nfdisk <-p> <device_num>\n")

how sabre sd boots directly from uboot without SPL

情到浓时终转凉″ 提交于 2019-12-10 18:46:16
问题 sabre sd is based on imx-6 which has around 150Kb max internal RAM. however the uboot is large enough to fit in this space. How things work in this scenerio ? https://community.freescale.com/docs/DOC-95015 In this freescale documentation only uboot is used to create an SD card for sabre sd boot. 回答1: Short answer: it doesn't matter how small SRAM is since U-Boot itself apparently doesn't go anywhere near it. The major giveaway is that the mx6qsabresd config sets an entry point of 0x17800000,

nuc970 蛋疼的nfs启动问题!!

眉间皱痕 提交于 2019-12-10 03:25:26
1.linux内核配置支持nfs启动 2.服务器端配置NFS服务器(本人机器环境为Ubuntu18.04) 3.uboot启动参数设置(问题出在这里) 之前困扰了一个星期的nuc970评估板nfs启动问题,今天终于解决了,这里写个帖子记录下,避免之后忘记。 1.linux内核配置 我们的配置还是在官方给出的nuc970基本配置之上做一些改动。首先进入linux的内核目录,然后进行内核配置,和内核编译工作,具体命令如下。 make nuc972_defconfig make menuconfig 然后就会进入内核配置如图 对于系统从nfs启动我需要内核如下配置,这里有一个先后顺序,先配置IP:kernel level autoconfiguration,才会出现root file system on NFS的选项 这里最好勾选上下满的NFSv2,NFSv3,NFSv4的客户端支持选项。 到这里支持NFS启动的内核最小配置就已经完成了,接下来编译出内核,执行命令 make -j4 #这里的j4是指用4个核去编译 然后使用mkimage将linux内核打包 mkimage -A arm -O linux -T kernel -S crc32 -a 0x7fc0 -e 0x8000 -d image/970image 970nfsimage.bin 然后将内核烧录到nand flash