for max-frequency I based it on a DTS with the same emmc (a samsung iot dev platform) and on another box that uses the same eemc component (an Amlogic Phicomm N1 box) => max-frequency = <0x2faf080>.
thank you, try again
for max-frequency I based it on a DTS with the same emmc (a samsung iot dev platform) and on another box that uses the same eemc component (an Amlogic Phicomm N1 box) => max-frequency = <0x2faf080>.
thank you, try again
Hi ilmich ,
Same thing : not working
I'm going to check the changes I've made on my side (and how work fine) and I'll get back to you soon (with an MR I think), I'm out of town for the next two weeks...
See you soon!
log:
INF TEE-CORE:rockchip_cpu_suspend:217: 1.1.0-333-gc9d95d1 #2 2018年 08月 17日 星期五 03:32:22 UTC arm v2.0
012345Am6DDR Version V1.11 20200910_dbg
In
ID:0xFFF
330MHz
DDR3
Bus Width=16 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
mach:3
OUT
Boot1 Release Time: May 13 2019 17:02:59, version: 2.56
ChipType = 0xc, 380
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=1000
UserCapSize=7456MB
FwPartOffset=2000 , 1000
SdmmcInit=0 NOT PRESENT
StorageInit ok = 48837
SecureMode = 0
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x63337df8 signature is wrong
recovery gpt...
GPT 0x63337df8 signature is wrong
recovery gpt fail!
LOADER Check OK! 0x60200000, 126700
TOS Check OK! 0x68400000, 149056
Enter Trust OS
INF [0x0] TEE-CORE:init_primary_helper:377: Initializing (1.1.0-333-gc9d95d1 #2 2018年 08月 17日 星期五 03:32:22 UTC arm)
INF [0x0] TEE-CORE:init_primary_helper:378: Release version: 2.0
INF [0x0] TEE-CORE:init_primary_helper:379: Next entry point address: 0x60200000
INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
U-Boot 2017.09 (May 15 2024 - 19:18:08 +0200)
Model: Rockchip RK322x SoC (eMMC)
PreSerial: 2
DRAM: 2 GiB
Sysmem: init
Relocation Offset is: 00000000
MMC: dwmmc@30000000: 1, dwmmc@30020000: 0
Using default environment
In: serial@11030000
Out: serial@11030000
Err: serial@11030000
Model: Rockchip RK322x SoC (eMMC)
Bootdev(atags): mmc 0
mmc_init: -110, time 31
rockchip_get_bootdev: can't find dev_desc!
rockchip_get_boot_mode: dev_desc is NULL!
CLK: (sync kernel. arm: enter 600000 KHz, init 600000 KHz, kernel 0N/A)
apll 600000 KHz
dpll 660000 KHz
cpll 500000 KHz
gpll 594000 KHz
armclk 600000 KHz
aclk_bus 74250 KHz
hclk_bus 37125 KHz
pclk_bus 37125 KHz
aclk_peri 74250 KHz
hclk_peri 37125 KHz
pclk_peri 37125 KHz
Net: eth0: ethernet@30200000
Hit key to stop autoboot('CTRL+C'): 0
MMC: no card present
mmc_init: -123, time 2
mmc_init: -110, time 31
starting USB...
USB0: Core Release: 3.10a
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Device 0: unknown device
DMA reset timeout
Display More
Hi guys, im new here.
First of all, thanks for the work you've done, i've been reading and its a lot of passion here.
I recently got a MXQ PRO 5g 4K:
*Rockchip RK3229
I installed LibreELEC and works but my Wi-Fi Card is not working, can you help?
I'd ask ilmich to bump the kernel to something newer than Linux 6.1.y as there are improvements/fixes to the rtl8xxxu driver that might benefit things for an RTL8723BU chip. That might not be a simple exercise though, and his time is limited. In the longer term support should be added to the rtw88 driver, but that effort is still in early stages.
Plan B .. (or C) .. use an external USB wifi device or something that's powered from USB but presents an Ethernet interface (so there are no drivers involved).
Hi guerrero2694,
You could provide the reference of the board (you have to remove the 4 screws hidden behind the little anti-slip pads).
I also bought a model with the same reference "MXQ PRO 5g 4K" recently (today ), the reference of my card inside is: r29_5g_lp3_v3.0 231005
I quickly tested the tvbox (on libreelec with r29 dtb):
boot on SDcard : ok
Ethernet: OK
HDMI/video playback: ok
USB : OK
console UART Ok (requires soldering)
maskrom pin : I'll need to look for it...
Install to emmc : NO OK ( strange thing is that if I boot with multitool, and then reboot with quick removing the SD card, I manage to boot correctly... otherwise on cold boot the emmc is not detected by the uboot..)
wifi : no detected
For info => Android GPIO debug + dmesg :
That might not be a simple exercise though, and his time is limited.
I'm starting to work on libreelec 12, but unfortunately, it's true that I have little time available.
pocng , do you have a link to the Android firmware of your box (alternatively also the first ~100mb of a dump of the internal memory) ? I looked at the logs and you should have a Broadcom BCM4330 wifi chip which is supported by the mainline kernel. If it's not detected, the correct gpio that enables it probably needs to be added, but I need the android dtb.
guerrero2694 as pocng said, try sending a photo of the board
Hi ilmich
You will find on this share : http://sandbox02.poc.ng/tvbox/r29/
- the backup made with multitools
- 100MB first rom backup (FIRST100MB-R29_5G_LP3_V3.0-231005_mxqpro4k.img.xz)
- the android device tree in FS mode (R29_5G_LP3_V3.0-231005_android_dtbfs.tar.gz )
- the source device tree created from devicetree fs android (R29_5G_LP3_V3.0-231005_android.dts)
- the gpio kernel debug file (R29_5G_LP3_V3.0-231005_gpio.txt)
- Board pictures (R29_5G_LP3_V3.0-231005-Photos.pdf)
guerrero2694 can you confirm that you have the same? (look http://sandbox02.poc.ng/tvbox/r29/R29_…1005-Photos.pdf)
Hi guys, thank you for your response, i decided to return the TV box. I will try to get the chips that are official to Libreelec.
Sorry for the troubles, but i managed to take a pic of the board. It is not the same pocng
Hi @ilmich,
I quickly checked the GPIOs for Wlan and so far I haven't found the source of the problem. At first glance, the pins are indeed those defined in the dtb...
To help me identify the pinctrl from the gpio kernel debug file, I've made myself a correspondence table, I don't know if it can help other people but i share it here : http://sandbox02.poc.ng/tvbox/rk322x_linux_gpio.txt
WIP :
* From Extract info from android DTS:
WIFI,host_wake_irq = <0x75 0x1c 0x00>; => gpio0/RK_PD4
WIFI,poweren_gpio = <0x7c 0x1a 0x00>; => gpio2/RK_PD2
BT,power_gpio = <0x7c 0x1d 0x00>; => gpio2/RK_PD5
uart_rts_gpios = <0xa9 0x06 0x01>; => gpio3/RK_PA6
BT,wake_gpio = <0xa9 0x1b 0x00>; => gpio3/RK_PD3
* From dmesg
[ 5.250216] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 102. => GPIO3 RK_PA6
[ 5.250334] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,power_gpio = 93. => GPIO2 RK_PD5 => rk322x.dtsi =??=> uart0-cts (rockchip,pins = <2 RK_PD5 1 &pcfg_pull_none>;)
[ 5.250466] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 123. => GPIO3 RK_PD3
[ 5.250604] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 122.
[ 4.789424] export led gpio: 39 => GPIO1 RK_PA7
/* defined in android dtb but fd650 not present */
[ 4.965395] fd650_devs_get_of_pdata sda gpio:13 => GPIO0 RK_PB5
[ 4.965530] fd650_devs_get_of_pdata scl gpio:116 => GPIO3 RK_PC4
* from /sys/kernel/degub/gpio
GPIOs 0-31, platform/pinctrl.17, gpio0:
gpio-13 (fd650_sda ) out hi GPIO0 RK_PB5 /* fd650 controle not present */
GPIOs 32-63, platform/pinctrl.17, gpio1:
gpio-35 (spk_ctl ) out lo GPIO1 RK_PA3
gpio-39 (power-led-normal ) out lo GPIO1 RK_PA7
GPIOs 64-95, platform/pinctrl.17, gpio2:
gpio-72 (phy_led ) out lo GPIO2 RK_PB0 /* orange led */
gpio-75 (power-hold ) in lo GPIO2 RK_PB3
gpio-90 (wlan_default_wlan_po) out hi GPIO2 RK_PD2
gpio-93 (ap6335_poweron ) out lo GPIO2 RK_PD3
GPIOs 96-127, platform/pinctrl.17, gpio3:
gpio-102 (ap6335_rts ) in hi GPIO3 RK_PA6
gpio-116 (fd650_scl ) out hi GPIO3 RK_PC2 /* fd650 controle not present */
gpio-117 (phy_link ) out lo GPIO3 RK_PC3
gpio-118 (otg_drv_gpio ) out hi GPIO3 RK_PC4
gpio-119 (power ) in hi GPIO3 RK_PC5
gpio-121 (menu ) in hi GPIO3 RK_PC7
gpio-122 (ap6335_wake_host ) in hi GPIO3 RK_PD2
gpio-123 (ap6335_wake ) in hi GPIO3 RK_PD3
Display More
To be continue ...
Hi @ilmich,
I once again fell for a box on special offer for less than $7 (including postage, just received), an H20 (board tagged H20-221-1.8-B).
The DTS decompiled from Android is almost identical to the DTS of the R2 _5G_LP3_V3.0-231005 box (quoted posts above but another wifi chipset).
With the "R29" DTB:
Boot on SDcard: OK
Ethernet: OK
HDMI/video Playback : OK (for over 3 hours)
Power/Standby LED : OK
UART Port Pin : OK
SDIO WIFI : not detected => wifi is sdio 02e7/9086 / smartchip sci S9082H (on armbian forum i can see : its a clone of some wifi rtl chips , its closse source , no linux support)
I've added this tvbox info (photo, android dts, backup...) to this share: http://sandbox02.poc.ng/tvbox/H20-221-V1_8-B/
Hi @ilmich,
I quickly checked the GPIOs for Wlan and so far I haven't found the source of the problem. At first glance, the pins are indeed those defined in the dtb...
To help me identify the pinctrl from the gpio kernel debug file, I've made myself a correspondence table, I don't know if it can help other people but i share it here : http://sandbox02.poc.ng/tvbox/rk322x_linux_gpio.txtCode Display MoreWIP : * From Extract info from android DTS: WIFI,host_wake_irq = <0x75 0x1c 0x00>; => gpio0/RK_PD4 WIFI,poweren_gpio = <0x7c 0x1a 0x00>; => gpio2/RK_PD2 BT,power_gpio = <0x7c 0x1d 0x00>; => gpio2/RK_PD5 uart_rts_gpios = <0xa9 0x06 0x01>; => gpio3/RK_PA6 BT,wake_gpio = <0xa9 0x1b 0x00>; => gpio3/RK_PD3 * From dmesg [ 5.250216] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 102. => GPIO3 RK_PA6 [ 5.250334] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,power_gpio = 93. => GPIO2 RK_PD5 => rk322x.dtsi =??=> uart0-cts (rockchip,pins = <2 RK_PD5 1 &pcfg_pull_none>;) [ 5.250466] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 123. => GPIO3 RK_PD3 [ 5.250604] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 122. [ 4.789424] export led gpio: 39 => GPIO1 RK_PA7 /* defined in android dtb but fd650 not present */ [ 4.965395] fd650_devs_get_of_pdata sda gpio:13 => GPIO0 RK_PB5 [ 4.965530] fd650_devs_get_of_pdata scl gpio:116 => GPIO3 RK_PC4 * from /sys/kernel/degub/gpio GPIOs 0-31, platform/pinctrl.17, gpio0: gpio-13 (fd650_sda ) out hi GPIO0 RK_PB5 /* fd650 controle not present */ GPIOs 32-63, platform/pinctrl.17, gpio1: gpio-35 (spk_ctl ) out lo GPIO1 RK_PA3 gpio-39 (power-led-normal ) out lo GPIO1 RK_PA7 GPIOs 64-95, platform/pinctrl.17, gpio2: gpio-72 (phy_led ) out lo GPIO2 RK_PB0 /* orange led */ gpio-75 (power-hold ) in lo GPIO2 RK_PB3 gpio-90 (wlan_default_wlan_po) out hi GPIO2 RK_PD2 gpio-93 (ap6335_poweron ) out lo GPIO2 RK_PD3 GPIOs 96-127, platform/pinctrl.17, gpio3: gpio-102 (ap6335_rts ) in hi GPIO3 RK_PA6 gpio-116 (fd650_scl ) out hi GPIO3 RK_PC2 /* fd650 controle not present */ gpio-117 (phy_link ) out lo GPIO3 RK_PC3 gpio-118 (otg_drv_gpio ) out hi GPIO3 RK_PC4 gpio-119 (power ) in hi GPIO3 RK_PC5 gpio-121 (menu ) in hi GPIO3 RK_PC7 gpio-122 (ap6335_wake_host ) in hi GPIO3 RK_PD2 gpio-123 (ap6335_wake ) in hi GPIO3 RK_PD3
To be continue ...
maybe you have already sent it, but could you please send me a dmesg? at this point the problem could be elsewhere.
SDIO WIFI : not detected => wifi is sdio 02e7/9086 / smartchip sci S9082H (on armbian forum i can see : its a clone of some wifi rtl chips , its closse source , no linux support)
I found this driver
I don't like it much but I can try.
Hi ilmich
When I wrote that the wifi card is not detected, it's because I don't have any SDIO device information in the dmesg (dmesg | grep -i sdio => nothing). I think I've got a DTS problem, probably something missing...
I've read the article https://community.silabs.com/s/article/linu…?language=en_US and for the moment it's not a driver problem but more a mmc/sdio dts config problem, I'm going to have another look at the configs and prepare debug files to share. (same things with r29 tv box posted above...)
Thanks for rtl8822bs-aml git projet, I'll test it as soon as I get to detect SDIO
PS: for the r329q v3.1 I've finally made the merge request for boot support on the emmc and share this patched LibreElec built here
PS2: the Android dmesg / dts / firmware / pictures for H20 and R29 box is shared here
I flashed my rk3328a MXQ Box and it seems to works just fine.
But there's one big issue, most of my TV outputs only at 1024x768 (LG and Sony TVs) and without any kind of audio. Sometimes a power cycle fix it but the issue seems to be popping up randomly every boot. But some of my TVs dont really like the TV box at all, it just outputs with unsupported resolution (Samsung TV). And finally I tested it with a cheap dumb TV from china it works but as I said earlier limited to 1024x768 with no audio as well, and here's a weird thing, that cheap tv detects the signal as DVI instead of HDMI.
BTW, I dont have any kind of issue regarding to video and audio output on this thing via HDMI with a Android ROM on it. The cheap chinese tv now detects it as a proper HDMI signal instead of DVI.
Hi remlei
Can you share kodi and dmesg logs?
Can you open your TV BOX and take some photos?
MXQ Box have lot of different hardware revision...
Regards,
pocng
hi pocng
it's because I don't have any SDIO device information in the dmesg
that's correct, if you don't see this
at least it means that the wifi card is not active. I looked at the DTS and it seems to me to be the usual pin (90 --> gpio2 PD2) so the problem is really strange.
Thanks for rtl8822bs-aml git projet, I'll test it as soon as I get to detect SDIO
in this image, I have compiled the driver I was telling you about. the source is here (I forked) https://github.com/rockchip-with-…rtchip-sci-wifi
PS: for the r329q v3.1 I've finally made the merge request for boot support on the emmc and share this patched LibreElec built here
Thanks so much, I'll take a look at it as soon as I can
remlei I imagine you also tried changing the HDMI cable. In any case, the problem is that the edid is not read correctly (so basically your TV is not correctly detected). this can happen if the HDMI cable is of poor quality, or the TV returns an EDID not correctly recognized by the driver.
Android in these cases sets the resolution fixed to 720p with audio. Linux instead at 768p without audio.
The best thing would be to understand if this is the problem (I'm pretty sure it is) because I could simulate what android does but you miss out on all the other resolutions.
So, as requested, please send a log (tutorial here https://wiki.libreelec.tv/support/log-files)
Thanks again for the effort you put on this, ilmich .
Wich skins are you guys using with the latest build? I like AH2, but I think it is too much to this little board to handle
jaum20 I use estuary and my builds are optimized for this skin. personally on the boxes with ddr2 I tried pellucid for a period but estuary is the best currently.
However, try this pre-release build if you have an extra SD card.
there are some kodi optimizations that use smaller textures (lower quality but less stress on the cpu/gpu). Even third party skins should be better (I tried arctic fuse and it's not too bad)