{"id":343,"date":"2012-08-15T11:46:42","date_gmt":"2012-08-15T11:46:42","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=343"},"modified":"2012-08-15T11:46:42","modified_gmt":"2012-08-15T11:46:42","slug":"apc-final-u-boot-tests-for-the-time-being","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=343","title":{"rendered":"APC – Final U-Boot tests, for the time being..?"},"content":{"rendered":"

Just to finally confirm that the U-Boot parameters were not in any way affection the APC boot – and therefore that the problem was in the APC’s kernel configuration, probably with the CONFIG_CMDLINE<\/strong> parameter in the original kernel’s .config<\/strong> file – I removed all<\/strong> the U-Boot parameters, as follows:<\/p>\n

WMT # setenv wmt.display.logoaddr; setenv logocmd; setenv wmt.gpo.lcd; setenv wmt.i2c.param; setenv wmt.eth.param; setenv wmt.ui.storage; setenv wmt.vd.debug; setenv wmt.camera.param; setenv wmt.gpo.cmos; setenv wmt.webview.param; setenv wmt.audio.i2s; setenv wmt.audio.rate; setenv wmt.pwbn.param; setenv wmt.l2c.param; setenv wmt.display.hdmi.vmode; setenv wmt.sd0.param; setenv wmt.sd1.param; setenv wmt.sd2.param; setenv wmt.ge.param; setenv android_bootargs; setenv wmt.mali.param; setenv wmt.wifi.param; setenv wmt.gpo.wifi; setenv wmt.nfc.mtd.u-boot-logo; setenv wmt.nfc.mtd.kernel-logo; setenv wmt.plla.param; setenv wmt.io.bat; setenv wmt.io.ts;\n\nWMT # setenv wmt.io.gsensor; setenv wmt.usb.param; setenv wmt.camera.i2c_gpio; setenv memtotal; setenv mmcid; setenv mbsize; setenv scriptcmd; setenv logocmd; setenv mmcargs; setenv mmcboot; setenv nandargs; setenv nandboot; setenv bootcmd; setenv kernel-NAND_mtd; setenv kernel-NAND_ofs; setenv kernel-NAND_len; setenv initrd-NAND_mtd; setenv initrd-NAND_ofs; setenv initrd-NAND_len; setenv filesystem-NAND_mtd; setenv filesystem-NAND_ofs; setenv filesystem-NAND_len; setenv stdin; setenv stdout; setenv stderr; setenv ver; setenv mmcboot; setenv usbboot; setenv filesystem-mmc_mtd; setenv filesize; setenv uboot_usb; setenv ipaddr; setenv ethaddr; setenv serverip; setenv gatewayip; setenv netmask; setenv usbargs;\n\n- got message:\nCan't delete \"stdin\"\nCan't delete \"stdout\"\nCan't delete \"stderr\"\n\nWMT # printenv\nstdin=serial\nstdout=serial\nstderr=serial<\/pre>\n
The command has to be split into two parts, as there appears to be a limit to the length of a single U-Boot command..<\/p>\n
I then entered the minimum<\/em> U-Boot parameters necessary for USB boot, and then booted the APC.<\/p>\n
WMT # setenv wmt.usb.param “11:3”<\/strong><\/p>\n
WMT # usb reset<\/strong><\/p>\n
WMT # root=\/dev\/sdb2<\/strong><\/p>\n
WMT # rootfstype=ext2<\/strong><\/p>\n
WMT # fatload usb 1:1 0x1000000 uzImage.bin 400000<\/strong><\/p>\n
WMT # fatload usb 1:1 0x1400000 initrd.gz 400000<\/strong><\/p>\n
WMT # bootm 0x1000000<\/strong><\/p>\n
The result was a kernel panic, as before, as the system was – once again – only expecting a rootfs on on of the \/dev\/mtdblockNN devices..<\/p>\n
There seems little that can now be done to fix this at the moment, as the only solution would be a different version of the APC kernel that does not have the ‘root=<\/strong> ‘ parameter hard-coded at compile time.\u00a0\u00a0\u00a0 Of course, the best solution would be a complete set of source code for the entire<\/em><\/strong> kernel, including WMT drivers..<\/p>\n","protected":false},"excerpt":{"rendered":"
Just to finally confirm that the U-Boot parameters were not in any way affection the APC boot – and therefore that the problem was in the APC’s kernel configuration, probably with the CONFIG_CMDLINE parameter in the original kernel’s .config file – I removed all the U-Boot parameters, as follows: WMT # setenv wmt.display.logoaddr; setenv logocmd; setenv wmt.gpo.lcd; …<\/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":[3,5,6,11,14,16,19,20],"tags":[89,101,116,1173,233,327],"class_list":["post-343","post","type-post","status-publish","format-standard","hentry","category-apc","category-compilation","category-crash-and-burn","category-hacks","category-kernel","category-linux-arm","category-opinion","category-performance-2","tag-apc-2","tag-boot","tag-closed-source","tag-kernel","tag-kernel-panic","tag-rootfs"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/343","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=343"}],"version-history":[{"count":0,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/343\/revisions"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=343"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=343"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=343"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}