Jump to content

N4IRS

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by N4IRS

  1. N4IRS

    Odroid M1

    I have my M1 sitting here waiting for some Armbian action!
  2. I know this is a old thread, take a look at this https://www.instructables.com/Get-HDMI-Output-From-Your-Rock64-Using-Armbian/ Look at notes starting with step 6.
  3. Thank you projetoarduino. Your sun8i-h3-nanopi-neo.dtb worked for me. I downloaded the Stretch nightly for the NEO at https://dl.armbian.com/nanopineo/nightly/Armbian_5.44.180510_Nanopineo_Debian_stretch_next_4.14.40.7z I booted, logged in and did the usual apt-get update, apt-get upgrade. At this point, I have wired ethernet but no eMMC. I replaced the existing dtb with yours from https://github.com/projetoarduino/armbian-nanopi-core. Once I rebooted I had wired ethernet AND eMMC. I copied the OS to the eMMC and I can boot from the eMMC! Once again, Armbian comes through! Steve
  4. Well that was fast. I retried the build and saw a change had been committed to the repository. It's building now. Thanks SO much! Steve
  5. I am attempting to build the following: Full OS image for flashing Do not change the kernel configuration nanopineo2 next or dev kernel same error stretch or xenial same error [ o.k. ] Downloading sources [ o.k. ] Checking git sources [ u-boot v2017.11 ] [ .... ] Up to date [ o.k. ] Checking git sources [ linux-mainline linux-4.14.y ] [ .... ] Up to date [ o.k. ] Checking git sources [ arm-trusted-firmware-sunxi-mainline allwinner-stable ] [ .... ] Fetching updates fatal: Couldn't find remote ref allwinner-stable [ .... ] Checking out error: pathspec 'FETCH_HEAD' did not match any file(s) known to git. [ o.k. ] Checking git sources [ sunxi-tools master ] [ .... ] Up to date [ o.k. ] Checking git sources [ rkbin-tools master ] [ .... ] Up to date [ o.k. ] Checking git sources [ marvell-tools A3700_utils-armada-17.10 ] [ .... ] Up to date [ o.k. ] Checking git sources [ odroidc2-blobs master ] [ .... ] Up to date [ o.k. ] Cleaning output/debs for [ nanopineo2 next ] [ o.k. ] Cleaning [ arm-trusted-firmware-sunxi-mainline/allwinner-stable ] [ o.k. ] Compiling ATF [ o.k. ] Compiler version [ aarch64-linux-gnu-gcc 6.4.1 ] [ o.k. ] Started patching process for [ atf sunxi64-nanopineo2-next ] [ o.k. ] Looking for user patches in [ userpatches/atf/atf-sunxi64 ] [ warn ] * [l][c] add-SRAM-mapping-for-SCPI.patch [ failed ] [ warn ] * [l][c] enable-a53-errata-workaround.patch [ failed ] [ warn ] * [l][c] enable-additional-regulators.patch [ failed ] [ warn ] * [l][c] set-rsb-to-nonsec.patch [ failed ] make: *** No rule to make target 'bl31'. Stop. [ error ] ERROR in function compile_atf [ compilation.sh:59 ] [ error ] ATF compilation failed [ o.k. ] Process terminated root@ImageBuilder:/srv/build# Can someone point me in the proper direction? I have been using the builder for custom images for other boards without error. I will also say, I love this tool. Makes it very easy for me to build customized Armbian images with my applications pre-installed. Thanks, Steve
  6. Just to be clear, I'm just getting used to the environment I'm not trying to put anything into production. If I break it, I get to keep both pieces. I am a BIG fan of Armbian and I hope I can at least feedback information. Thanks, Steve
  7. Processing file /srv/build/patch/u-boot/u-boot-sunxi/fix-spi-spl-fit-support.patch patch unexpectedly ends in middle of line Processing file /srv/build/patch/u-boot/u-boot-sunxi/fix-sunxi-gpio-driver.patch patch unexpectedly ends in middle of line In patching.log
  8. I'm still building, I am seeing this in the console: Setting up python3 (3.5.3-1) ... qemu: Unsupported syscall: 384 qemu: Unsupported syscall: 384 qemu: Unsupported syscall: 384 qemu: Unsupported syscall: 384 qemu: Unsupported syscall: 384 Setting up python3-gi (3.22.0-2) ... Just a example I think ever qemu error is 384.
  9. Nice! Building now. I am just testing for now so I will be aware of the thermal issue with the kernel. Can the EXPERT switch be added to the config-default.conf?
  10. I would be happy to build Stretch. I did not see the option. Please point me to the info.
  11. I should have added that I did make the change in the resulting image. Thanks, for the info. Steve
  12. I am building a full image for the OPiPC. For the most part everything works. I do get one error while running compile.sh The error I see during build is: "W: Failed to fetch http://apt.armbian.com/dists/jessie/InRelease Unable to find expected entry 'jessie-utils/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used instead. I am building on a VMware vm running Linux armbian 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I did the clone from the git repository and ran compile.sh as root. I selected: Full OS image for flashing Do not change the kernel configuration orangepipc next Mainline (@kernel.org) (4.x) jessie Debian 8 Jessie Image with console interface (server) The image does create and boot when burned to a SD I get deb http://apt.armbian.com jessie main jessie-utils jessie-desktop in /etc/apt/sources.list.d/armbian.list which generates a error on apt-get update. Did I miss something during the build? Are there any logs I need to post. Thanks, Steve
  13. I know this is a old topic, but in case someone else is searching. I used nand-sata-install to copy the OS from a SD card to the eMMC. Worked fine the first time. No problems. root@odroidxu4:/etc# cat armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=odroidxu4 BOARD_NAME="Odroid XU4" VERSION=5.33.171003 LINUXFAMILY=odroidxu4 BRANCH=next ARCH=arm IMAGE_TYPE=nightly BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage Steve
  14. Tony, Thanks for the comments. I was looking at the Odroid UX4. You confirmed it. I'm going to skip the directly attached RAID and use Network Attached Storage. Thanks again, Steve
  15. OK, Forget the building images. I am interested in building a ARM based development machine for compiling and testing programs for the ARM processor. I do not want to cross compile. I do not plan to run the machine headless. I will not be connecting a keyboard mouse or screen. For storage, I would like to use RAID 1 (mirror) I would like a fast SATA interface that can support at least 2 SATA fast SSD. I would like it to run Armbian Any suggestions? Thanks, Steve
  16. Sorry if I was unclear. X64 I have no problem. I want a ARM based machine. I am looking for a recommendation for a ARM based board to use for development.
  17. I am considering building a development machine for building images, and Debian packages (deb). I do not plan a GUI on it. I plan to ssh in. I would like to be able to mirror a couple of SATA drives for safety. Speed and connectivity are important. Can anyone make a suggestion on what board. Must run Armbian of course. Thanks, Steve
  18. I just want to post a thank you to the developers and contributors who have built one NICE distribution. Over a year ago I bought a few OPi PC as a possible replacement for Raspberry Pi based HAM radio projects I support. To say I was disappointed in the distribution from the manufacturer is a understatement. Without Loboris stepping up and getting something usable I would have tossed them in the trash and moved on. Last night I downloaded and installed Jessie server from Armbian. What a pleasure. Small, clean and a giant plus for me, HEADERS!!!!. I am so tired of having to build the headers for a kernel so I can compile the out of tree modules I need. I just ordered a few NanoPi NEO and I look forward to being able to run Armbian. Thank you VERY much! My next stop is the donate button. Steve
  19. I'm new to the Allwinner family of processors but not to building kernels etc. I need to build a custom kernel for the OrangePi PC. I've worked with Loboris image builder but I have not had much luck with the kernel builder. Has there been any movement to add the H3 to supported processors for Armbian? Thanks, Steve
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines