I migrated from rk3399-roc-pc to rk3399-roc-pc-plus. After porting the audio driver, I found a problem, that is, when the HDMI is not connected when the power is turned on, the headset audio works normally, but it is plugged in when the power is turned on HDMI.the headphone audio driver does not work properly. When I tested the audio decoder chip, I found that I2S is working properly, the i2c register is configured correctly, everything is the same as when HDMI is not connected, but there is no sound, and there is only noise when the headphones come out. Or there is no sound.can you give me some advice? 
Posts by dengkx
-
-
Display More
These are not official test images for the RK33xx and rk3288 rk3188 platform.
Pay attention. Starting from version (20200826), the configuration order for the used DTB changes.
Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.
After writing the image, you must correctly configure the DTB used in the file uEnv.txtkernel 5.
Images rk3328 and r3399 and 3288 are universal, when starting from USB media images are interchangeable (the only difference is used for the image u-boot and UART console output settings). Tar archives for updating are also universal.
Note that the new generic images now use a single download directory.
Important. Changed the directory location of the images. Now all images (for all supported platforms) are in one place.
Old (not support_
https://yadi.sk/d/xhf45z3bk-joga
Add u-boot to SD card
If you have any working system on the SD card that starts normally, you will be able to check the LE. You need to try to replace the u-boot in LE, on the version with a working SD card. You need to perform a few additional steps when preparing an SD card.
1. Remove from working SD card u-boot. This can be done with this command on a Linux PC.
dd if=/dev/<name_you_SD_works_card> of=u-boot-rockpro.img bs=1M count=16
2. Write LE to SD card, configure DTB and replace u-boot with taken from working SD card. U-boot replacement is performed by two commands.
dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=1 count=442
dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=512 skip=1 seek=1
After that, you can try running LE on RockPro. The last two commands write a working u-boot and save the existing partition table for the system written to the SD card. By the way, in the same way you can replace u-boot for Armbian system and check the start of any image.
Hello, I downloaded the official LE source code. The compiled image cannot run on rk3399-roc-pc, and then it can be run using an unofficial image. I found that the problem appeared on uboot. Then replace the uboot of the official mirror with the uboot of the unofficial mirror and it can run normally. I would like to ask how this bootable uboot is compiled? Or is there a source code for the uboot?
-
You are using images not from this theme. Most likely, these are the official versions of LE, they are discussed in another topic.
append: boot=UUID=3004-5504 disk=UUID=88ad0901-c5cc-4a0d-bd82-3935bf1814cd
I don't know why the official firmware can't run, but the image under this theme can run on rk3399-roc-pc. Can you tell me how the image here is compiled, or in which version of the source code it was compiled? I am new to LE, which puzzles me.
-
Maybe this fixes it
RK fixes by knaerzche · Pull Request #5370 · LibreELEC/LibreELEC.tv · GitHub
You have to use the latest nightly image to test that will be released in a day.
Hello, using the firmware compiled with the latest source code or using the rk3399-roc-pc version firmware in "Index of/", the problem is still the same as before, and it cannot run. The unofficial firmware I found on the forum before is the only firmware it can run. I don’t know what went wrong, and I don’t know how the unofficial firmware was compiled, help me
-
Hello,I just got in touch with LE. I ran into a problem with running the system on rk3399-roc-pc. When using the official LE version to run on rk3399-roc-pc, there was a problem, but the unofficial LE version can run on rk3399-roc-pc. What is wrong with this? Where can I download the source code of the unofficial LE version?
-
Hello, I ran into a problem with running the system on rk3399-roc-pc. When using the official LE version to run on rk3399-roc-pc, there was a problem, but the unofficial LE version can run on rk3399-roc-pc. What is wrong with this? Where can I download the source code of the unofficial LE version?
-
I tried to run the system on rk3399-roc-pc, but it stopped when it reached "Starting kernel ...".In order to find the problem, I need to open the printing information after "Starting kernel...". How can I open the kernel to print the information?
-
I also had troubles getting this to work. My working SD: LibreELEC from 20210429. Also I burned a brand new SD-Card. In extlinux.conf replace rk3399-roc-pc with rk3399-roc-pc-mezzanine (if under windows you musn't use standard editor, please use notepad++ or something equivalent). I hope it will work for you...
I changed the device tree to rk3399-roc-pc-mezzanlne, and the result does not seem to change
-
I tried to run the system on rk3399-roc-pc, but it stopped when it reached "Starting kernel ...".
