guidol Posted May 16, 2018 Posted May 16, 2018 I installed ARMBIAN 5.44 testing Ubuntu 18.04 LTS 4.14.40-odroidc2 on my C2 and it is working fine at this time, but it hangs with the command "shutdown -r now" - I have to power off/on. Now I did get the advice to update to U-Boot V2018.03 On my C2 dpkg does show me as actual installed: linux-u-boot-odroidc2-next 5.44 arm64 Uboot loader 2017.11 Via "apt-cache search" or at http://apt.armbian.com/pool/main/l/linux-u-boot-odroidc2-next/ I couldnt find nothing newer than the installed version or linux-u-boot-next-odroidc2_5.38_arm64.deb 25-Jan-2018 07:48 206K In /etc/apt/sources.list.d/armbian.list I got as the only armbian-source: deb http://apt.armbian.com bionic main bionic-utils bionic-desktop So could please point me anyone the the v2018.03 U-boot as .deb or how could I compile it for myself? As Info I only did find that: https://github.com/armbian/build/pull/913 Thanks in advance
Igor Posted May 16, 2018 Posted May 16, 2018 "committed 8 hours ago" https://github.com/armbian/build/commit/0e7681ee250a2beab744b854062ee558e4bf1e39 Updated package will be at next nightly rebuilt but since I just tear down build server it might take more than 24h before things are back in action. 1
guidol Posted May 16, 2018 Author Posted May 16, 2018 22 minutes ago, Igor said: "committed 8 hours ago" Alright! so I will wait some time for the next up & reboot. Many thanks @Igor
Igor Posted May 18, 2018 Posted May 18, 2018 On 5/16/2018 at 7:05 PM, guidol said: some time for the next up & reboot https://github.com/armbian/upload/commit/761f38516873149506f886eec78abcf65653ffc6 apt update & upgrade on the stable branch. Nightly building still offline.
guidol Posted May 19, 2018 Author Posted May 19, 2018 22 hours ago, Igor said: https://github.com/armbian/upload/commit/761f38516873149506f886eec78abcf65653ffc6 apt update & upgrade on the stable branch. Nightly building still offline. Hmm @Igor thats seems to be the moment when a Odroid C2 doesnt use eMMC (mmcblk0) as boot-device, but a uSD-Card (mmcblk1). Entpacken von linux-u-boot-odroidc2-next (5.45) über (5.44) ... linux-u-boot-odroidc2-next (5.45) wird eingerichtet ... Device /dev/mmcblk0 does not exist, skipping root@odroid-c2:~# ls /dev/mmc* /dev/mmcblk1 /dev/mmcblk1p1 Is there any way/command to configure this u-boot for a uSD-Card? wget http://apt.armbian.com/pool/main/l/linux-u-boot-odroidc2-next/linux-u-boot-next-odroidc2_5.45_arm64.deb and dpkg -i ./linux-u-boot-next-odroidc2_5.45_arm64.deb doenst did the "trick" dpkg does show it as installed. but I dont think it was successful: root@odroid-c2:~# dpkg -l|grep boot linux-u-boot-odroidc2-next 5.45 arm64 Uboot loader 2018.03 inside the .deb/tar I did found the platform_install.sh: DIR=/usr/lib/linux-u-boot-next-odroidc2_5.45_arm64 write_uboot_platform () { dd if=$1/bl1.bin.hardkernel of=$2 bs=1 count=442 conv=fsync > /dev/null 2>&1; dd if=$1/bl1.bin.hardkernel of=$2 bs=512 skip=1 seek=1 conv=fsync > /dev/null 2>&1; dd if=$1/u-boot.bin of=$2 bs=512 seek=97 conv=fsync > /dev/null 2>&1 } $1 will be the DIR /usr/lib/linux-u-boot-next-odroidc2_5.45_arm64 but what will be $2 (for of=) ? Maybe /dev/mmcblk1 ?
Igor Posted May 19, 2018 Posted May 19, 2018 DEVICE=/dev/mmcblk1 dpkg -i linux-u-boot-next-odroidc2_5.45_arm64.deb
guidol Posted May 19, 2018 Author Posted May 19, 2018 7 minutes ago, Igor said: DEVICE=/dev/mmcblk1 dpkg -i linux-u-boot-next-odroidc2_5.45_arm64.deb Installation seem to went fine: root@odroid-c2:/home/guido# DEVICE=/dev/mmcblk1 dpkg -i ./linux-u-boot-next-odroidc2_5.45_arm64.deb (Lese Datenbank ... 72496 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../linux-u-boot-next-odroidc2_5.45_arm64.deb ... Entpacken von linux-u-boot-odroidc2-next (5.45) über (5.45) ... linux-u-boot-odroidc2-next (5.45) wird eingerichtet ... Updating u-boot on /dev/mmcblk1 but after a power off/on reboot for activating the new u-boot the C2 doenst reboot complete neither after a "reboot" nor a "shutdown -r now" Is there any way to check the successfull installation or is there any chance that the reboot also wont work after the new u-boot 2018.3?
Igor Posted May 19, 2018 Posted May 19, 2018 1 minute ago, guidol said: Is there any way to check the successfull installation With serial console to see if thingie was booted with a new u-boot. I assume you don't have one?
guidol Posted May 19, 2018 Author Posted May 19, 2018 18 minutes ago, Igor said: With serial console to see if thingie was booted with a new u-boot. I assume you don't have one? OK, when there is no other way I will install a TTL-serial-USB-Dongle on the C2 and check if the new u-boot is used....have to check where is the TTL-Prt on the C2
Igor Posted May 19, 2018 Posted May 19, 2018 12 minutes ago, guidol said: .have to check where is the TTL-Prt on the C2 I think all Odroid's have 1.8V TTL logic https://forum.odroid.com/viewtopic.php?f=53&t=4758
zador.blood.stained Posted May 19, 2018 Posted May 19, 2018 18 minutes ago, Igor said: I think all Odroid's have 1.8V TTL logic https://forum.odroid.com/viewtopic.php?f=53&t=4758 According to this C2 has 3.3V logic, it's the XU4 family that has 1.8V logic. Edit: also this: https://wiki.odroid.com/accessory/development/usb_uart_kit#port_description_of_uart_connector
guidol Posted May 19, 2018 Author Posted May 19, 2018 7 minutes ago, Igor said: I think all Odroid's have 1.8V TTL logic https://forum.odroid.com/viewtopic.php?f=53&t=4758 too bad all my Dongles have 3.3/5V (CP2102 and CH340G). The serial Dongle from FriendlyARM has the same connector but not only a other pinout but also only 3.3V and 5V. Maybe I burned now my serial Port with 3.3V? I dont know, but the C2 only makes trouble to me.... First he allways he want to boot eMMC as first (switch only at later models) so I cant reformat my messed-up emmc with a sdcard-boot and now the serial-TTL isnt a 3.3V/5V standard
guidol Posted May 20, 2018 Author Posted May 20, 2018 I couldnt get any data out of the serial port I used some Jumper-Wire - also did try to switch rx/tx but no data from the port. I used 3 several TTL-Dongles - maybe my serial debug port is defective?
guidol Posted May 21, 2018 Author Posted May 21, 2018 On 5/19/2018 at 7:40 PM, Igor said: DEVICE=/dev/mmcblk1 dpkg -i linux-u-boot-next-odroidc2_5.45_arm64.deb "same" problem - but with the NanoPi Core2 (using the image for the NanoPi Neo Plus2) - via "apt upgrade" : Setting up linux-u-boot-nanopineoplus2-next (5.45.180521) ...Device /dev/mmcblk0 does not exist, skipping root@nanopi-core2:~# ls /dev/mmc*/dev/mmcblk2 /dev/mmcblk2boot0 /dev/mmcblk2boot1 /dev/mmcblk2p1 /dev/mmcblk2 is the internal emmc of the NanoPi Core2 (there is no sd-card inserted - armbian was installed via armbian-config from sd-card to emmc) As Information: System diagnosis information will now be uploaded to http://ix.io/1aZk But at http://apt.armbian.com/pool/main/l/linux-u-boot-nanopineoplus2-next/ there isnt a 5.45.180521 u-boot .deb [EDIT] OK I did found it wget http://beta.armbian.com/pool/main/l/linux-u-boot-nanopineoplus2-next/linux-u-boot-next-nanopineoplus2_5.45.180521_arm64.deb DEVICE=/dev/mmcblk2 dpkg -i ./linux-u-boot-next-nanopineoplus2_5.45.180521_arm64.deb Setting up linux-u-boot-nanopineoplus2-next (5.45.180521) ...Updating u-boot on /dev/mmcblk2
mattaw Posted May 26, 2018 Posted May 26, 2018 Unfortunately with a clean install of Armbian Odroid c2 on an SD-CARD and linux-u-boot-odroidc2-next 5.45 (u-boot 2018.03) my C2 still hangs on "shutdown -r now" with updated u-boot. Thoughts on things to poke to find the source of the problem? Matthew
TonyMac32 Posted May 26, 2018 Posted May 26, 2018 I'm away from my computer, are we using the BayLibre patchset on C2? If not the u-boot might not function properly, I remember Neil saying we needed those patches for Le Potato to use mainline u-boot.
Recommended Posts