justsomeguy1983

Members
  • Posts

    6
  • Joined

  • Last visited

justsomeguy1983's Achievements

  1. Ahhh so i just fixed it.... change the boot.ini from GNU nano 2.5.3 File: /boot/boot.ini ODROIDXU-UBOOT-CONFIG setenv rootdev "/dev/mmcblk0p1" # U-Boot Parameters setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" # Mac address configuration setenv macaddr "00:1e:06:61:7a:55 #------------------------------------------------------------------------------------------------------ # Basic Ubuntu Setup. Don't touch unless you know what you are doing. # -------------------------------- setenv bootrootfs "console=tty1 loglevel=1 root=${rootdev} rootwait ro fsck.repair=yes" # boot parameter for serial console console=ttySAC2,115200n8 to this GNU nano 2.5.3 File: /boot/boot.ini ODROIDXU-UBOOT-CONFIG setenv rootdev "/dev/mmcblk0p1" # U-Boot Parameters setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" # Mac address configuration setenv macaddr "00:1e:06:61:7a:55 #------------------------------------------------------------------------------------------------------ # Basic Ubuntu Setup. Don't touch unless you know what you are doing. # -------------------------------- setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 loglevel=1 root=${rootdev} rootwait ro fsck.repair=yes" # boot parameter for serial console console=ttySAC2,115200n8 All is well! Thanks. Caleb
  2. Yes, I can log in with a display or by ssh. Here is dmesg: Caleb
  3. I'm trying to get a full serial console on my XU4. I currently only get the U-boot output. The last message says "Loading Kernel". I never get any kernel related messages. I understand I will need to start up a getty to actually log in via this console port, but I haven't even gotten that far. In my (unchanged) boot.ini I have console=ttySAC2, 115200n8. And when the system boots up, I cannot manually write anything to that port (as i believe the kernel has it opened) Any Ideas? Thanks! Caleb
  4. Read my post #33. It will show you how to make the EMMC module boot by copying the armbian uboot to your emmc module. (you will need a serial console adapter to do it though...)
  5. Ok, So I'm pretty sure I've gotten the problem solved with my EMMC module on my XU4. You will need 3 things to make this a success. 1. UART Module available from hardkernel or ameridroid (USA), or you can just buy an ftdi usb to uart cable but make sure you buy the 1.8V version so you don't over-voltage the console port 2. MicroSD card flashed with the latest version of Armbian I used 5.25 3. EMMC module for the XU4 ALSO flashed with the lastest Armbian version. A. Install BOTH the microsd and the emmc module into the XU4 B. Hook up the uart module to another computer and open up putty or hyperterminal or whatever you prefer, so when you power up your XU4 you can see the boot process (baud rate is 115200) C. Switch the Boot selector switch to microSD card. D. Apply power to XU4 E. After you see text scrolling hit enter twice to stop UBOOT F. If done correctly you should be greeted with a 'Exynos5422 #' prompt G. Run this command "run copy_uboot_sd2emmc" H. Below is a printout of a successful copy of armbians uboot to the special-hidden uboot partition on the EMMC module Exynos5422 # run copy_uboot_sd2emmc reading FWBL1 ..device 0 Start 1, Count 30 MMC read: dev # 0, block # 1, count 30 ... 30 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing FWBL1 ..device 1 Start 0, Count 30 MMC write: dev # 1, block # 0, count 30 ... 30 blocks write: OK completed eMMC CLOSE Success.!! reading BL2 ..device 0 Start 31, Count 32 MMC read: dev # 0, block # 31, count 32 ... 32 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing BL2 ..device 1 Start 30, Count 32 MMC write: dev # 1, block # 30, count 32 ... 32 blocks write: OK completed eMMC CLOSE Success.!! reading bootloader..device 0 Start 63, Count 656 MMC read: dev # 0, block # 63, count 656 ... 656 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing bootloader..device 1 Start 62, Count 656 MMC write: dev # 1, block # 62, count 656 ... 656 blocks write: OK completed eMMC CLOSE Success.!! reading 0 TrustZone S/W.. Start 719, Count 512 MMC read: dev # 0, block # 719, count 512 ... 512 blocks read: OK completed eMMC OPEN Success.!! !!!Notice!!! !You must close eMMC boot Partition after all image writing! !eMMC boot partition has continuity at image writing time.! !So, Do not close boot partition, Before, all images is written.! writing 1 TrustZone S/W.. Start 718, Count 512 MMC write: dev # 1, block # 718, count 512 ... 512 blocks write: OK completed eMMC CLOSE Success.!! if you receive a eMMC OPEN Failed.!! message you didn't select the microSD as the boot Final step is to remove power, remove the microSD card and move the boot selector switch to the EMMC module. Enjoy your blazing fast EMMC Caleb
  6. Here is the Uboot printout information off off my XU4 Using the "Armbian_5.24_Odroidxu4_Ubuntu_xenial_default_3.10.104_desktop" image. This image works great on the SD card but will not boot when using the EMMC Module (which I'd much rather use) U-Boot 2012.07-00035-g0209be0 (Oct 06 2015 - 18:21:02) for Exynos5422 CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7] APLL = 800MHz, KPLL = 800MHz MPLL = 532MHz, BPLL = 825MHz Board: HardKernel ODROID 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: 29.1 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 quickly 'Enter' twice to stop autoboot: 0 ** Unable to use mmc 0:1 for fatload ** Unknown command 'ext4load' - try 'help' Unknown command 'ext4load' - try 'help' >>> 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 #