Jump to content

flyoffthehandle

Members
  • Posts

    2
  • Joined

  • Last visited

  1. Just to make sure I went back and used a 14.04 server image. The script ran smoothly and created a 16.04 image that I flashed to eMMC and was able to boot. The only problems I see is the boot partition being ~30MB instead of 128MB. So it looks like the boot partition is just large enough to fit the initial contents. If anything tries to reconfigure anything inside that partition it exits with error not enough disk space. Is this something I could have (or should have) changed before I ran the compile.sh? I think I saw something about HDMI and odroid c2 in the forums earlier but just in case, the other problem (maybe or maybe not) is the HDMI output flashes on and off, not quickly but will be on for ~5 seconds and then off for 15-20 seconds and then repeat. I've been able to restart and have this not happen after bootup of the board is complete. I'm going to go back and check if maybe it has something to do with what is connected via USB as I had an external hard drive connected via SATA to USB3 adapter that does not have it's own power supply. edit: Plugging in the external drive after boot seems to fix the HDMI flashing. I'm trying the nand-sata script provided to see if I can go about getting the boot partition resized. I saw another thread describing a method of flashing via rsync so I'm assuming the boot partition size is not a bug at all. Great tool by the way. Thanks for making it available.
  2. I have been trying to build a C2 image with xenial and without including a desktop using the armbian build script. I have tried putting the toolchain in /opt/toolchains (like odroid's wiki states) and also in the build script's directory under toolchains. I've placed the proper export lines to each path in .profile & .bashrc but no matter how i go about this I always have the compile.sh script error out after "Cleaning [ linux-odroidc2/odroidc2-3.14.y ] I am using a VM that has gcc/g++ 4.9 installed and is running ubuntu xenial (would not using 14.04 have something to do with this?). /home/kyle/build/lib/common.sh: line 230: /home/kyle/build/toolchains/gcc-linaro-aarch64-linux-gnu-4.9-2014.09_linux/bin/aarch64-linux-gnu-gcc: No such file or directory awk: cmd. line:1: BEGIN{exit ! ( < 5.0)} awk: cmd. line:1: ^ syntax error awk: cmd. line:1: BEGIN{exit ! ( < 5.0)} awk: cmd. line:1: ^ syntax error [ error ] ERROR in function find_toolchain [ common.sh:240 ] [ error ] Could not find required toolchain [ aarch64-linux-gnu-gcc < 5.0 ] [ o.k. ] Process terminated Any help would be appreciated. I need 16.04 for the c2 that hasn't had any of the window manager packages added to it for a project and this is my first go at building a kernel or full image so this is my first time setting up a cross compile. I also tried using this script on a c2 running the stock hardkernel xenial image but the script quit with the error that it is unable to run on the board itself.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines