QEMU启动arm u-boot

最新推荐文章于 2024-06-05 01:38:33 发布
最新推荐文章于 2024-06-05 01:38:33 发布
阅读量3.4k 收藏 7
点赞数 5
分类专栏： arm_linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/pkokocl/article/details/108632698
版权

0、环境  ubuntu16.04

Linux aikou 4.15.0-112-generic #113~16.04.1-Ubuntu SMP Fri Jul 10 04:37:08 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

1、安装交叉编译工具

sudo apt-get install gcc-arm-linux-gnueabi

2、下载u-boot

  下载地址：http://ftp.denx.de/pub/u-boot/，选择的版本是u-boot-2020.07

3、解压缩，并切换到u-boot目录

tar xvf u-boot-2020.07.tar.bz2
cd u-boot-2020.07

4、编译u-boot

 export ARCH=arm  CROSS_COMPILE=arm-linux-gnueabi-
 make vexpress_ca9x4_defconfig
 make -j16

 此处我们使用vexpress_ca9x4_defconfig 默认配置。

4.1 gcc 版本错误

执行上面的编译命令，提示如下错误 *** Your GCC is older than 6.0 and is not supported 错误

scripts/kconfig/conf  --syncconfig Kconfig
  UPD     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk.dep
  GEN     include/autoconf.mk
  UPD     include/generated/dt.h
  UPD     include/generated/timestamp_autogenerated.h
*** Your GCC is older than 6.0 and is not supported
arch/arm/config.mk:66: recipe for target 'checkgcc6' failed
make: *** [checkgcc6] Error 1
make: *** Waiting for unfinished jobs....
  UPD     include/config/uboot.release
make: *** wait: No child processes.  Stop.

 查看交叉编译环境gcc的版本是5.4.0 低于要求的6.0


kou@aikou:~$ arm-linux-gnueabi-gcc --version
arm-linux-gnueabi-gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

解决办法是升级arm-linux-gnueabi-gcc的版本到要求的6.0以上。也可以如下解决，屏蔽掉 u-boot-2020.07/arch/arm/config.mk文件中的61，62,65-70行的代码，不检查6.0的版本

cd .../u-boot-2020.07/arch/arm
vi config.mk

     52
     53 checkthumb:
     54         @if test "$(call cc-name)" = "gcc" -a \
     55                         "$(call cc-version)" -lt "0404"; then \
     56                 echo -n '*** Your GCC does not produce working '; \
     57                 echo 'binaries in THUMB mode.'; \
     58                 echo '*** Your board is configured for THUMB mode.'; \
     59                 false; \
     60         fi
     61 #else
     62 #archprepare: checkgcc6
     63 endif
     64
     65 #checkgcc6:
     66 #       @if test "$(call cc-name)" = "gcc" -a \
     67 #                       "$(call cc-version)" -lt "0600"; then \
     68 #               echo '*** Your GCC is older than 6.0 and is not supported'; \
     69 #               false; \
     70 #       fi

4.2 This board does not use CONFIG_DM 

继续编译，编译可完成，但出现如下告警：

OBJCOPY u-boot.srec
  OBJCOPY u-boot-nodtb.bin
  SYM     u-boot.sym
  COPY    u-boot.bin
========================= WARNING ===========================
This board does not use CONFIG_DM. CONFIG_DM will be
compulsory starting with the v2020.01 release.
Failure to update may result in board removal.
See doc/driver-model/migration.rst for more info.
========================= WARNING ============================
This board does not use CONFIG_DM_MMC. Please update
the board to use CONFIG_DM_MMC before the v2019.04 release.
Failure to update by the deadline may result in board removal.
See doc/driver-model/migration.rst for more info.
======================== WARNING==============================
This board does not use CONFIG_DM_ETH (Driver Model
for Ethernet drivers). Please update the board to use
CONFIG_DM_ETH before the v2020.07 release. Failure to
update by the deadline may result in board removal.
See doc/driver-model/migration.rst for more info.
==============================================================
  CFGCHK  u-boot.cfg

这三个告警是新的uboot版本强制要使用者三个配置，需开启。先不用管它

5、u-boot文件

至此，u-boot编译完成，在当前目录下，生成了u-boot相关的文件，如下。其中u-boot就是我们需要的文件

-rwxrwxr-x   1 kou kou 3215488 9月  16 22:45 u-boot
-rwxrwxr-x   1 kou kou  504804 9月  16 22:45 u-boot.bin
-rw-rw-r--   1 kou kou      49 9月  16 22:45 .u-boot.bin.cmd
-rw-rw-r--   1 kou kou    9014 9月  16 22:31 u-boot.cfg
-rw-rw-r--   1 kou kou    4993 9月  16 22:45 u-boot.cfg.configs
-rw-rw-r--   1 kou kou    1203 9月  16 22:45 .u-boot.cmd
-rw-rw-r--   1 kou kou    1719 9月  16 22:45 u-boot.lds
-rw-rw-r--   1 kou kou    5929 9月  16 22:45 .u-boot.lds.cmd
-rw-rw-r--   1 kou kou  466345 9月  16 22:45 u-boot.map
-rwxrwxr-x   1 kou kou  504804 9月  16 22:45 u-boot-nodtb.bin
-rw-rw-r--   1 kou kou     312 9月  16 22:45 .u-boot-nodtb.bin.cmd
-rwxrwxr-x   1 kou kou 1514538 9月  16 22:45 u-boot.srec
-rw-rw-r--   1 kou kou     298 9月  16 22:45 .u-boot.srec.cmd
-rw-rw-r--   1 kou kou  136154 9月  16 22:45 u-boot.sym
-rw-rw-r--   1 kou kou      67 9月  16 22:45 .u-boot.sym.cmd

6、QEMU中启动u-boot

用下面的命令启动

qemu-system-arm -M vexpress-a9 -kernel ./u-boot -nographic -m 128M -append "console=ttyAMA0"

 执行启动u-boot的命令，u-boot启动输出如下信息：

audio: Could not init `oss' audio driver


U-Boot 2020.07 (Sep 16 2020 - 22:45:36 +0800)

DRAM:  128 MiB
WARNING: Caches not enabled
Flash: 128 MiB
MMC:   MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   smc911x-0
Hit any key to stop autoboot:  0
MMC Device 1 not found
no mmc device at slot 1
Card did not respond to voltage select!
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (1 ms)
*** Warning: no boot file name; using '0A00020F.img'
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename '0A00020F.img'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-52-54-00-12-34-56
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/01-52-54-00-12-34-56'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00020F
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020F'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00020
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A0002
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0002'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A000
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A000'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A0
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
Config file not found
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
smc911x: MAC 52:54:00:12:34:56
smc911x: detected LAN9118 controller
smc911x: phy initialized
smc911x: MAC 52:54:00:12:34:56
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (1 ms)
Using smc911x-0 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
smc911x: MAC 52:54:00:12:34:56

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>

在这里输入 printenv 可输出环境变量：

TFTP error: trying to overwrite reserved memory...
smc911x: MAC 52:54:00:12:34:56
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>
=>
=> printenv
arch=arm
baudrate=38400
board=vexpress
board_name=vexpress
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_syslinux_conf=extlinux/extlinux.conf
boot_targets=mmc1 mmc0 pxe dhcp
bootargs=root=/dev/sda1 rw console=ttyAMA0,38400n8 mem=1024M mtdparts=armflash:1M@0x800000(uboot),7M@0x1000000(kernel),24M@0x2000000(initrd) mmci.fmax=190000 devtmpfs.mount=0 vmalloc=256M
bootcmd=run distro_bootcmd; run bootflash
bootcmd_dhcp=if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00010:UNDI:003000;setenv bootp_arch 0xa;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci;
bootcmd_mmc0=devnum=0; run mmc_boot
bootcmd_mmc1=devnum=1; run mmc_boot
bootcmd_pxe=dhcp; if pxe get; then pxe boot; fi
bootdelay=2
bootfile=boot.scr.uimg
bootflash=run flashargs; cp ${ramdisk_addr} ${ramdisk_addr_r} ${maxramdisk}; bootm ${kernel_addr} ${ramdisk_addr_r}
console=ttyAMA0,38400n8
cpu=armv7
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
dram=1024M
efi_dtb_prefixes=/ /dtb/ /dtb/current/
ethact=smc911x-0
ethaddr=52:54:00:12:34:56
fdtfile=vexpress-v2p-ca9.dtb
flashargs=setenv bootargs root=${root} console=${console} mem=${dram} mtdparts=${mtd} mmci.fmax=190000 devtmpfs.mount=0  vmalloc=256M
kernel_addr=0x44100000
kernel_addr_r=0x80008000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile}
loadaddr=0x80008000
maxramdisk=0x1800000
mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi
mtd=armflash:1M@0x800000(uboot),7M@0x1000000(kernel),24M@0x2000000(initrd)
pxefile_addr_r=0x88000000
ramdisk_addr=0x44800000
ramdisk_addr_r=0x61000000
root=/dev/sda1 rw
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist
scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x88000000
stderr=serial
stdin=serial
stdout=serial
ubifs_boot=env exists bootubipart || env set bootubipart UBI; env exists bootubivol || env set bootubivol boot; if ubi part ${bootubipart} && ubifsmount ubi${devnum}:${bootubivol}; then devtype=ubi; run scan_dev_for_boot; fi
vendor=armltd

Environment size: 4482/262140 bytes
=>

可见u-boot已经启动。但有不少错误。因为我们直接采用的是vexpress_ca9x4_defconfig 默认配置文件，并未修改。

下一篇写如何修改，去掉这些错误告警。

 

 

pkokocl
关注
  • 5
    点赞
  • 踩
  • 7
    收藏
    觉得还不错? 一键收藏
  • 3
    评论
专栏目录
U-boot中TFTP解释及nfs命令的小bug
BoArmy的专栏
03-09 1198
一、      概述       U-boot中的TFTP用于发送较小的文件。下层使用UDP协议，发送使用UDP 69端口，每次发送的最大分组为512 Bytes。发送双方采用超时重传机制。数据传输模式为octet模式（ 二进制模式　）。     在U-boot中使用tftp功能可以使用如下命令：             tftp  MemoryAddress  FileName
qemu下u-boot+kernel+rootfs完整启动移植手册
05-21
嵌入式开发中，较流行的虚拟开发板qemu，本文挡详细描述了在qemu下，通过加载bin文件(u-boot+linux内核+根文件系统)成功挂载根文件系统的流程，有问题可留言。
编译和运行qemu-uboot-arm64单板的Armbian系统
最新发布
陨石䧛的天际
06-05 894
编译和运行qemu-uboot-arm64单板的Armbian系统，解决u-boot下载失败的问题。
Debug uboot on QEMU ARM model with GDB
alex_mianmian的博客
05-10 369
u-boot runs on QEMU ARM model , we can start GDB server on QEMU with command line parameters '-s -S' as following: chunxie@chunxie-VirtualBox:~/uboot-mainline/u-boot$ qemu-system-arm -M vexpress-a9 ...
Qemu搭建ARM vexpress开发环境(二)----通过u-boot启动Linux内核
kunkliu的博客
04-02 755
gcc标签（空格分隔）： Qemu ARM Linux在上文《》中已经简单讲述了通过Qemu模拟直接启动Linux内核，并挂在SD卡根文件系统的方法，这种方法是直接启动内核，与实际应用中ARM板的启动方式：u-boot、kernel、rootfs有些不同。现在就来讲述下通过Qemu搭建通过u-boot启动Linux内核并挂载根文件系统的方法。
从0开始使用QEMU模拟ARM开发环境之uboot通过sd卡加载uImage
墨1024
02-05 4736
介绍如何让uboot通过sd卡加载uImage
使用QEMU启动uboot引导linux内核
个人学习记录
11-02 2217
上篇文章中实现了使用qemu启动uboot，本文实现使用qemu启动uboot引导内核的过程。
u-boot:git.qemu.orgu-boot.git的镜像
03-21
在提供的压缩包中，"u-boot-master"文件夹代表了u-boot项目的一个特定版本，可能是最新的稳定版或开发版。这个文件夹包含了源代码、构建脚本、配置文件等，可以用来编译和生成适用于特定平台的u-boot引导加载器。 ...
使用QEMU搭建U-boot+linux+NFS开发环境.zip
02-10
qemu-system-arm -m 512M -nographic -kernel u-boot.bin -append "root=/dev/nfs ip=dhcp nfsroot=<your_nfs_server_ip>:<exported_directory>" -device virtio-net-pci -boot c ``` 6. **运行QEMU**：执行上述...
qemu-5.0.0+u-boot+linux-5.4.95+gcc-linaro-6.5.0+busybox-1.32.1.zip
02-05
qemu-5.0.0、u-boot 源码、linux-5.4.95内核、gcc-linaro-6.5.0-2018.12-x86_64_arm-linux-gnueabihf交叉编译链、busybox-1.32.1 工具 文章 https://blog.csdn.net/leacock1991/article/details/113703897 使用资源
从0开始使用QEMU模拟ARM开发环境之定制Ubuntu rootfs（根文件系统）
墨1024
02-07 3984
QEMU定制Ubuntu rootfs（根文件系统）
移植u-boot-2019.10到jz2440
gzxb1995的博客
12-25 3526
目录前言1 u-boot简介2 第一步——根据自己的硬件修改u-boot2.1 移植的不同硬件层次2.2 选择合适的坯子2.3 将旧版本中支持SMDK2410的文件拷贝到新版u-boot2.3.1 拷贝s3c24x0目录2.3.2 拷贝smdk2410目录2.3.3 拷贝arch-s3c24x0目录2.3.4 拷贝零散分布的驱动源程序2.3.5 拷贝smdk2410.h2.3.6 拷贝smdk24...
U-Boot 之八 详解 Driver Model 架构、配置、命令、初始化流程
技术干货
02-27 5046
U-Boot 在 2014 年 4 月参考 Linux Kernel 的 Driver Model 设计并引入了自己的 Driver Model（DM） 这个驱动架构。这个驱动模型（DM）为驱动的定义和访问接口提供了统一的方法，提高了驱动之间的兼容性以及访问的标准性。
U-BOOT分析（二）之顶层Makefile文件(1)
u012826733的博客
12-14 1479
uboot顶层Makfile分析，介绍Makefile编译uboot的前期make设置,编译前的准备过程，config文件的解析，uboot 的编译等。
linux开启tftp服务,Linux tftp服务无法启动原因及解决方法
weixin_33908564的博客
05-02 1524
在linux下，不管使用的是哪一种super-server，inetd或者xinetd，默认情况下TFTP服务是禁用的，所以要修改文件来开启服务。根据(1)的安装方法，可以修改文件/etc/xinetd.d/tftp。主要是设置TFTP服务器的根目录，开启服务。修改后的文件如下：servicetftp{socket_type=dgramprotocol=udpwait=yesuser=r...
tftp配置方法及常见错误
热门推荐
一直走的专栏
03-08 1万+
之前也配置过tftp，但是没有做记录，导致今天再次配置的时候又出问题了，所以在这里记录一下 大部分内容都是参考别人的，这里只是综合了一下 一、tftp配置方法 1：sudo apt-get install tftp tftpd openbsd-inetd 特别指出很多文章里用的是netkit-inetd,但是实际下载时发现 这个软件是下不到的，特改用openbsd-inetd,实验效果不
u-boot移植（六）---代码修改---串口
dongbipi3785的博客
06-08 286
一、代码流程 1.1 串口代码 　　程序流程图如下； 　　 　　default_serial_console 执行的代码如下： 　　 　　 　　在JZ2440.H中有如下定义： 　　 　　则执行结构体s3c24xx_serial0_device，从而执行INIT_S3C_SERIAL_STRUCTURE(0, "s3ser0")： 　　 　　_serial_set...
uboot阶段无法使用tftp(或者nfs)挂载内核及设备树
唯有代码的博客
01-10 2111
今天在学习uboot系统移植时出现了一个问题，挂载无反应。先贴图 一开始我的反应是网络的问题，我就开始排查网络，测试uboot下开发板是否能ping虚拟机 发现是没有问题的，接下来我就想去试试虚拟机是否也能ping通开发板，当然我已经是完成我的开发板的网络配置。然后出现的情况是 发现并不能ping通开发板。于是我开始纳闷是否是我的网口以及网络配置出错了。针对于此我进行了以下几项排查工作： 1、开发板的网络环境搭建。 这里我使用的设备是台式机电脑，开发板，光猫一台，网线2条。（PS...
评论 3
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值