Rolf Bakker

Members
  • Content Count

    11
  • Joined

  • Last visited

About Rolf Bakker

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Rolf Bakker

    Network problem on stress test

    Hi Rami, I've got several NanoPi Neo2 boards and their network connection runs very stable in my experience. Actually, I'm quite happy with these little boards. I've got mine fitted with the standard heatsink from FriendlyElec. Regards, Rolf
  2. Thank you for the swift reply! I will try this.
  3. I've got a working Vagrant Armbian Build environment. Now I want to add the following to the sun50i-h5-nanopi-neo2.dts (provides network support in U-boot) and compile a new image. &emac { pinctrl-names = "default"; pinctrl-0 = <&emac_rgmii_pins>; status = "okay"; phy = <&phy1>; phy-mode = "rgmii"; phy1: ethernet-phy@1 { reg = <0>; }; }; Despite reading the docs, I still can't figure out how it's done. Maybe someone can point me in the right direction?
  4. ok, I tested from a different machine and it appears that the DHCP server shouldn't provide the fullpath of the filename, but just the path within the tftp folder. After I changed the setting in my DHCP server the file could be loaded. U-Boot 2018.09-rc3-00026-g4cdeda511f-dirty (Sep 10 2018 - 16:37:11 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => setenv serverip 192.168.188.1 => dhcp BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.188.50 (1003 ms) Using ethernet@1c30000 device TFTP from server 192.168.188.1; our IP address is 192.168.188.50 Filename '/boot/boot.scr'. Load address: 0x42000000 Loading: # 1.5 MiB/s done Bytes transferred = 3090 (c12 hex) => One step closer to booting the NanoPi Neo 2 from the network. I think my brain got a bit numb yesterday, by the end of the day Does any one have a u-boot script in combination with Armbian to make this work with NFS?
  5. I'm trying to boot my Nano Pi Neo 2 from the network but I am a bit stuck. I have found out how to add network support to u-boot for the Nano Pi Neo 2, I can set the serverip and perform the dchp command, the Nanopi neo get's an IP address from the DHCP server but then booting halts with the message that it can't find the file. I'm pretty sure the location & access rights are valid. (Is there an easy way to check?) U-Boot 2018.09-rc3-00026-g4cdeda511f-dirty (Sep 10 2018 - 16:37:11 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => setenv serverip 192.168.188.1 => dhcp BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.188.50 (1003 ms) Using ethernet@1c30000 device TFTP from server 192.168.188.1; our IP address is 192.168.188.50 Filename '/nfsshares/tftp/npi/boot/boot.scr'. Load address: 0x42000000 Loading: T TFTP error: 'File not found' (1) Not retrying... => Is there anyone who has experience booting Armbian from the network that can point me in the right direction / perhaps share a working solution?
  6. Rolf Bakker

    OrangePi Zero Plus: ethernet in u-boot

    @Hackbeere How to enable network support in u-boot for the Nano Pi Neo 2. The instructions above use the FriendlyArm repo, the same can be achieved with mainline using a more recent version of u-boot, the procedure is slightly different and described below: In order to enable the network interface for the Nanopi Neo 2 in U-boot you have to take the following steps (works with Ubuntu 18.04): 1) Install the toolchain on a Host PC (Ubuntu) 2) Install some additional software 3) Compile arm-trusted-firmware 3) Install u-boot 4) Make changes to the nanopi neo2 dts file in order to add network capability in U-boot 5) Compile u-boot with the changes 6) Update U-boot on the SD card for the Nanopi Neo 2 Here are some detailed working instructions: Install toolchain on Host PC (Ubuntu) sudo su mkdir -p /opt/FriendlyARM/toolchain/ cd /root wget https://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz tar -xf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz -C /opt/FriendlyARM/toolchain/ export PATH=/opt/FriendlyARM/toolchain/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin:$PATH export GCC_COLORS=auto . ~/.bashrc Install additional software on Host PC (Ubuntu) apt install gcc-aarch64-linux-gnu -y apt install git make gcc bison flex -y apt install swig python-dev python3-dev -y apt install device-tree-compiler -y apt install gcc-arm-linux-gnueabihf -y Compile arm-trusted-firmware on Host PC cd /root git clone https://github.com/apritzel/arm-trusted-firmware.git cd arm-trusted-firmware/ git checkout allwinner export CROSS_COMPILE=aarch64-linux-gnu- make PLAT=sun50iw1p1 DEBUG=1 bl31 export BL31=/root/arm-trusted-firmware/build/sun50iw1p1/debug/bl31.bin Compile U-Boot with network support on Host PC cd /root git clone git://git.denx.de/u-boot.git u-boot/ cd u-boot nano arch/arm/dts/sun50i-h5-nanopi-neo2.dts Add to the end &emac { pinctrl-names = "default"; pinctrl-0 = <&emac_rgmii_pins>; status = "okay"; phy = <&phy1>; phy-mode = "rgmii"; phy1: ethernet-phy@1 { reg = <0>; }; }; Compile u-boot make nanopi_neo2_defconfig CROSS_COMPILE=aarch64-linux-gnu- make CROSS_COMPILE=aarch64-linux-gnu- Update U-Boot on SD Card Insert the SD card with the Nanopi Neo 2 official ROM / OS in the cardreader of the host-pc. Check with lsblk where the SD card is with for the Nanopi Neo 2 is located (e.g. sdb) Replace sdX in the following commands with the actual location of the Nanopi Neo 2 SD card. dd if=spl/sunxi-spl.bin of=/dev/sdX bs=1024 seek=8 dd if=u-boot.itb of=/dev/sdX bs=1024 seek=40 sync I hope this helps.
  7. Rolf Bakker

    OrangePi Zero Plus: ethernet in u-boot

    @Hackbeere In order to enable the network interface for the Nanopi Neo 2 in U-boot you have to take the following steps (works with Ubuntu): 1) Install the toolchain on a Host PC (Ubuntu) 2) Install some additional software 3) Install u-boot 4) Make changes to the nanopi neo2 dts file in order to add network capability in U-boot 5) Compile the changes 6) Update U-boot on the SD card for the Nanopi Neo 2 Here are some detailed working instructions: Install toolchain on Host PC (Ubuntu) sudo su mkdir -p /opt/FriendlyARM/toolchain/ cd /root Download gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu.tar.xz from friendlyarm to the current (/root) folder tar -xf gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu.tar.xz -C /opt/FriendlyARM/toolchain/ export PATH=/opt/FriendlyARM/toolchain/gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu/bin:$PATH export GCC_COLORS=auto . ~/.bashrc Install some additional software on Host PC (Ubuntu) (as root) apt-get install swig python-dev python3-dev -y apt-get install device-tree-compiler -y apt-get install gcc-arm-linux-gnueabihf -y Download and Compile U-Boot with network support on Host PC (as root) cd /root git clone https://github.com/friendlyarm/u-boot.git cd u-boot git checkout sunxi-v2017.x nano arch/arm/dts/sun50i-h5-nanopi-neo2.dts Add to the end &emac { pinctrl-names = "default"; pinctrl-0 = <&emac_rgmii_pins>; status = "okay"; phy = <&phy1>; phy-mode = "rgmii"; phy1: ethernet-phy@1 { reg = <0>; }; }; Compile make nanopi_h5_defconfig CROSS_COMPILE=aarch64-linux-gnu- make CROSS_COMPILE=aarch64-linux-gnu- Update U-Boot on SD Card Insert the SD card with the Nanopi Neo 2 official ROM / OS in the cardreader of the host-pc. Check with lsblk where the SD card is with for the Nanopi Neo 2 is located (e.g. sdb) Replace sdX in the following commands with the actual location of the Nanopi Neo 2SD card. dd if=spl/sunxi-spl.bin of=/dev/sdX bs=1024 seek=8 dd if=u-boot.itb of=/dev/sdX bs=1024 seek=40 After that you can put the SD card in the Nanopi Neo 2 and the ethernet interface will show up in U-boot.
  8. For a new project with multiple socs, I want to use the NanoPi Neo 2 with the Allwinner H5 soc and boot from DHCP / NFS. I've done the same in the past for a setup with Raspberry Pi's, but the Allwinner socs require a different approach. What would be the best way to achive this? - FEL? - SD or USB with U-Boot? - any other suggestions?
  9. I've got a Cubieboard2 with a serial interface hardwired to PI10 and PI11 (uart5). The default Cubieboard2 DT overlay connects uart5 to PH6 and PH7, so I made a new dts, called "sun7i-a20-uart5b" with the pins like I need them: /dts-v1/; /plugin/; / { compatible = "allwinner,sun7i-a20"; fragment@0 { target-path = "/aliases"; __overlay__ { serial5 = "/soc@01c00000/serial@01c29400"; }; }; fragment@1 { target = <&pio>; __overlay__ { uart5_pins_a_2: uart5@1 { pins = "PI10", "PI11"; function = "uart5"; }; }; }; fragment@2 { target = <&uart5>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <&uart5_pins_a_2>; status = "okay"; }; }; }; According to the instructions I need to excute: armbian-add-overlay sun7i-a20-uart5b But this results in an error: Kernel headers are not installed properly. Please install the kernel headers package root@cubieboard2:/boot/dtb# armbian-add-overlay sun7i-a20-uart5b.dts Kernel headers are not installed properly. Please install the kernel headers package if I execute as root the following: apt-get install linux-headers-$(uname -r) I get the following errors: root@cubieboard2:/boot/dtb# sudo apt-get install linux-headers-$(uname -r) Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-headers-4.13.16-sunxi E: Couldn't find any package by glob 'linux-headers-4.13.16-sunxi' E: Couldn't find any package by regex 'linux-headers-4.13.16-sunxi' I'm stuck now: My basic question is: how do I enable uart5 on PI10,PI11 ? If I've proceeded in the correct way, how do I install the kernel header package?