g40

  • Content Count

    66
  • Joined

  • Last visited

About g40

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Hi Martin I've been playing with the 2018.11 release of U-Boot. The problem with not finding USB devices on busses > 0 seems to have been fixed. Annoyingly the device tree has been completely revised so there is a deal of patching to be done. I also got u-boot network support enabled in 2018.05 with some device tree changes. I'll try and get patches out in due course. LMK if you'd like the changes. Thanks for all the help.
  2. You need to enable both the Sunxi CSI and the OV5647 drivers in the kernel configuration. Make them loadable modules ('M') in the kernel configuration..
  3. I'm trying to get TFTP support into U-Boot but it insists that 'no ethernet found'. I've added a couple of nodes to the device tree such that it has 'status = "okay" and mac-address = [00 00 00 00 00 00]; I've also added a top level alias in sun50i-h5-nanopi-k1-plus.dts (as added by @martinayotte following this thread) as below. Not sure if the U-Boot config needs changing in any way but the network components are certainly being built. Any thoughts most welcome. AATIA. aliases { serial0 = &uart0; ethernet0 = &emac; }; U-Boot dum
  4. Hi Zador, Thanks. Have you had any 64bit boards working with NFS?
  5. So this is failing for some odd reason. Armbian command line configuration is: /compile.sh BOARD=nanopik1plus BRANCH=next KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=jessie BUILD_DESKTOP=no ROOTFS_TYPE=fel FEL device mode is activated: @ubuntu-1804:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 005: ID 1f3a:efe8 Onda (unverified) V972 tablet in flashing mode Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Armbian interaction is then ... [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] Starti
  6. Working from the documentation here: https://docs.armbian.com/Developer-Guide_FEL-boot/#what-is-felnfs-boot. Not much luck so far with an FA NanoPi K1 Plus. Please see below for details. TIA.
  7. Yes, is it ever I am going to try and repeat this exercise for the K1+ so it can boot out of SPI flash using TFTP. Are any of the other Allwinner based boards configured to do this? Thanks again for your help here.
  8. Hello Martin u-boot is detecting the OHCI/EHCI controllers. But it is only finding storage attached to USB0. In this case a USB=>SD card adapter. If I swap the thumb drive into USB0 and and SD adapter into USB2 or 4, it gets correctly identified. It's slightly annoying but definitely not a show-stopper. => usb reset resetting USB... EHCI failed to shut down host controller. EHCI failed to shut down host controller. USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for dev
  9. Hello, What is the correct way to set armbianEnv.txt values when the distro is being built? Specifically I'd like to set kernel verbosity to a non-zero value? There does not seem to be a skeleton file so is all content generated dynamically? TIA
  10. Hi Martin. So, this is really good. I can now get the board to boot from the USB 1 connector on the K1 board (this is the single socket on the board pictured below). The actual USB device is in fact a USB=>SD card adapter, which is rather useful for comparison. One more question if I may. Does the DT control which USB interface is used? Repeating the exercise above with a card plugged into USB 2 or 3 does not work. `usb storage` does not detect any devices. *Many* thanks for your help here. FA NanoPi K1
  11. Hello Martin, Many thanks. Having tried both an update and a clean armbian build I get the same build failure. There is indeed no config in `build/cache/sources/u-boot/v2018.05/configs` Please let me know if you'd like to see any logs etc. Built build/sun50i_a64/debug/bl31.bin successfully [ o.k. ] Cleaning [ u-boot/v2018.05 ] [ o.k. ] Compiling u-boot [ 2018.05 ] [ o.k. ] Compiler version [ aarch64-linux-gnu-gcc 7.2.1 ] [ .... ] Checking out sources [ o.k. ] Cleaning [ u-boot/v2018.05 ] [ o.k. ] Started patching process for [ u-boot sunxi64-na
  12. Hello Martin Let me paste better info then. Using master from armbian/build, UART spew below. How come no network or USB controllers? What else do I need to enable in the u-boot .config? Or is this because something is disabled in the DTB? TIA. U-Boot SPL 2018.05-armbian (Dec 29 2018 - 13:49:33 +0000) DRAM: 2048 MiB Trying to boot from sunxi SPI NOTICE: BL31: v2.0(debug):c876582 NOTICE: BL31: Built : 13:49:30, Dec 29 2018 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x407ecc8, model: FriendlyARM NanoPi K1 plus INFO:
  13. Thank you Martin, I have u-boot getting to the media detection stage[1]. This is a FriendlyArm K1 (H5) with some externally attached SPI flash which is all working nicely. My problem seems to be getting USB support enabled in u-boot. Whatever .config options I have tried so far fail with section overflows and/or unresolved externals. [1] Trying to boot from sunxi SPI NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):0fc0ec6 NOTICE: BL3-1: Built : 14:33:21, Dec 8 2017 INFO: BL