• Content count

  • Joined

  • Last visited

About umiddelb

  • Rank
    Advanced Member

Recent Profile Visitors

460 profile views
  1. Why shouldn't I buy ROCK64?

    I cannot confirm this behaviour. My Rock64 board does not need that manual interaction in order to boot.
  2. You should be able to read and modify the stored custom u-boot environment since the -next kernel has built-in support for the M25P80 chip. To gain access, you need to pass some partitioning information to the kernel command line. You may check if the device files /dev/mtd[012] exists. Otherwise you need to add the following parameter to the command line: mtdparts=spi0.0:1536k(uboot),64k(uboot-environment),-(reserved) Then, after having rebooted, you need to install the `u-boot-tools´ package and modify `/etc/fw_env.config´ like this # device name device offset env. size flash sector size number of sectors /dev/mtd1 0x0 0x00010000 0x1000 0x10 Now you can make use of `fw_printenv´ and `fw_setenv´ to get userland access the u-boot environment.
  3. The device node for the SD card has changed from mmcblk0 to mmcblk1. You need to edit the file `/boot/armbianEnv.txt`. Either you change mmcblk0 to mmcblk1 there as well or you modify the `rootdev` variable to something like: rootdev=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx where xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx has to be replaced by the UUID of /dev/mmcblk1p1. sudo blkid will tell you the right UUID.
  4. OK, thanks. I can live perfectly with the 5.24 u-boot release (U-Boot 2017.01-g0675f99 (Jan 20 2017 - 23:04:59 +0100)). Does this issue affect other boards using mainline u-boot as well? - The 5.35 u-boot release (U-Boot 2017.09-armbian (Nov 22 2017 - 17:09:56 +0100)) works as well.
  5. Just for curiosity, I've updated my Armbian on my Pine64 to the latest release. The latest u-boot for Pine64 (U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:32:21) seems to have an issue with the persistent u-boot environment. Once I've written a custom environment back to MMC using `saveenv´ the board hangs during boot. Environment size: 10335/131068 bytes => saveenv Saving Environment to MMC... Writing to MMC(0)... done => reset resetting ... INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF INFO: AffInst: Level 0, MPID 0x3, State OFF U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:32:21) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 08:32:15, Jan 25 2018 NOTICE: Configuring AXP PMIC NOTICE: PMIC: Output power control 2 is an unexpected 0xd9 ERROR: PMIC: setup failed: -3 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 This might be an edge case for most of the Armbian users, since Armbian doesn't rely on a custom u-boot environment in oder to boot. I prefer to use my own u-boot framework instead, but it needs the capability to store a permanent custom u-boot environment. So if there is a chance to fix this issue I'd really appreciate it.
  6. Can't Install MongoDB on Cubietruck 3

    I'm running the unifi controller software on a 2.6.10 mongodb server (using the xenial distro package). You may give it a try.
  7. I'm using a different defconfig to build my kernel. It's derived from one of the first Marvell 4.4 kernel sources with arm64 platform defaults and Docker requirements added. I know that Armbian uses a different one. I started to merge both configs but that kernel didn't boot up. I've started some bisects but didn't find the time to identify all problematic kernel parameters.
  8. Hm, 4.14. comes with SD card support for the espressobin (no additional patch needed).
  9. Actually yes. I've removed the partitioning information from the dts and pass it as a kernel parameter.
  10. You might want to add some spi magic to your device tree ... (tidy up afterwards)
  11. You need to initialise the u-boot environment. IHMO Armbian for the espressobin comes with a text file containing a suitable environment, see here for more details.
  12. Due to a stuck board during kernel compilation I've switched back to the 1000_800 firmware (from September, 30th). I can see both u_boot environments (each of 64k size): - 1200_750 (and stock firmware) environment starts at offset 0x000000180000 (which I use as the beginning of /dev/mtd1) - 1000_800 environment starts at offset 0x0000003F0000 (last 64 k block of spi32766.0)
  13. I've tried both the 1000_800 and the 1200_750 firmware for the 2GB board today. The 1000_800 variant seems to use a different partitioning layout and didn't find the u-boot environment created by the stock firmware. The 1200_750 firmware instead uses the same offsets and booted without any hassle.
  14. RK3399 Orange Pi

    You can get an 8 GB, 8 Cores ARMv8 server for 12 EUR/month (and many other configurations) at Scaleway as well.
  15. You may try the network configuration, I'm using for the espressobin (individual ports, no bridging): auto eth0 iface eth0 inet manual hwaddress ether f0:ad:4e:03:6a:9f auto lan0 iface lan0 inet dhcp pre-up /sbin/ifup eth0 hwaddress ether f0:ad:4e:03:6a:a1 Btw. has anyone succeeded to do the networking setup with pure nmcli ? Cheers Uli