-
Posts
2023 -
Joined
-
Last visited
Other groups
Contributor/Maintainer
Recent Profile Visitors
16922 profile views
-
@Christopher Ruehl congratulations, great finding! That could explain some of the compatibility issues people is still having. I have a couple of questions: 1) what is the purpose of enabling the internal gpio pull-up when there already is the external pull-up? 2) do you have any suggestions to apply to existing device tree to enhance compatibility for other users? Exchanging SMD components on the board is out of the league for most people Thanks!
-
@A t sorry but I have no idea, no logs, no board info and photos couldn't help understand what the problem may be
-
Find a possible IP address for the box and try to access via SSH, or use the UART serial to debug the issue
-
There is a driver for ssv6051p in the armbian images, but if the kernel does not see the chip it is probably turned off. You need to set the right led-conf using rk322x-config script that enables the GPIO to turn on the wifi chip. MX10 is the tv box commercial name, but it tells nothing about the board which is inside: you have to look for the signatures on the board itself and see if you have a match with the led-conf proposed by rk322x-config
-
Yes, the same. Technically the SoC enters in maskrom mode when all the boot devices fails. Gating the eMMC will make the SoC boot from sdcard, if there's no sdcard, the SoC will attempt other boot options programmed in its ROM. Finally, if nothing is available, will sit and wait in maskrom mode.
-
exactly; shorting the clock pin will make the eMMC disappear from the system, hence the SoC will boot from sdcard
-
As said, you can either remove the eMMC or short the clock pin to ground. Otherwise learn how the rockchip vendor boot happens and use the multitool binaries to hack the armbian boot
-
@ToShuk it depends upon a tree of factors. mmc is totally invisible to the SoC The the SoC will automatically look for the sdcard - just plug armbian in the sdcard and it will work the above won't work if the sdcard slot is attached to the sdmmc_ext controller of the SoC; this depends on how the manufactured designed the board and, if this is your case, your only solution is to replace the onboard eMMC mmc is stuck in read-only mode the SoC will indeed execute the bootloader, if any was present in the eMMC when it went read-only If the existing bootloader is the stock one, then you're stuck with the possibilities of the stock bootloader (eg: see the rockchip boot process wiki page): multitool will boot, but not plain armbian images; tinkering with armbian images bootloader will let them boot though. You can either short permanently the eMMC clock pin to ground, so the eMMC is clock gated and actually excluded from the system, or phisically remove the eMMC chip, so you can reconduct to the "totally invisible" case above if the existing bootloader is the one provided with armbian, the you're lucky and it should be possibile to boot from sdcard and USB
-
@Francisco Hasuky it is a known problem: some boards are sent to "suspension" after one minute by the proprietary Trust OS; you need to build u-boot with an opensource Trust to overcome the problem. At the moment I'm unable to build an image or provide the binary, but will do in the forthcoming hours/days @Jota Ce if you got ssv6051p chip, then you should be ok using any recent armbian image with kernel 6.12 (you could upgrade to edge kernel via armbian-config, or use the beta.armbian.com APT repository). Also kernel 6.6 should work with ssv6051p because the (horrible) driver has been ported from 4.4 kernel.
-
-
@Fcn3 this what you can expect from such hardware. There is a chromium fork around with patches to allow v4l2request accelerated video decoding, but has never been tested on rk3318 and probably you have to built it yourself.
-
Hello @Francisco Hasuky, does the HDMI turns off but the board is still responsive or the board just drops dead?
-
Hello, exactly the same instruction, yes