• Content Count

  • Joined

  • Last visited

About umiddelb

  • Rank
    Elite member

Recent Profile Visitors

2344 profile views
  1. root@mgmt:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=cubox-i BOARD_NAME="Cubox i2eX/i4" BOARDFAMILY=cubox BUILD_REPOSITORY_URL= BUILD_REPOSITORY_COMMIT=b9adf0ea-dirty VERSION=5.98 LINUXFAMILY=cubox BRANCH=next ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage root@mgmt:~# uname -a Linux mgmt 5.3.1-cubox #5.98 SMP Fri Sep 27 23:11:49 CEST 2019 armv7l armv7l armv7l GNU/Linux root@mgmt:~# find /sys -name phy_id /sys/devices/soc0/soc/2100000.aips-bus/2188000.ethernet/mdio_bus/2188000.ethernet-1/2188000.ethe
  2. Good idea, you may get in touch with Edward Vielmetti (@vielmettialt).
  3. This board might meet your requirements, except of the price tag ... you may regard it as an upper bound.
  4. The spi flash memory (with the u-boot environment stored inside) is accessible from the command line. Please check if the corresponding driver is loaded via dmesg. It should look like: [ 1.878826] spi-nor spi0.0: w25q32dw (4096 Kbytes) [ 1.878850] 2 cmdlinepart partitions found on MTD device spi0.0 [ 1.878854] Creating 2 MTD partitions on "spi0.0": [ 1.878870] 0x000000000000-0x0000003f0000 : "uboot" [ 1.888884] 0x0000003f0000-0x000000400000 : "uboot-environment" The partitioning information is passed as a command line parameter to the kernel (last parameter in this case):
  5. The problematic reset-gpios instruction is still present in the device tree description. Removing it solves the issue for my board (which is a pre-series test sample). The suggested patch doesn't apply since there are different pins involved (0x24 vs 0x21).
  6. Hi, the lastest kernel update issues the following lines in dmesg output: [ 12.214293] meson8b-dwmac ff3f0000.ethernet: Failed to reset the dma [ 12.215002] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed [ 12.223988] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Hw setup failed Do I need to update the firmware as well? B.t.w. you may mention that armbianmonitor -u needs to be run as root, otherwise the fping check will fail.
  7. The download directory doesn't seem to contain the recent firmware with the correct RAM layout. The last modification date is from 2019 and I run into the some issue when I've 'refurbished' my espressobin today with Ubuntu 20.04.
  8. I don't know if you have already read an article which I've written for ODROID Magazine a couple of years ago ("Das-U-Boot") .
  9. You may test the following approach: - have a look with `fdisk -l /dev/<sd card>` and find out where the first (and only) partition starts - copy with `dd bs=512 if=/dev/<sd card> of=<imagefile> count=<start sector of first partition> - copy the contents of /boot to a different location - look which file system features have been enabled for / (`tune2fs -l /dev/<sd card>`) - write the image file to a different sd card - delete and recreate on the different sd card the first partition according to the space requirements of /boot, ma
  10. Where do you load the kernel image, dtb and initrd from, from sd card or from a network device as well?
  11. With a different (and well known working at 3,3V) adapter, the PBP boots up fine. I can intercept the boot sequence and play around with the u-boot console. Next thing is to fix the serial console speed mismatch.
  12. As the adapter is working when connected to a booted PBP, I suppose that the automatic voltage detection in the TTL adaptor does not work reliably and switches to 5V when connected to a switched off PBP.