Nerten
-
Posts
12 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Nerten
-
-
I also found this method two days ago, but stacked on kernel booting. It won't boot.
-
As I said previously - on eMMC u-boot is stored in the hidden boot partition, it comes flashed on the eMMC by default and can be updated only with a special software or from system running on the board.
What if i boot from microsd? can I change u-boot on emmc?
-
If you wrote our image to eMMC (via SD card adapter), how is possible that you got this u-boot?
I don't know, maybe it because i burn this image through Etcher instead of dd?
-
Here is log for Armbian 5.25 with mainline kernel 4.9.7:
U-Boot 2012.07-00008-ge2d58a1-dirty (Aug 08 2014 - 20:57:19) for Exynos5422 CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7] APLL = 800MHz, KPLL = 800MHz MPLL = 532MHz, BPLL = 825MHz Board: XYREF5422 DRAM: 2 GiB WARNING: Caches not enabled TrustZone Enabled BSP BL1 version: ÿ/áâ VDD_KFC: 0x44 LDO19: 0xf2 Checking Boot Mode ... EMMC MMC: S5P_MSHC0: 0, S5P_MSHC2: 1 MMC Device 0: 14.7 GiB MMC Device 1: [ERROR] response timeout error : 00000104 cmd 1 Card did not respond to voltage select! *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press 'Enter' or 'Space' to stop autoboot: 1 0 ** Unable to use mmc 0:1 for fatload ** Loading file "/boot/boot.ini" from mmc device 0:1 xxa1 ** File not found /boot/boot.ini ext4load - load binary file from a Ext4 filesystem Usage: ext4load <interface> <dev[:part]> [addr] [filename] [bytes] - load binary file 'filename' from 'dev' on 'interface' to address 'addr' from ext4 filesystem ** Bad partition 2 ** ext4load - load binary file from a Ext4 filesystem Usage: ext4load <interface> <dev[:part]> [addr] [filename] [bytes] - load binary file 'filename' from 'dev' on 'interface' to address 'addr' from ext4 filesystem >>> Load Boot Script from mmc 0:1 <<< ** Unable to use mmc 0:1 for fatload ** >>> Load Boot Script from mmc 0:2 <<< ** Partition 2 not valid on device 0 ** ** Unable to use mmc 0:2 for fatload ** >>> Run Default Bootcmd <<< reading kernel..device 0 Start 1263, Count 16384 MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Start 17647, Count 2048 MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK completed Bad Linux ARM zImage magic! Exynos5422 #
-
You burn SD card and install to eMMC?
I have eMMC 16gb with micro-sd adapter and microsd-usb card reader.
-
Here is log from fresh-installed to emmc Armbian 5.25:
U-Boot 2012.07-00008-ge2d58a1-dirty (Aug 08 2014 - 20:57:19) for Exynos5422 CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7] APLL = 800MHz, KPLL = 800MHz MPLL = 532MHz, BPLL = 825MHz Board: XYREF5422 DRAM: 2 GiB WARNING: Caches not enabled TrustZone Enabled BSP BL1 version: ÿ/áâ VDD_KFC: 0x44 LDO19: 0xf2 Checking Boot Mode ... EMMC MMC: S5P_MSHC0: 0, S5P_MSHC2: 1 MMC Device 0: 14.7 GiB MMC Device 1: [ERROR] response timeout error : 00000104 cmd 1 Card did not respond to voltage select! *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press 'Enter' or 'Space' to stop autoboot: 1 0 ** Unable to use mmc 0:1 for fatload ** Loading file "/boot/boot.ini" from mmc device 0:1 xxa1 9509 bytes read Loading boot.ini from ext4 0:1 Find boot.ini file from FAT/Ext4 Area!! boot.ini command = setenv rootdev "/dev/mmcblk0p1" boot.ini command = setenv initrd_high "0xffffffff" boot.ini command = setenv fdt_high "0xffffffff" boot.ini command = setenv macaddr "00:1e:06:61:7a:55 boot.ini command = setenv bootrootfs "console=tty1 loglevel=1 root=${rootdev} rootwait ro fsck.repair=yes" boot.ini command = setenv vout "hdmi" boot.ini command = setenv cecenable "false" # false or true boot.ini command = setenv governor "performance" boot.ini command = setenv HPD "true" boot.ini command = setenv hdmi_tx_amp_lvl "31" boot.ini command = setenv hdmi_tx_lvl_ch0 "3" boot.ini command = setenv hdmi_tx_lvl_ch1 "3" boot.ini command = setenv hdmi_tx_lvl_ch2 "3" boot.ini command = setenv hdmi_tx_emp_lvl "6" boot.ini command = setenv hdmi_clk_amp_lvl "31" boot.ini command = setenv hdmi_tx_res "0" boot.ini command = setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}" boot.ini command = ext4load mmc 0:1 0x40008000 /boot/zImage || fatload mmc 0:1 0x40008000 zImage || ext4load mmc 0:1 0x40008000 zImage Loading file "/boot/zImage" from mmc device 0:1 xxa1 3392720 bytes read boot.ini command = ext4load mmc 0:1 0x42000000 /boot/uInitrd || fatload mmc 0:1 0x42000000 uInitrd || ext4load mmc 0:1 0x42000000 uInitrd Loading file "/boot/uInitrd" from mmc device 0:1 xxa1 6351073 bytes read boot.ini command = ext4load mmc 0:1 0x44000000 /boot/dtb/exynos5422-odroidxu3.dtb || fatload mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb || ext4load mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb Loading file "/boot/dtb/exynos5422-odroidxu3.dtb" from mmc device 0:1 xxa1 52006 bytes read boot.ini command = fdt addr 0x44000000 boot.ini command = if test "${cecenable}" = "false"; then fdt rm /cec@101B0000; fi boot.ini command = setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control} ${extraargs}" boot.ini command = bootz 0x40008000 0x42000000 0x44000000 ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6351009 Bytes = 6.1 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 Using Device Tree in place at 44000000, end 4400fb25 Starting kernel ...
-
Changing console output to serial also may help.
What i must do to do this?
-
https://www.armbian.com/odroid-xu4
written on eMMC. Well, in worse case I'll need to get eMMC and see what's going on
Ok, just started to create backup from my system and going to install latest one.
-
@Nerten
This does not look to be Armbian boot, at least no recent.
It's Armbian, had installed 5.14, upgraded to 5.17 -> 5.20 -> 5.22 -> 5.25.
-
U-Boot 2012.07-00008-ge2d58a1-dirty (Aug 08 2014 - 20:57:19) for Exynos5422
CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7]
APLL = 800MHz, KPLL = 800MHz
MPLL = 532MHz, BPLL = 825MHz
Board: XYREF5422
DRAM: 2 GiB
WARNING: Caches not enabled
TrustZone Enabled BSP
BL1 version: ÿ/áâ
VDD_KFC: 0x44
LDO19: 0xf2
Checking Boot Mode ... EMMC
MMC: S5P_MSHC0: 0, S5P_MSHC2: 1
MMC Device 0: 14.7 GiB
MMC Device 1: there are pending interrupts 0x00000001
14.8 GiB
MMC Device 2: MMC Device 2 not found
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Press 'Enter' or 'Space' to stop autoboot: 1 0
reading boot.ini
8528 bytes read
Loading boot.ini from FAT
Find boot.ini file from FAT/Ext4 Area!!
boot.ini command = setenv initrd_high "0xffffffff"
boot.ini command = setenv fdt_high "0xffffffff"
boot.ini command = setenv macaddr "00:1e:06:61:7a:55
boot.ini command = setenv bootrootfs "console=tty1 loglevel=1 root=/dev/mmcblk0p2 rootwait ro fsck.repair=yes"
boot.ini command = setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb; bootz 0x40008000 0x44000000"
boot.ini command = setenv vout "hdmi"
boot.ini command = setenv governor "performance"
boot.ini command = setenv HPD "true"
boot.ini command = setenv hdmi_tx_amp_lvl "31"
boot.ini command = setenv hdmi_tx_lvl_ch0 "3"
boot.ini command = setenv hdmi_tx_lvl_ch1 "3"
boot.ini command = setenv hdmi_tx_lvl_ch2 "3"
boot.ini command = setenv hdmi_tx_emp_lvl "6"
boot.ini command = setenv hdmi_clk_amp_lvl "31"
boot.ini command = setenv hdmi_tx_res "0"
boot.ini command = setenv hdmi_phy_control "hdmi_tx_amp_lvl=${hdmi_tx_amp_lvl} hdmi_tx_lvl_ch0=${hdmi_tx_lvl_ch0} hdmi_tx_lvl_ch1=${hdmi_tx_lvl_ch1} hdmi_tx_lvl_ch2=${hdmi_tx_lvl_ch2} hdmi_tx_emp_lvl=${hdmi_tx_emp_lvl} hdmi_clk_amp_lvl=${hdmi_clk_amp_lvl} hdmi_tx_res=${hdmi_tx_res} HPD=${HPD} vout=${vout}"
boot.ini command = setenv bootargs "${bootrootfs} ${videoconfig} smsc95xx.macaddr=${macaddr} governor=${governor} ${hdmi_phy_control}"
boot.ini command = boot
reading zImage
3392720 bytes read
reading dtb/exynos5422-odroidxu3.dtb
52006 bytes read
Starting kernel ...
-
Hi there.
Now I have this issue too. Today I had upgraded my system on XU4 from 5.22 to 5.25 and it stopped working.
We can't start to resolve this:
- without any logs
or
- without possibility to reproduce and catch logs. I don't have eMMC card for XU4
I have usb-uart and i can catch logs for you. Any help wanted!
Odroid XU4 - Ubuntu Xenial doesn't run on eMMC
in Odroid XU4
Posted
Oh, nevermind! It works perfectly.