Unfortunately, this also affects many USB HID / keyboard devices which would not be detected properly by U-Boot. Previous U-Boot versions (v2015.04 and older) have a problem supporting both USB 1.x (OHCI) and USB 2.0 (EHCI) at the same time - the latter includes the SUNXI_EHCI driver for Allwinner boards. OHCI and EHCI no longer conflict with each other (after the switch to device model). U-Boot v2015.07 and later shouldn't have problems supporting mixed USB 1.x/2.0 devices. Troubleshooting USB 1.x, USB keyboards (U-Boot < v2015.07) Look at Manual build howto for more details. Load mmc 0:1 0x43000000 $ above) that is generated as part of your kernel compilation. Setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait panic=10 create a file boot.cmd on the first partition (also check Kernel arguments for extra 'bootargs' options):.This article provides a collection of various scenarios for booting with U-Boot.įor getting these bits loaded onto the hardware, please refer to the respective howto:įor booting from SD with mainline U-Boot, the recommended way is: a SD card), but first U-Boot needs to be configured. The installation step will instruct how to install this on the installation media (e.g. When the build has completed, there will be u-boot-sunxi-with-spl.bin available in your u-boot tree. (When compiling natively, omit the CROSS_COMPILE=…) Make CROSS_COMPILE=aarch64-linux-gnu- B元1=/build/sun50i_a64/debug/bl31.bin Make CROSS_COMPILE=aarch64-linux-gnu- B元1=/build/sun50i_a64/debug/bl31.bin menuconfig Make CROSS_COMPILE=arm-linux-gnueabihf- menuconfigĪrm64 make CROSS_COMPILE=aarch64-linux-gnu- B元1=/build/sun50i_a64/debug/bl31.bin _defconfig Use menuconfing to play with the settings if you feel like it and then just build it:Īrmhf make CROSS_COMPILE=arm-linux-gnueabihf- _defconfig When you have determined what just configure U-Boot with a suitable default configuration. Make CROSS_COMPILE=aarch64-linux-gnu- PLAT= DEBUG=1 bl31 (See board/sunxi/README.sunxi64 in uboot sources for more infos.) PLAT=sun50i_a64 for example is suitable for H5 and A64 devices. In order to build U-Boot for a arm64 device you need to build Arm Trusted Firmware (ATF) as a prerequisite first. So, if your device is Cubieboard2 your build target is Cubieboard2_defconfig.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |