MICE Posted October 6, 2016 Posted October 6, 2016 I did a clean install of Armbian_5.20_Odroidc2_Debian_jessie_3.14.79.img i found that after installing updates: udev and libudev1 OdroidC2 with 128GB eMMC; stops working with a blue solid light after reboot twice and no response from the device. If i do the same install on a micro-sd card 1 UHS no problem :S I have my mail, irc, web and openvpn server running on this device. Please HELP!! apt-get install udev libudev1Preconfiguring packages ...(Reading database ... 44010 files and directories currently installed.)Preparing to unpack .../libudev1_215-17+deb8u5_arm64.deb ...Unpacking libudev1:arm64 (215-17+deb8u5) over (215-17+deb8u4) ...Setting up libudev1:arm64 (215-17+deb8u5) ...Processing triggers for libc-bin (2.19-18+deb8u6) ...(Reading database ... 44010 files and directories currently installed.)Preparing to unpack .../udev_215-17+deb8u5_arm64.deb ...locale: Cannot set LC_ALL to default locale: No such file or directoryUnpacking udev (215-17+deb8u5) over (215-17+deb8u4) ...Processing triggers for man-db (2.7.0.2-5) ...Processing triggers for systemd (215-17+deb8u4) ...Setting up udev (215-17+deb8u5) ...addgroup: The group `input' already exists as a system group. Exiting.update-initramfs: deferring update (trigger activated)Processing triggers for initramfs-tools (0.120+deb8u2) ...ln: failed to create hard link '/boot/initrd.img-3.14.79-odroidc2.dpkg-bak' => '/boot/initrd.img-3.14.79-odroidc2': Operation not permittedupdate-initramfs: Generating /boot/initrd.img-3.14.79-odroidc2
Igor Posted October 6, 2016 Posted October 6, 2016 I just issue an update to my eMMC driven C2, going from 5.16 to 5.20 without a problem. How exactly did you install to eMMC? Do you have a serial console?
MICE Posted October 6, 2016 Author Posted October 6, 2016 On 10/6/2016 at 12:15 PM, Igor said: I just issue an update to my eMMC driven C2, going from 5.16 to 5.20 without a problem. How exactly did you install to eMMC? Do you have a serial console? sudo dd if=Armbian_5.20_Odroidc2_Debian_jessie_3.14.79.img of=/dev/sdb bs=1M sync with a Transcend MicroSD reader USB3.0 and the eMMC Reader module that comes with the emmc module from the hardkernel site: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145622510341 it happens after the update and after rebooting twice
Igor Posted October 6, 2016 Posted October 6, 2016 I repeat the same with clean 5.20 install to eMMC, the exact same way and with the same gears. I only don't have 128Gb eMMC but 8gb which should not play any role. apt-get update apt-get upgrade reboot all fine next no boot ... true. I can take a look later ... This is the uart log: Reveal hidden contents [Reset cause: unknown] [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04] bl30: check_permit, count is 1 bl30: check_permit: ok! chipidLoad bl33 from eMMC, src: 0x00034200, des: 0x01000000, size: 0x00066de0 : ef be ad de d f0 ad ba ef be ad de not ES chip [0.174304 Inits done] secure task start! high task start! low task start! NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x1000000 INFO: BL3-1: Next image spsr = 0x3c9 U-Boot 2015.01 (Sep 15 2016 - 06:15:35) DRAM: 2 GiB Relocation Offset is: 76f3f000 ------------------------------------------------- * Welcome to Hardkernel's ODROID-C2 ------------------------------------------------- CPU : AMLogic S905 S/N : HKC21323344B2C13 MAC : 00:1e:06:33:01:d3 BID : HKC2211512 ------------------------------------------------- register usb cfg[1][0] = 0000000077f97338 register usb cfg[0][1] = 0000000077f97360 vpu detect type: 5 vpu clk_level = 7 set vpu clk: 666667000Hz, readback: 666660000Hz(0x300) MMC: aml_priv->desc_buf = 0x0000000073f37d30 aml_priv->desc_buf = 0x0000000073f39ec0 SDIO Port C: 0, SDIO Port B: 1 [mmc_init] mmc init success In: serial Out: serial Err: serial ---------------------------------- MMC Size : 8 GB ---------------------------------- reading boot-logo.bmp.gz ** Unable to read file boot-logo.bmp.gz ** reading boot-logo.bmp ** Unable to read file boot-logo.bmp ** movi: the partiton 'logo' is reading... MMC read: dev # 0, block # 58976, count 4096 ... 4096 blocks read: OK hpd_state=1 [CANVAS]addr=0x3f800000 width=3840, height=1440 set hdmitx VIC = 16 hdmitx phy setting done set hdmitx VIC = 16 hdmitx phy setting done Error: Bad gzipped data There is no valid bmp file at the given address Net: Meson_Ethernet Hit [Enter] key twice to stop autoboot: 0 reading boot.ini 4385 bytes read in 3 ms (1.4 MiB/s) cfgload: applying boot.ini... cfgload: setenv m "1080p60hz" # Progressive 60Hz cfgload: cfgload: setenv cec "cecf" cfgload: setenv m_bpp "24" cfgload: setenv mesontimer "0" cfgload: setenv nographics "0" cfgload: setenv maxcpus "4" cfgload: setenv max_freq "1536" # 1.536GHz cfgload: setenv condev "console=ttyS0,115200n8 console=tty0 consoleblank=0" # on both cfgload: setenv verbosity "1" cfgload: setenv bootargs "root=/dev/mmcblk0p2 rootwait rootflags=data=writeback rw ${condev} no_console_suspend hdmimode=${m} m_bpp=${m_bpp} vout=${vout} fsck.repair=yes loglevel=${verbosity} net.ifnames=0" cfgload: setenv loadaddr "0x11000000" cfgload: setenv dtb_loadaddr "0x1000000" cfgload: setenv initrd_loadaddr "0x13000000" cfgload: fatload mmc 0:1 ${initrd_loadaddr} uInitrd reading uInitrd 4877402 bytes read in 117 ms (39.8 MiB/s) cfgload: fatload mmc 0:1 ${loadaddr} zImage reading zImage 12520496 bytes read in 297 ms (40.2 MiB/s) cfgload: fatload mmc 0:1 ${dtb_loadaddr} dtb/meson64_odroidc2.dtb reading dtb/meson64_odroidc2.dtb 29164 bytes read in 5 ms (5.6 MiB/s) cfgload: fdt addr ${dtb_loadaddr} cfgload: if test "${mesontimer}" = "0"; then fdt rm /meson_timer; fdt rm /cpus/cpu@0/timer; fdt rm /cpus/cpu@1/timer; fdt rm /cpus/cpu@2/timer; fdt rm /cpus/cpu@3/timer; fi libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND cfgload: if test "${mesontimer}" = "1"; then fdt rm /timer; fi cfgload: if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi cfgload: booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr} ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4877338 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid reading boot-logo.bmp.gz ** Unable to read file boot-logo.bmp.gz ** reading boot-logo.bmp ** Unable to read file boot-logo.bmp ** movi: the partiton 'logo' is reading... MMC read: dev # 0, block # 58976, count 4096 ... 4096 blocks read: OK hpd_state=1 set hdmitx VIC = 16 hdmitx phy setting done set hdmitx VIC = 16 hdmitx phy setting done Error: Bad gzipped data There is no valid bmp file at the given address movi: the partiton 'dtb' is reading... MMC read: dev # 0, block # 1504, count 128 ... 128 blocks read: OK movi: the partiton 'boot' is reading... MMC read: dev # 0, block # 1632, count 32768 ... 32768 blocks read: OK Bad Linux ARM64 Image magic! odroidc2#reset resetting ... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0; TE: 59422 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 set vcck to 1100 mv set vddee to 1050 mv CPU clk: 1536MHz DDR channel setting: DDR0 Rank0+1 same DDR0: 2048MB(auto) @ 912MHz(2T)-13 DataBus test pass! AddrBus test pass! Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000012e0 Wait bl30...Done Sending bl301.....OK. Run bl301... d bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00011130
MICE Posted October 6, 2016 Author Posted October 6, 2016 On 10/6/2016 at 12:40 PM, Igor said: I repeat the same with clean 5.20 install to eMMC, the exact same way and with the same gears. I only don't have 128Gb eMMC but 8gb which should not play any role. apt-get update apt-get upgrade reboot all fine next no boot ... true. I can take a look later ... This is the uart log: Reveal hidden contents [Reset cause: unknown] [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04] bl30: check_permit, count is 1 bl30: check_permit: ok! chipidLoad bl33 from eMMC, src: 0x00034200, des: 0x01000000, size: 0x00066de0 : ef be ad de d f0 ad ba ef be ad de not ES chip [0.174304 Inits done] secure task start! high task start! low task start! NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x1000000 INFO: BL3-1: Next image spsr = 0x3c9 U-Boot 2015.01 (Sep 15 2016 - 06:15:35) DRAM: 2 GiB Relocation Offset is: 76f3f000 ------------------------------------------------- * Welcome to Hardkernel's ODROID-C2 ------------------------------------------------- CPU : AMLogic S905 S/N : HKC21323344B2C13 MAC : 00:1e:06:33:01:d3 BID : HKC2211512 ------------------------------------------------- register usb cfg[1][0] = 0000000077f97338 register usb cfg[0][1] = 0000000077f97360 vpu detect type: 5 vpu clk_level = 7 set vpu clk: 666667000Hz, readback: 666660000Hz(0x300) MMC: aml_priv->desc_buf = 0x0000000073f37d30 aml_priv->desc_buf = 0x0000000073f39ec0 SDIO Port C: 0, SDIO Port B: 1 [mmc_init] mmc init success In: serial Out: serial Err: serial ---------------------------------- MMC Size : 8 GB ---------------------------------- reading boot-logo.bmp.gz ** Unable to read file boot-logo.bmp.gz ** reading boot-logo.bmp ** Unable to read file boot-logo.bmp ** movi: the partiton 'logo' is reading... MMC read: dev # 0, block # 58976, count 4096 ... 4096 blocks read: OK hpd_state=1 [CANVAS]addr=0x3f800000 width=3840, height=1440 set hdmitx VIC = 16 hdmitx phy setting done set hdmitx VIC = 16 hdmitx phy setting done Error: Bad gzipped data There is no valid bmp file at the given address Net: Meson_Ethernet Hit [Enter] key twice to stop autoboot: 0 reading boot.ini 4385 bytes read in 3 ms (1.4 MiB/s) cfgload: applying boot.ini... cfgload: setenv m "1080p60hz" # Progressive 60Hz cfgload: cfgload: setenv cec "cecf" cfgload: setenv m_bpp "24" cfgload: setenv mesontimer "0" cfgload: setenv nographics "0" cfgload: setenv maxcpus "4" cfgload: setenv max_freq "1536" # 1.536GHz cfgload: setenv condev "console=ttyS0,115200n8 console=tty0 consoleblank=0" # on both cfgload: setenv verbosity "1" cfgload: setenv bootargs "root=/dev/mmcblk0p2 rootwait rootflags=data=writeback rw ${condev} no_console_suspend hdmimode=${m} m_bpp=${m_bpp} vout=${vout} fsck.repair=yes loglevel=${verbosity} net.ifnames=0" cfgload: setenv loadaddr "0x11000000" cfgload: setenv dtb_loadaddr "0x1000000" cfgload: setenv initrd_loadaddr "0x13000000" cfgload: fatload mmc 0:1 ${initrd_loadaddr} uInitrd reading uInitrd 4877402 bytes read in 117 ms (39.8 MiB/s) cfgload: fatload mmc 0:1 ${loadaddr} zImage reading zImage 12520496 bytes read in 297 ms (40.2 MiB/s) cfgload: fatload mmc 0:1 ${dtb_loadaddr} dtb/meson64_odroidc2.dtb reading dtb/meson64_odroidc2.dtb 29164 bytes read in 5 ms (5.6 MiB/s) cfgload: fdt addr ${dtb_loadaddr} cfgload: if test "${mesontimer}" = "0"; then fdt rm /meson_timer; fdt rm /cpus/cpu@0/timer; fdt rm /cpus/cpu@1/timer; fdt rm /cpus/cpu@2/timer; fdt rm /cpus/cpu@3/timer; fi libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND cfgload: if test "${mesontimer}" = "1"; then fdt rm /timer; fi cfgload: if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi cfgload: booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr} ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4877338 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid reading boot-logo.bmp.gz ** Unable to read file boot-logo.bmp.gz ** reading boot-logo.bmp ** Unable to read file boot-logo.bmp ** movi: the partiton 'logo' is reading... MMC read: dev # 0, block # 58976, count 4096 ... 4096 blocks read: OK hpd_state=1 set hdmitx VIC = 16 hdmitx phy setting done set hdmitx VIC = 16 hdmitx phy setting done Error: Bad gzipped data There is no valid bmp file at the given address movi: the partiton 'dtb' is reading... MMC read: dev # 0, block # 1504, count 128 ... 128 blocks read: OK movi: the partiton 'boot' is reading... MMC read: dev # 0, block # 1632, count 32768 ... 32768 blocks read: OK Bad Linux ARM64 Image magic! odroidc2#reset resetting ... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0; TE: 59422 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 set vcck to 1100 mv set vddee to 1050 mv CPU clk: 1536MHz DDR channel setting: DDR0 Rank0+1 same DDR0: 2048MB(auto) @ 912MHz(2T)-13 DataBus test pass! AddrBus test pass! Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from eMMC, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from eMMC, src: 0x0001c200, des: 0x01000000, size: 0x000012e0 Wait bl30...Done Sending bl301.....OK. Run bl301... d bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00011130 Thanks you so far. Your efforts are much appreciated! Keep up the good work.
Igor Posted October 6, 2016 Posted October 6, 2016 https://github.com/igorpecovnik/lib/commit/3332e4bb38d89e96b77201bbde60e1da08c15ca1 It's fixed in build script but images need to be updated. Possible workaround: reboot a board at first login and it might be o.k. (untested) 1
MICE Posted October 7, 2016 Author Posted October 7, 2016 I tested the workaround with clean 5.20 install to eMMC: rebooted after login than did the apt-get update && apt-get upgrade rebooted 2 times but same issue and tested reboot before login same issue after update && upgrade
MICE Posted October 7, 2016 Author Posted October 7, 2016 Thanks for the 5.21 update it works!! Keep up the good work!!!
Igor Posted October 7, 2016 Posted October 7, 2016 Check image.armbian.com for updated 5.21 images. Both are tested and working O.K. Noticed before my notice
Recommended Posts