y52

  • Content Count

    159
  • Joined

  • Last visited

About y52

  • Rank
    Elite member

Recent Profile Visitors

1489 profile views
  1. My UART cable hasn't arrived yet, it should has been lost on its way to complete the setback with the W2 itself. Meanwhile I have decided sending the BPI-W2 back to the supplier, as no achievement has been made with the broken ethernet and it looks, that nobody interested from the Sinovoip side. Thus I shall not be able dumping mtd. The hardware components are good for different applications, but the absence of drivers and kernel support makes it a handicap.
  2. Out of curiosity I cloned the Andreas Färber's repo branch rtd1295-next and looked into the kernel configs. There isn't a lot about the rtd1296 inside. What I found : | | [*] Realtek Platforms | | <*> Realtek chip info (NEW) | | | | [*] Realtek SB2 (NEW) | | | | [*] Realtek SCPU Wrapper (NEW)
  3. I can not but agree. I've tried several kernel branches for now: mainline, next, legacy BPI-SINOVOIP. In the absence of Realtek's support, accessibility to the board features is very poor. Even basic ethernet NIC's are not operational, even with the legacy BPI-SINOVOIP, which is supposed meeting this basic task. I do not even mention the video Mali T820 support, which is probably far from being thought of.
  4. Does somebody know how to implement the following solution ? https://lkml.org/lkml/2019/7/7/39
  5. I believe, this method will require an access through a serial console. I am waiting for the UART cable to get delivered. I shall try making more series of tests.
  6. It was quite an upset discovering, that the 2nd ethernet port is left unsupported and disabled. The ethX signaling LEDs do no work either. Will the issue with proper ethX support be resolved to make the board functional? https://github.com/BPI-SINOVOIP/BPI-W2-bsp/issues/5 It has been constantly reported to BPi through different posts, but it seems, that no action is taken so far.
  7. I am currently booting from SD card.
  8. root@bpi-iot-ros-ai:~# ls -al /dev/mtd0 crw------- 1 root root 90, 0 Dec 21 21:09 /dev/mtd0 root@bpi-iot-ros-ai:~# dd if=/dev/mtd0 of=dump.dd doesn't complete. root@bpi-iot-ros-ai:~# journalctl -f shows a lot of Dec 21 21:42:49 bpi-iot-ros-ai systemd-journald[1956]: Missed 17 kernel messages Dec 21 21:42:49 bpi-iot-ros-ai kernel: [RTK_SB2_DBG] sb2 get int 0x00000002 from SB2_INV_INTSTAT Dec 21 21:42:49 bpi-iot-ros-ai systemd-journald[1956]: Missed 8 kernel messages Dec 21 21:42:49 bpi-iot-ros-ai kernel: [RTK_SB2_DBG] Invalid access issued by SCPU Dec 21
  9. It's quite a long list : root@bpi-iot-ros-ai:~# ls -al /dev |less total 4 drwxr-xr-x 15 root root 14560 Dec 21 12:39 . drwxr-xr-x 23 root root 4096 Dec 21 13:52 .. crw------- 1 root root 10, 55 Dec 21 12:39 ashmem crw------- 1 root root 10, 235 Dec 21 12:39 autofs crw------- 1 root root 10, 54 Dec 21 12:39 binder drwxr-xr-x 2 root root 700 Dec 21 12:38 block crw-rw---- 1 root disk 10, 234 Dec 21 12:39 btrfs-control drwxr-xr-x 3 root root 60 Jan 1 1970 bus crw------- 1 root root 246, 0 Dec 21 12:39 cec-0 dr
  10. Having received the board, I've tried the available image from the BPi downloads. Interestingly enough, that the image 2019-08-02-debian-10-buster-lite-preview-aarch64-bpi-w2-m4-sd-emmc.img provides an Armbian distro, although built by somebody else : root@bpi-iot-ros-ai:~# dmesg |less [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.119-BPI-W2-Kernel (root@bpi-iot-ros-ai) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #4 SMP PREEMPT Mon Apr 29 15:13:32 CST
  11. I've just get W2 delivered. How could the SPI dump be made? Being a couple of years Armbian's follower, I share the interest implementing the mainstream kernel build for W2 and ultimately put an Armbian on it.
  12. Hello, I've managed building uboot and kernel from the sources, which gives me : root@06e63d8891fd:/Source/BPI-W2-bsp/SD/bpi-w2# ls -alh total 109M drwxr-xr-x 5 root root 4.0K Nov 24 22:08 . drwxr-xr-x 3 root root 4.0K Nov 24 22:07 .. drwxr-xr-x 2 root root 4.0K Nov 24 22:07 100MB -rw-r--r-- 1 root root 76M Nov 24 22:08 4.9.119-BPI-W2-Kernel.tgz -rw-r--r-- 1 root root 266 Nov 24 22:08 BOOTLOADER-bpi-w2.tgz drwxr-xr-x 3 root root 4.0K Nov 24 22:07 BPI-BOOT -rw-r--r-- 1 root root 18M Nov 24 22:07 BPI-BOOT-bpi-w2.tgz drwxr-xr-x 4 root root 4.0K Nov 24 22:07 BPI-ROOT -r
  13. I am upgrading the OrangePI plus bought in 2016 to Buster and moved the system to eMMC with "armbian-config". / _ \| _ \(_) _ | | | | |_) | |_| |_ | |_| | __/| |_ _| \___/|_| |_| |_| Welcome to Debian Buster with Armbian Linux 4.19.57-sunxi Does armbian-config update the u-boot firmware? Or should I run it manually as described? $ sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 How could the current firmware version be checked and backed up before updating it ? Where is an appropriate latest firmware file? I
  14. I can't mount the eMMC : root@orangepiplus:~# lsblk -o model,name,type,fstype,size,label MODEL NAME TYPE FSTYPE SIZE LABEL mmcblk1boot0 disk 4M mmcblk1boot1 disk 4M mmcblk0 disk 60G └─mmcblk0p1 part ext4 60G <- @ SDCard mmcblk1 disk 7.3G └─mmcblk1p1 part ext4 7.2G <- eMM #mount /dev/mmcblk1p1 /mnt/mountpoint [34182.366277] EXT4-fs (mmcblk1p1): couldn't mount RDWR because of unsupported optional features (400) Is there a reason for that?
  15. I followed the Rasbian Jessy to Stretch migration link (above). It doesn't allow for the kernel upgrade. The migration ends up with the root@orangepiplus:/# uname -a Linux orangepiplus 3.4.113-sun8i #8 SMP PREEMPT Sat Feb 9 20:17:57 CET 2019 armv7l GNU/Linux The fresh installation from scratch allows for the Linux 4.19.20. Thus at least the kernel upgrade procedure needs to be thought of. The other question for Orange PI : how could different boot device be chosen? How could I choose booting from Nand or SD Card of USB?