Energokom

Therefore, if you do not need GPIOs, it is better to buy a mini PC than an SBC. People buy TV boxes for Linux precisely because of the cheapness. Few people need SBCs. Most people need a small device in a box for a minimal price. Why buy a banana pi M5 pro for $ 195, which will stop support in a few years, when you can buy x86 mini PC with this money and not know the problems with support? Can you name the reasons why it is worth buying an SBC instead of a mini PC?

You can upload your dts or img?

If you don't need GPIOs and you're not a developer: don't buy SBCs as long as their prices are higher than the TV box. For the same price, you can buy a mini PC and it will be better than SBC. I advise you to buy a TV box on SOC s905x3. 1) You will be able to install Linux for your purposes. 2) As well as being able to use an android set-top box, amlogic is better in this regard. P.S. I believe that 90% of users do not need SBC, since they do not use GPIO, camera, ports for connecting the screen and the like. Many users need a cheap headless server. There are high-quality and inexpensive TV boxes for these purposes. In addition, for the price of banana pi m5, you can buy a mini PC that will work faster. SBC is a device for developers. For those who then make TV boxes and tablets. For ordinary users, SBC is unnecessary. The SBC manufacturer needs to pay attention to the user's need, which is: 1. SD card, emmc or M2. 2.LAN 1000/100 3. Wi-fi/BT 4. USB 3.0 5. 2/4/8 GB RAM The rest 90% of users do not need and therefore they will buy either a TV box or a mini PC as it is more profitable for the price

Unfortunately, it didn't work. I want to build u-boot 2024 (since the old u-boot 2019 is being used now). But it doesn't work out for me. I can't change defconf, since ./compile.sh CREATE_PATCHES="yes", doesn't work now. I try CREATE_PATCHES (uboot-patch) but I don't get a pause to make changes. I used to use CREATE_PATCHES=yes and everything worked, now I can't build u-boot with my settings. You need more detailed instructions in the description of build options

Hi. Can you buid a loader c with rk3566_ddr_1056MHz_v1.21.bin https://github.com/rockchip-linux/rkbin/blob/master/bin/rk35/rk3566_ddr_1056MHz_v1.21.bin or tell me how to do it. Thanks!

I can take it from android. But I asked how to build it myself

How to build a miniloader.bin with rk3566_ddr_1056MHz_v1.21.bin ?

When using X11VNC in SBC without a connected display, everything works well on some assemblies and the screen resolution is 1024 x 768. But I could change that in xorg.conf. But now, either in kernel 6.x.x, or in bookworm, I have a 720x576 composite video output resolution, since HDMI is not connected. And there is no way I can change the resolution and make sure that the composite video output is not used. HELP me

This will be a better solution than using, a microphone on an SBC board (for example, orange pi). The sound quality of the USB microphone is incomparably better The USB microphone is cheap. You save time and effort than looking for where to solder the microphone terminals and the decoupling on the TV box

It is better to use a USB microphone

I have sp6330 On github, you said: devmfc 5 days ago I would expect the sp6330 to work... You could try to install the full firmware package via apt-get install firmware-linux. If that doesn't work you could try to see if dmesg complains about something... I looked, there is no mention of wi-fi in dmesg. In the last message, I sent the original dts from android, can you take a look at it? Android DTS aml_wifi { compatible = "amlogic, aml-wifi"; status = "okay"; irq_trigger_type = "GPIO_IRQ_LOW"; pwm_config = <0x50>; interrupt-gpios = <0x1b 0x37 0x0>; power_on-gpios = <0x1b 0x36 0x0>; }; wifi_pwm_conf { phandle = <0x50>; pwm_channel1_conf { pwms = <0x51 0x0 0x774d 0x0>; duty-cycle = <0x3ba6>; times = <0x7>; }; pwm_channel2_conf { pwms = <0x51 0x2 0x7724 0x0>; duty-cycle = <0x3b92>; times = <0xa>; }; }; Linux DTS sdio-pwrseq { compatible = "mmc-pwrseq-simple"; reset-gpios = <0x11 0x36 0x01>; clocks = <0x19>; clock-names = "ext_clock"; phandle = <0x0b>; }; wifi32k { compatible = "pwm-clock"; #clock-cells = <0x00>; clock-frequency = <0x8000>; pwms = <0x1a 0x00 0x7736 0x00>; phandle = <0x19>; }; wifi SDIO ID: 0x02d0:0x4330 dmesg systemd[1]: Failed to start systemd-binfmt.service - Set Up Additional Binary Formats.

@Devmfc I'm using your image for S905w2, on the T95W2 TV box, help me start Wi-FI. I have dts from the android firmware of my T95w2 TV box. There is also a dts from linux (meson-s4) on which I have a TV box running, but no Wi-FI Can you tell me how to make changes to dts correctly in order to register the necessary SDIO bus? I will install the SP6330 drivers myself android-T95w2-2g.dts.7z meson-s4-s905w2-ap201.dts.7z P.S. Thank you for your work

How to find out which SDIO bus wi-fi is connected to (HK6334Q)?

First of all: there is practically no support for TV box as it is. Basically, users themselves share their best practices. Secondly, as I said, SBC manufacturers need to adapt to the needs of users and make cheap SBC (example raspberry). And then they will buy SBC instead of TV box

My friend had an SBC orange pi 3, on which the emmc failed after 2.5 years. I have a s905w TV box (the first one I bought instead of SBC), it has been working for a year with armbian on emmc. (This is me to the reliability of emmc on SBC). In any case, having a stencil and a soldering station, you can always solder the emmc All my other TV boxes are still working on the SD card.I want to install two more on emmc - that's just setting up a weekly backup of the system on Google disk.