TCB13

  • Posts

    56
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Portugal

Recent Profile Visitors

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

TCB13's Achievements

  1. Never late to the party! Thank you for your tips. Btw, for future reference fro anyone going about the same path, page 11 of the NanoPi M4v2 schematic contains a definition of the SPI1 that can be easily between the overlay and physical pins. Schematic: http://wiki.friendlyarm.com/wiki/images/c/cc/NanoPi-M4V2_1908_Schematic.pdf Physical pin assignment: https://wiki.friendlyarm.com/wiki/index.php/NanoPi_M4V2#Diagram.2C_Layout_and_Dimension
  2. I think there is a misunderstanding here, I never requested support in "record time" and I certainly didn't said that it needs to happen fast. I just said I would upload my log file as soon as I can. I'm happy with the "few minutes" whenever you guys have some spare time!
  3. I'll wait patiently for some news. It's not a life or death situation
  4. Okay, you win I'll provide the file ASAP.
  5. I'm sorry but... it is for an unsupported board or image (CSC/EOS/WIP/edge) > It's a supported board it is for software that is not supported (such as userspace modules installed on top of the core operating system) > NO it has been logged in the wrong forum (for example requests for help that are not actual bug reports) > NO, its a bug. it lacks requested data (armbianmonitor output) > Not relevant in this case. it could have been easily solved by a quick search and/or reading documentation > ??
  6. Hello, I'm trying to use the NanoPi M4v2 SPI however it doesn't seem to work. I used armbian-config to enable the gpio overlay: [ ] dwc3-0-host [ ] i2c7 [ ] i2c8 [*] pcie-gen2 [ ] rk3328-opp-1.4ghz [ ] rk3328-opp-1.5ghz [ ] rk3399-opp-2ghz [ ] spi-jedec-nor [*] spi-spidev [ ] uart4 [ ] w1-gpio And the SPI isn't showing up on /dev: ls /dev/spi* ls: cannot access '/dev/spi*': No such file or directory Wasn't this enough to be able to use the SPI1 on this board? SBC: NanoPi M4V2 System: 5.10.35-rockchip64 #21.05.1 SMP PREEMPT Fri May 7 13:53:11 UTC 2021 aarch64 GNU/Linux Thank you.
  7. Hello, I'm trying to find out how to use a 1.5 Inch RGB OLED Display that uses the SSD1351 IC on a NanoPi M4 however I don't seem to be able to turn on the SPI. I used armbian-config to enable the gpio overlay: [ ] dwc3-0-host [ ] i2c7 [ ] i2c8 [*] pcie-gen2 [ ] rk3328-opp-1.4ghz [ ] rk3328-opp-1.5ghz [ ] rk3399-opp-2ghz [ ] spi-jedec-nor [*] spi-spidev [ ] uart4 [ ] w1-gpio And the SPI isn't showing up on /dev: ls /dev/spi* ls: cannot access '/dev/spi*': No such file or directory Wasn't this enough to be able to use the SPI1 on this board? Also if anyone has connected this display to the M4 I'm not sure if my pin mapping is correct: Display ---> NanoPi M4 1 VCC --> 17 VCC3V3_SYS 2 GND --> 20 GND 3 DIN --> (identified as MOSI on an RPi) 19 SPI1_TXD/UART4_TX(3V) 4 CLK --> 23 SPI1_CLK(3V) 5 CS --> 24 SPI1_CSn0(3V) 6 DC --> (rpi GPIO) 16 GPIO1_C6(3V) 7 RST --> (rpi GPIO) 18 GPIO1_C7(3V) SBC: NanoPi M4V2 System: 5.10.35-rockchip64 #21.05.1 SMP PREEMPT Fri May 7 13:53:11 UTC 2021 aarch64 GNU/Linux Display: https://www.ebay.com/itm/203101646517 Datasheet: https://www.waveshare.com/w/upload/5/5b/1.5inch_RGB_OLED_Module_User_Manual_EN.pdf Thank you.
  8. Yes I did, however the limitation on the number of bays x price didn't make me very happy. My current setup with more SATA expansion boards can go up to 20 bays without cascading and 75 with cascading. And.. I already had a M4v2 with a the NVMe adapter so... No more costs there.
  9. Here, my testing setup with both boards. Everything powered up by a standard ATX power supply. Now I did run some benchmarks on the disks. System/Kernel: Armbian 21.05.1 Buster with Linux 5.10.35-rockchip64 Hard Drives: Seagate Barracuda 7200rpm 1TB. ST31000524AS (hard drives from 06/2012) https://www.seagate.com/docs/pdf/en-GB/datasheet/disc/barracuda-7200-12-ds1668-6-1101gb.pdf Scenario: Amrbian installed to the SATA hard drive using the armbian-config helper tool. BTRFS filesystem used. Benchmark Command: dd if=/dev/zero of=test bs=100MB count=100 conv=fdatasync Notes: I enabled the PCIe x2 overlay. - HDD Attached to the SATA to M2 Board (HDD > SATA to M2 > NanoPI M4v2) 10000000000 bytes (10 GB, 9.3 GiB) copied, 27.248 s, 367 MB/s 10000000000 bytes (10 GB, 9.3 GiB) copied, 24.6339 s, 406 MB/s - HDD Attached to the SATA Expansion Board (HDD > SATA Expansion Board > SATA to M2 > NanoPI M4v2) 10000000000 bytes (10 GB, 9.3 GiB) copied, 25.1813 s, 397 MB/s Conclusion: I run the test multiple times I was getting around 350-400MB/s regardless of having the disk connected to the SATA Expansion board or to the SATA to M2 board directly. I run the same test by while booting from an eMMC card. The performance is the same if the the disks are mounted with: mount -t btrfs -o defaults,noatime,commit=600,compress=lzo,x-gvfs-hide /dev/sda1 /mnt/HDD Interestingly the performance of ext4 was very bad (tested both as boot device and simple mount): So it seems I'm able to build a low power and high capacity NAS with this setup. Please note that I'm not after the best performance and parallel wiring to disks. I also seem to be able to write simultaneously to two disks without a performance drop and that's enough for my use case. Does anyone has a similar setup?
  10. So, after some research I decided to tune down a bit my project. I decided to ditch the NVMe as boot device because I believe a regular SATA SSD will be enough for my use case. My goal was: Boot from a SATA SSD; Have around 10 SATA ports for 3.5" hard drives. I ended up buying the following: I chose this PCIe to SATA because I already had the NVMe adapter for my M4v2 and it uses the JMB585 chip is used by other SBC manufacturers in hats thus compatible with Armbian. This chip also features "Cascaded mode: support up to x75 SATA devices with JMB575" that allows me to pair it with the other board (based on JMB575) to have more SATA ports.
  11. Hello, I've been using a M4V2 since its release mostly as a NAS (disks over UBS 3.0). I also have it booting from a Samsung NVMe with the official NVMe hat. My setup works flawlessly however I was thinking about ways to add more storage with reasonable performance/price so I thought, what if I managed to add a standard PCIe x1 port from the pins on the board and use standard hardware with it. The idea was to add a cheap PCI switch + NVMe adapter (to boot from) and a PCI to SATA controller such as the following: 1) PCI Switch: https://www.ebay.com/itm/PCI-Express-1X-to-4X-PCI-E-4-Ports-Switch-Multiplier-Expansion-Riser-Card-New/293564888755 2) PCI > NVMe Adapter: https://www.ebay.com/itm/NVMe-PCIe-x4-x2-M-2-NGFF-SSD-to-PCIe-x1-converter-card-adapter-PCIe-x1-to-M-00e/143915406968 3) PCI > Sata: https://www.ebay.com/itm/PCI-Express-1x-To-4-Port-Sata-3-0-6G-Expansion-Controller-Card-Marvell-88SE9215/233219670613 Did anyone had success with a setup like this? It looks like there isn't any adapter for the board to add a standard PCI interface, however I could probably solder something. Software wise would it work? I believe the Marvell 88SE9215 is supported by Armbian from what I read on espressobin threads. Any tips? Thank you!
  12. You always need and SD card / eMMC to start the boot, then it switches to the system on the NVMe disk. Here the general steps on how to set it up: parted -l parted /dev/nvme0n1 mklabel msdos parted -a opt /dev/nvme0n1 mkpart primary ext4 0% 100% armbian-config # -> system -> install -> boot from (eMMC/SD) run from NVMe. reboot cd /media/mmcboot rm -rf bin etc home lib media mnt opt proc root run sbin selinux srv sys usr var dev tmp Enjoy.