{"id":1606,"date":"2015-11-10T04:49:38","date_gmt":"2015-11-10T04:49:38","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1606"},"modified":"2015-11-12T20:35:52","modified_gmt":"2015-11-12T20:35:52","slug":"arm64-dragonboard-410c-now-with-u-boot","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1606","title":{"rendered":"ARM64 – Dragonboard 410c – Now with U-Boot.."},"content":{"rendered":"

One of the shortcomings of the DragonBoard 410c was that it relied on the Android-phone-centric fastboot<\/em><\/strong> for any Kernel updates, but now there is a version of U-Boot available, thanks to Mateusz Kulikowski<\/strong>..<\/p>\n

This is very much a work-in-progress, but I thought I would give it a try…<\/p>\n

I started with the version at https:\/\/github.com\/hallor\/u-boot\/tree\/dragonboard-2015.11.01<\/a>, and made some modifications to get it working on my 410c (Fedora 23, EXT4 rootfs, boot from SDCard)..<\/p>\n

I should emphasize that I am a complete novice when it comes to hacking u-boot, and there may well be a better way of doing all this, but this worked, for me..<\/p>\n

Modify u-boot\/include\/configs\/dragonboard.h<\/span><\/strong><\/p>\n

add:
\n#define CONFIG_CMD_EXT4 \/* EXT4 support *\/
\n<\/span><\/strong>#define CONFIG_SYS_BOOTM_LEN (16 << 20) \/* Increase max image size *\/<\/span><\/strong><\/p>\n

And.. as the SAVEENV command was not included, for some reason – and I could not work out how to reenable it – I hard-coded the boot parameters, as follows:
\nafter:
\n\/* Environment – Boot*\/<\/span><\/strong>
\n#define CONFIG_BOOTDELAY 5 \/* autoboot after 5 seconds *\/
\n<\/span><\/strong>insert:<\/span><\/span>
\n#define CONFIG_BOOTARGS “root=\/dev\/mmcblk1p1 rw rootwait console=tty0 console=ttyMSM0,115200n8 rootfs=ext4 noinitrd selinux=0”<\/span><\/strong>
\n#define CONFIG_BOOTCOMMAND “ext4load mmc 1:1 0x90000000 \/boot\/uImage; ext4load mmc 1:1 0x89000000 \/boot\/apq8016-sbc.dtb; bootm 0x90000000 – 0x89000000; ”
\n<\/span><\/strong>< each of these #defines should be a single line..>
\n<\/strong><\/span><\/p>\n

Then:<\/p>\n

#] make distclean<\/strong><\/span>\r\n#] make dragonboard_config<\/strong><\/span>\r\n#] make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-<\/strong><\/span>  (or whatever cross-compiler you are using..)<\/pre>\n
And make a ‘fake kernel’ image to use with fastboot, to install u-boot…<\/p>\n
mkbootimg<\/em><\/strong> can be found at git:\/\/codeaurora.org\/quic\/kernel\/skales<\/strong><\/span>, and I just installed it in \/opt<\/strong>, and then added the location to the $PATH<\/em><\/strong>..<\/p>\n
#] export PATH=\/opt\/skales:$PATH\r\n#] mkbootimg --kernel=u-boot.bin --output=u-boot.img --dt=fake_dt --pagesize 2048 --base 0x80000000 --ramdisk=fake_ramdisk --cmdline=\"\"\r\n<\/span><\/strong>(su, and enable fastboot on the 410c, after connecting the USB cable, etc. etc..)<\/span>\r\n#] fastboot flash boot u-boot.img\r\n<\/span><\/strong><\/pre>\n
So.. the fastboot-enabled ‘boot’ image is not the kernel now, but actually the u-boot executable.. You will only need to use fastboot to install\/update u-boot.<\/p>\n
The kernel can now be compiled on the Dragonboard, now, but the arm64 kernels do not include any built-in #make uImage<\/span><\/strong> or #make zImage<\/span><\/strong> capability, and so you will need to create a uImage after the #make Image<\/span><\/strong> kernel compile..<\/p>\n
#] make defconfig <\/span><\/strong>(if necessary..)<\/span>\r\n#] make xconfig <\/span><\/strong>(select qcom...)<\/span>\r\n#] make -j5 Image<\/span><\/strong>\r\n#] make dtbs<\/span><\/strong>\r\n#] cp arch\/arm64\/boot\/dts\/qcom\/apq8016-sbc.dtb \/boot<\/span><\/strong>\r\n#] make -j5 modules<\/span><\/strong>\r\n#] make modules_install<\/span><\/strong>\r\n#] make firmware_install<\/span><\/strong>\r\n#] cp System.map \/boot<\/span><\/strong>\r\n#] cp arch\/arm64\/boot\/Image \/boot<\/span><\/strong><\/pre>\n
Then in the \/boot directory:<\/p>\n
#] mkimage -A arm64 -O linux -C none -T kernel -a 0x80080000 -e 0x80080000 -n Dragonboard -d Image uImage<\/span><\/strong><\/pre>\n
U-boot boot sequence – after u-boot is loaded by the old android bootloader:<\/p>\n
U-Boot 2015.10-00449-g8e0b5c4-dirty (Nov 09 2015 - 14:13:46 -0800)<\/strong><\/span>\r\nQualcomm-DragonBoard 410C<\/strong><\/span>\r\n\r\nDRAM: 986 MiB<\/strong><\/span>\r\nMMC: msm_sdhci: 0, msm_sdhci: 1<\/strong><\/span>\r\nUsing default environment<\/strong><\/span>\r\n\r\nIn: serial<\/strong><\/span>\r\nOut: serial<\/strong><\/span>\r\nErr: serial<\/strong><\/span>\r\nNet: Net Initialization Skipped<\/strong><\/span>\r\nNo ethernet found.<\/strong><\/span>\r\nHit any key to stop autoboot: 0<\/strong><\/span>\r\n=> printenv<\/strong><\/span>\r\nbaudrate=115200<\/strong><\/span>\r\nbootargs=root=\/dev\/mmcblk1p1 rw rootwait console=tty0 console=ttyMSM0,115200n8 rootfs=ext4 noinitrd selinux=0<\/strong><\/span>\r\nbootcmd=ext4load mmc 1:1 0x90000000 \/boot\/uImage; ext4load mmc 1:1 0x89000000 \/boot\/apq8016-sbc.dtb; bootm 0x90000000 - 0x89000000;<\/strong><\/span>\r\nbootdelay=5<\/strong><\/span>\r\nstderr=serial<\/strong><\/span>\r\nstdin=serial<\/strong><\/span>\r\nstdout=serial<\/strong><\/span>\r\n\r\nEnvironment size: 327\/4092 bytes<\/strong><\/span>\r\n=> boot<\/strong><\/span><\/pre>\n
<< Linux Kernel boots… >><\/p>\n
.................<\/strong><\/span>\r\n[ OK ] Reached target Network is Online.<\/strong><\/span>\r\n Starting LSB: Start or stop the Webmin server...<\/strong><\/span>\r\n Starting rolekit - role server...<\/strong><\/span>\r\n Starting Availability of block devices...<\/strong><\/span>\r\n[ OK ] Reached target Remote File Systems (Pre).<\/strong><\/span>\r\n[ OK ] Reached target Remote File Systems.<\/strong><\/span>\r\n Starting Permit User Sessions...<\/strong><\/span>\r\n[ OK ] Started OpenSSH server daemon.<\/strong><\/span>\r\n Starting OpenSSH server daemon...<\/strong><\/span>\r\n[ OK ] Started Availability of block devices.<\/strong><\/span>\r\n[ OK ] Started Permit User Sessions.<\/strong><\/span>\r\n Starting Terminate Plymouth Boot Screen...<\/strong><\/span>\r\n[ OK ] Started Command Scheduler.<\/strong><\/span>\r\n Starting Command Scheduler...<\/strong><\/span>\r\n Starting Wait for Plymouth Boot Screen to Quit...<\/strong><\/span>\r\n\r\nFedora 23 (Twenty Three)<\/strong><\/span>\r\nKernel 4.2.0 on an aarch64 (ttyMSM0)<\/strong><\/span>\r\n\r\nrg410c login:<\/strong><\/span><\/pre>\n
So.. I now have a Dragonboard 410c that I can compile the kernel on, and boot, without having to cross-compile or connect USB cables!<\/p>\n
Robert Gadsdon.\u00a0\u00a0 November 9, 2015.
\nUpdated November 12, to add info on mkbootimg..
\n<\/em><\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
One of the shortcomings of the DragonBoard 410c was that it relied on the Android-phone-centric fastboot for any Kernel updates, but now there is a version of U-Boot available, thanks to Mateusz Kulikowski.. This is very much a work-in-progress, but I thought I would give it a try… I started with the version at https:\/\/github.com\/hallor\/u-boot\/tree\/dragonboard-2015.11.01, and made …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1132,5,6,1130,10,11,14,16,937],"tags":[1133,1137,182,1175,372],"class_list":["post-1606","post","type-post","status-publish","format-standard","hentry","category-aarch64","category-compilation","category-crash-and-burn","category-dragonboard","category-fedora","category-hacks","category-kernel","category-linux-arm","category-u-boot-2","tag-arm64","tag-dragonboard-410c","tag-hack","tag-success","tag-u-boot"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1606","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1606"}],"version-history":[{"count":4,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1606\/revisions"}],"predecessor-version":[{"id":1614,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1606\/revisions\/1614"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1606"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1606"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}