• Posts

  • Joined

  • Last visited

Everything posted by jock

  1. @Wester_Minskthanks for the firmware and photos. I had a quick look into the device tree and it looked quite standard to me: no particular hardware like Power Management ICs or other significant differences from regular tv boxes. I will take a deeper look and check other compatibility things soon!
  2. @Wester_Minsk It could be that your board has some peculiarities we did not ever yet encountered. There could literally dozens of reasons you get a kernel crash, but probably CPU or DDR memories got badly configured. Usually this is a matter of the device tree, but can be related to bootloader too. Could you share the backup you did? It is ok also to share the first 100 megabytes if you don't want to upload the whole package and/or maybe you have some personal contents. From there we can extract the dtb and the bootloader. Remember to compress it before uploading Also a couple or more detailed photos of the board and its main chips (front and back) are very useful.
  3. Yes, the partition is enlarged as soon as you put it in the box. Anyway you can paste the compressed armbian image on the sdcard as the instructions never tells you to decompress it.
  4. jock

    Mainline VPU

    Everything well with h264 and h265 on my side, with both hantro and rkvdec drivers on kernel 5.14 on rockchip RK322x chip (roughly same performance as H3) and latest LE patches applied. One thing that always makes me have headaches are the userland kernel headers, which are not the same kernel headers used to compile modules and provided by armbian as a deb package. The userland kernel headers on Armbian comes from the distribution (debian or ubuntu) and match the distribution kernel version, not the really installed kernel version. Mismatch may cause compiling troubles (missing or duplicate structs or costants) or even subtle errors during runtime (unable to initialize things...) To make the userland kernel headers, compile the kernel on the board (with LE patches applied) and then running make headers_install INSTALL_HDR_PATH=/usr will install them in the proper place Just after doing it is possible to go further compiling and installing ffmpeg and then compiling and installing mpv. This is what I use to compile and install ffmpeg: ./configure --arch=armhf --extra-libs='-Lpthread -Lm' --disable-debug --enable-stripping --enable-gpl --enable-nonfree --enable-logging --disable-doc --enable-pic --enable-optimizations --enable-ffmpeg --enable-avdevice --enable-avcodec --enable-avformat --enable-swscale --enable-postproc --enable-avfilter --disable-devices --enable-pthreads --disable-w32threads --enable-network --disable-gnutls --disable-gray --enable-swscale-alpha --disable-small --enable-dct --enable-fft --enable-mdct --enable-rdft --disable-crystalhd --disable-vaapi --disable-vdpau --enable-libdrm --enable-version3 --enable-runtime-cpudetect --enable-hardcoded-tables --enable-encoder=ac3 --enable-encoder=aac --enable-encoder=wmav2 --enable-encoder=mjpeg --enable-encoder=png --enable-hwaccels --enable-muxer=spdif --enable-muxer=adts --enable-muxer=asf --enable-muxer=ipod --enable-muxer=mpegts --enable-demuxers --enable-parsers --enable-bsfs --enable-filters --enable-bzlib --enable-libspeex --enable-libx264 --enable-libx265 --enable-zlib --enable-asm --enable-neon --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-openssl --enable-libv4l2 --enable-v4l2-request --enable-libudev make -j4 sudo make install This is what I use to compile and install mpv: ./waf configure --enable-egl-drm And finally the mpv command line is (run on pure virtual terminal, no X11 at all): mpv -v --vo=gpu --hwdec=drm --gpu-context=drm --gpu-hwdec-interop=drmprime-drm --drm-draw-plane=overlay --drm-drmprime-video-plane=primary bbb_sunflower_1080p_30fps_normal.mp4 the --drm-draw-plane and --drm-drmprime-video-plane arguments are very imporant for my setup, probably because rk322x has no YUV capabilities for overlay plane and MPV refuses to show anything. Also they make the video and draw planes order correct (video below, GUI on top).
  5. Nope, it should be possibile to run directly on eMCP but at the moment, since I never had any chance to test any of them, it is still not officially supported. The latest multitool is capable of guessing the existing configuration and patching the image while installing it on the eMCP so it should run even there. I recently added another menu item that allows to change the DDR Command Rate Timing, which is the problem for the eMCP boards: eMCP DDR part usually wants 2T Command Rate, but existing images are configured for 1T Command Rate. If you install the armbian image with this misconfiguration, the board just bricks and the only chance to bring to board to life is shorting eMCP clock pins to bring the board in maskrom mode. Since eMCP clock pins are difficult to find because the package of the chip is BGA, installing on eMCP at the moment is discouraged. If you feel confident enough and have some electronic skills and you don't fear to lose the board, you may give a chance: First install the armbian image as usual using the multitool Use the "Change DDR Command Rate" menu item to switch to 2T command rate Shutdown the board, unplug the sdcard, reboot and hope! For this I may need the original device tree. Your board seems a newer one which is probably missing the right configuration for wifi
  6. Thanks for reporting, link should be available for anyone now!
  7. I think all people which have AP6330 (aka BCM4330) chip have this issue, including me on another rk3288 box
  8. There is some reference on the internet about this message as being a "harmless error message" due to some missing function in the firmware or whatever. It is "normal": functionality and performance of the wifi does not suffer due to that.
  9. Suspend is totally untested, I don't know if any rk3328/3318 device could suspend and come back without issues, there are plenty of variables to take in account when this happens. I would rather bind the power button to an unused keycode and then, via userspace, catch the keycode and run a script or something similar that does what I want. Don't know how to turn HDMI off although, maybe unbinding the device...
  10. Hello. I have limited experience with windows, there is indeed the AndroidTool, then renamed to RkDevTool, which can be downloaded from rockchip github tools repository. It is not hard to use, but does not come with a real user guide, just a series of buttons that do things and you need some background to understand what they really do. What you want to do (backup eMMC to SD, transfer backup to other similar box) is already covered by multitool, in fact the backup/restore paragraph you cite is for EXPERTS because involves entering maskrom mode, USB male-to-male cable, and some low level linux tools. Multitool is by far easier to use.
  11. Frame this post and pin it in the forum registration page! Moreover, ssv6x5x chips are working just on rockchip platforms, no mainline kernel, definitely if anyone gets an ssv6x5x is not lucky at all. I think the best wifi you can find in common tv boxes is one of the broadcom derivatives (the AmPak AP* series): slim and good opensource driver, good throughput, often working bluetooth, generally available firmwares. I don't have enough experience with realtek chips, but looking at their drivers... well, they are not really well engineered and the latest burst of discovered vulnerabilities is just a confirmation of bad source code. Then there are the mixed bags: esp8089 (very good opensource driver, simple design, only 802.11n and no bt though), allwinner XR series (weak and unstable drivers in the past, don't know now). But, as @hexdump said, it is a lottery: you won't know what you will get. One consideration can be helpful: getting a box with wifi + bt will exclude all the wifi-only chips (ssv6x5x, allwinner XR, esp8089), which increases the chances to get broadcom or realtek chips, which at least work well with mainline kernel.
  12. @Wester_Minskno, you misread the datasheet. Each chip is 2gbit, you have 8, then it's 16gbit / 8 = 2 gbyte, no way out. The specs given by the manufacturer are fake.
  13. Are you sure it is 4gb? If it detects 2Gb probably it is 2gb, and 4gb is a faking spec from the vendor. It's hard to tell how much memory you have, you have look into the datasheet for the memory chip and multiply for the number of chips.
  14. The answer to this question is yes, but it still requires some manual intervention because the bits to get hardware accelerated videos is getting merged into mainline kernel in these months. From the tests I did on rk3288 (not rk3318), it is working pretty well, but requires compiling ffmpeg and mpv by hand, plus ffmpeg source code has to be compiled with some more patches. A note: GPU is not involved in hardware video acceleration, so tinkering with the driver won't provide any dramatic performance improvement.
  15. it could be interesting to know what did you change to make it work
  16. Yes, the rk3318/rk3328 has a spare sdmmc controller, sometime it is left unused, sometime it is used for wifi or sdcard. In your case, it seems that it is used for wifi, and it is strange that if you enable the right device tree overlay it freezes your board.
  17. In the previous pages I posted some instructions on how to let it work. The driver for various led drivers is available on github and needs to be manually compiled. I did not include it yet because it has some limitations I would like to fix before integrating into. Overclock: bad idea on rk3318, but your mileage may vary Why do you want to remove the metal can? It is a very bad idea, it shields the wifi from interferences and if you remove it, probably your wifi/bt will have troubles. There are various instructions over the internet, but what are you expecting from the dts?
  18. Well, installing the wrong firmware on the wrong box is usually the best recipe to brick the box, as you experienced by yourself. Just in case someone else reads and wants to do that, it is something that I absolutely DO NOT recommend to do unless you exactly know what are you doing. It's not your case, I see you're fine because you got the eMMC clk pin to put the board in maskrom mode, but not all rk3318/rk3328 have accessible eMMC clock pin. Anyway thanks for the large list of rk3318 firmwares, it will be interesting to scavenge for firmwares and blobs
  19. From the dts you posted, the wifi chip is attached to the "alternate" sdio bus. From the dts also there is no evidence that your wifi chip is sv6051p, that is anyway not supported in mainline kernel. To understand why your box is hanging on reboot if you select the alternate sdio bus there is the need for a detailed log from the serial. edit: photos of the board and chips are welcome and interesting
  20. @RetroFan90 Thanks for the photos, firmwares and all the details! The HK1 Max (aka YX_RK3328 board) is already very well supported since it is the board I got here and it is the main developing asset I got. The H96 Max looks quite ordinary box, I took a look to the dtb and it seems pretty standard to me, should work fine out of the box. Do you have issues with some peripherals with the H96 Max?
  21. You can try the instructions for another board (xt-q8l-v10) I worked on: If it works for you, probably the basic things should work ok (usb, hdmi, sdcard, emmc, ...) but other peripherals like wifi, bluetooth, etc... may not work out of the box. Maybe it can be a starting point for further studies. AFAIR the rikomagic was somehow famous some years ago, and maybe there is a device tree already available in the linux kernel, but I'm not sure.
  22. I understand. Well, if you don't have any experience with Linux, it will be hard to suggest you to do anything valuable with such box. Surely Armbian, at the current state, is probably not going to be a good experience with netflix, multimedia things are still trying to get sorted out. Maybe you would give a look to LibreELEC, if your purpose is mainly multimedia.
  23. Hello, you didn't say what you want to do with your box. If you want to restore android, this is totally the wrong place. If you want to install/try armbian (and wipe out android), the other thread you already found has clear and simple step-by-step instructions on what to do for that. ps: link to the photos are not working
  24. The alsamixer is right, the devices have no hardware controls, so volume must be controlled from the source player. A sound server like pulseaudio can do all the mixing and volume control though.