sgofferj

If nothing else yet, I at least have a 3D printable case design to show for the CM3588 NAS... https://github.com/sgofferj/CM3588-NAS-case

@going Fantastic! Thank you!

@going I have tried all of FriendlyElec "Official images", most recent the debian. It's 6.1.25. @wasuu I don't think that dts even would even work for the CM3588 NAS. At least when I tried Armbian for the T6 on the CM3588 it booted but didn't run without quirks, e.g. no USB or HDMI out. I'm swamped this week and probably also next. But when I get to it, I'll try to find the dtb files from the "official" image and decompile them...

Thanks! I have heard about device trees and had a look at some DTS for the Banana Pi CM4 but I was lacking reference to understand the bigger picture. Looking at it, I'm probably not the one who is going to make Armbian work on this board but maybe I can do some prep work at least...

Thanks. I was though more looking for hints on how to get hardware working.

Morning all, so I got myself a FriendlyElec CM3588 NAS board for testing and in the end integrating in my homelab. I tried a few Armbian images - FriendlyElec suggests the NanoPi R6S image and I tried the NanoPC T6 image. Both boot but both have some issues, e.g. no USB connectivity and no HDMI out (T6). While not a being developer or SBC specialist, I am a Linux user since 1995 (server)/1996 (desktop) and I am used to some pain, tinkering and problem solving. Is there any kind of "getting started with a new board"- or similar document that I could use as a starting point to tinker with this board? Any hints, advice? Of course I could use the stock Debian/Ubuntu images from FriendlyElec but I grew to like Armbian a little after running it on a bunch of RPis and a Banana Pi... Happy New Year! Stefan

@c0rnelius Apologies, my edit probably overlapped with your reply. It works fine for me with the Waveshare board. I was stupid and missed the boot switch position. Still testing with the MCUZone board, though.

@c0rnelius Thank you! Unfortunately, I can't get it to work on either the Waveshare or the MCUZone board. It doesn't seem to disturb the function on the bananapi base board, though. I copied the dts-file and did a sudo armbian-add-overlay meson-g12b-bananapi-cm4-waveshare-usb.dts. There is a corresponding dtbo now in /boot/overlay-user and a line "user_overlays=meson-g12b-bananapi-cm4-waveshare-usb" in /boot/armbianENV.txt I tried several flash drives and 2 different keyboards. No device shows up in dmesg or lsusb. Please let me know if I have missed anything. I'm an experienced Linux user but fairly new to armbian. EDIT: Never mind, I'm an idiot! I forgot check the boot switch on the Waveshare board. It was set to "on". Set to "off", the Waveshare board works! The MCUZone board doesn't at first glance. The boot jumper doesn't seem to do anything. I'll do some experimenting but that board is also fairly buggy- The USB hub e.g. is very temperature sensitive.

I have a Waveshare board on order and an MCUZone POE board in non-production use at the moment. I can test whatever dtbo you can come up with and give feedback.

The BananaPi CM4 doesn't play well with a number of third party base boards in that often, USB does not work on them. Usually, that is because the third party base board designer connected the USB hub IC to an SOC OTG port without connecting a line to switch the OTG port into host mode. The problem was demonstrated at least with the Waveshare CM4 Base Board B and the MCUZone POE baseboard. In the Banana Pi forums, Sinovoip engineer "August" posted a DTBO for Ubuntu 20.04 which solves the issue by forcing host mode. Below is the DTBO decompiled to DTS. I would like to request that this overlay be updated for the Armbian kernel and included as an optional overlay into the Meson 64 / BananaPi CM4 distribution. dts-v1/; / { fragment@0 { target = <0xffffffff>; __overlay__ { controller-type = <0x01>; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { otg = <0x00>; }; }; __fixups__ { dwc2_a = "/fragment@0:target:0"; usb3_phy_v2 = "/fragment@1:target:0"; }; };

I have run into a similar problem with another board. The problem seems to be that the Waveshare board (as well as the other one) connect their hub IC to the OTG port without connecting a line which puts the OTG port into host mode. In the Banana Pi forums, a tech posted a DTBO for Ubuntu 20.04 which looks like this (decompiled) dts-v1/; / { fragment@0 { target = <0xffffffff>; __overlay__ { controller-type = <0x01>; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { otg = <0x00>; }; }; __fixups__ { dwc2_a = "/fragment@0:target:0"; usb3_phy_v2 = "/fragment@1:target:0"; }; }; I do, however, not have the slightest clue how to translate that to the significantly newer armbian kernel... Maybe @c0rnelius can help with that?