What is it with the experimental DTB file for the
MXQ 4K Pro (S905) from January, 20th?
Shall we (MXQ 4K Pro owners) use that or does it
have a special function/problem solution you are
just testing for a certain user (group)?
What is it with the experimental DTB file for the
MXQ 4K Pro (S905) from January, 20th?
Shall we (MXQ 4K Pro owners) use that or does it
have a special function/problem solution you are
just testing for a certain user (group)?
kszaq About unrecognized NAND in s905x. I just tried AlexElec build. He use the same kernel version 3.14.29 and NAND is accesable
dmesg output
[ 4.244458@1] nandphy: storage 2, boot 2
[ 4.244458@1]
[ 4.249548@1] nandphy: get_storage_dev return 2
[ 4.249548@1]
[ 4.255661@1] nandphy: Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
[ 4.262368@1] nandphy: ######STS IRQ mode for nand driver
[ 4.267605@1] nandphy: NAND device id: 45 de 94 93 76 50 8 4
[ 4.273180@1] nandphy: detect NAND device: A serials NAND 8GiB SDTNRGAMA-008G
[ 4.331081@1] nandphy: clk_reg = 81000245
[ 4.331105@1] nandphy: bus_c=6,bus_t=7,sys=5.0ns,T_REA=20,T_RHOH=25
[ 4.335666@1] nandphy: new oob mode
[ 4.340351@1] nandphy: NAND CKECK:arg nbbt:arg_valid=1,blk_addr=4,page_addr=0
[ 4.352210@1] nandphy: NAND CKECK:arg ncnf:arg_valid=1,blk_addr=7,page_addr=0
[ 4.385382@1] nandphy: NAND CKECK:arg phyp:arg_valid=1,blk_addr=8,page_addr=1
[ 4.419844@1] nandphy: NAND CKECK:arg nkey:arg_valid=1,blk_addr=6,page_addr=51
[ 4.462251@1] nandphy: NAND CKECK:arg ndtb:arg_valid=1,blk_addr=9,page_addr=17
[ 4.518174@1] nandphy: NAND CKECK:arg nenv:arg_valid=1,blk_addr=10,page_addr=115
[ 4.522729@1] nandphy: nfboot :
[ 4.523382@1] nandphy: off:0x000000000000-0x000001000000 :partn=0:single_chip single_plane
[ 4.531584@1] nandphy: nfcache :
[ 4.535025@1] nandphy: off:0x00000d000000-0x000026000000 :partn=1:single_chip multi_plane
[ 4.543137@1] nandphy: nfcode :
[ 4.546582@1] nandphy: off:0x000033000000-0x00007a000000 :partn=9:single_chip multi_plane
[ 4.554693@1] nandphy: nfdata :
[ 4.558140@1] nandphy: off:0x0000ad000000-0x000153000000 :partn=1:single_chip multi_plane
Display More
kszaq About unrecognized NAND in s905x. I just tried AlexElec build. He use the same kernel version 3.14.29 and NAND is accesable
AlexELEC copies S805 and S905 from me, it's my kernel and configuration files. Which device tree did you use?
[hr]
What is it with the experimental DTB file for the
MXQ 4K Pro (S905) from January, 20th?Shall we (MXQ 4K Pro owners) use that or does it
have a special function/problem solution you are
just testing for a certain user (group)?
It is a device tree with modified partition layout: thread-3902.html Marked as experimental because I don't have a device to test.
First stock dtb from release, also gxl_p212_1g.dtb. This box is with 905x CPU and MXQ Pro case
PS. Your build with alex dtb work fine. I have to find the right dtb img. Tanks for support
First stock dtb from release, also gxl_p212_1g.dtb. This box is with 905x CPU and MXQ Pro casePS. Your build with alex dtb work fine. I have to find the right dtb img. Tanks for support
Can you please upload device tree image from this build?
Thanks Kszaq for the great work you are doing here. Just bought a Minix U1 and LibreELEC is working fine - setup was much easier than I expected especially the import of a backup from my old (Revo) box which imported everything perfectly.
However I am having a few problems with sound pass-through on your later builds - it works on 7.0.2.008-fix but is broken on 7.0.2.009 onwards (including 7.0.3 beta builds). By broken i mean no ALSA HDMI device option in Audio Settings (only Bluetooth PULSEAUDIO).
I have tried different device trees with no luck - any suggestions?
AlexELEC copies S805 and S905 from me, it's my kernel and configuration files. Which device tree did you use?
[hr]It is a device tree with modified partition layout: thread-3902.html Marked as experimental because I don't have a device to test.
Thank you, but that is weird. I am using gxbb_p200_1G_100M.dtb on exactly this box (MXQ 4K Pro) on internal NAND and external SD and it works fine on both.
Or I do not know, what problem you guys were talking (in your linked thread).
However I am having a few problems with sound pass-through on your later builds - it works on 7.0.2.008-fix but is broken on 7.0.2.009 onwards (including 7.0.3 beta builds). By broken i mean no ALSA HDMI device option in Audio Settings (only Bluetooth PULSEAUDIO).I have tried different device trees with no luck - any suggestions?
You are doing something wrong with a device tree.
I have this file s9082 from original firmware. is it usefull?
No, I need driver source code to be able to compile it.
[hr]
This is gxbb_p200_1G_100M device tree.
In Jarvis builds there should be no micro-stutter except for the videos that are known to cause issues.
[hr]
OP udated with 7.0.3.012d build. I switched my development focus to Krypton builds now, so this is very little tested but the changes are very minor. In case anything stops working, 7.0.3.012c is still available.Please report if Bluetooth still works in this build if you have AP6xxx WiFi/BT chip. I have used an alternative way to load BT firmware in this build which should make BT work for AP6212A.
Unfortunately bluetooth is not working on my AP6212A using the 7.0.3.012d build. "No Bluetooth adapter is found".
Unfortunately bluetooth is not working on my AP6212A using the 7.0.3.012d build. "No Bluetooth adapter is found".
Thanks for trying. Can you please grab and post systemctl status | paste and ps | paste?
Thanks for trying. Can you please grab and post systemctl status | paste and ps | paste?
Sure thing.
Hi to everyone. Thank's to kszaq, I'm an happy user on S805 since first releases. Reading the various posts I would like to understand what you think is the best device S905 for these builds and maybe next release, tips?
Thanks. Please also grab
udevadm info /sys/bus/mmc/devices/sdio\:0001/sdio\:0001\:*
systemctl status brcmfmac_sdio-firmware-aml.service.
Also check if systemctl start brcmfmac_sdio-firmware-aml.service makes BT available?
Thanks. Please also grab
udevadm info /sys/bus/mmc/devices/sdio\:0001/sdio\:0001\:*
systemctl status brcmfmac_sdio-firmware-aml.service.Also check if systemctl start brcmfmac_sdio-firmware-aml.service makes BT available?
Yep.
systemctl start brcmfmac_sdio-firmware-aml.service didn't enable BT.
Thanks. Please also grab
udevadm info /sys/bus/mmc/devices/sdio\:0001/sdio\:0001\:*
systemctl status brcmfmac_sdio-firmware-aml.service.Also check if systemctl start brcmfmac_sdio-firmware-aml.service makes BT available?
Hi,
It turns out these Broadcom chips need a few reset retries after firmware upload. brcm_patchram already does this but hciattach just times out.
Here is a patch to fix hciattach, enjoy.
Hi,It turns out these Broadcom chips need a few reset retries after firmware upload. brcm_patchram already does this but hciattach just times out.
Here is a patch to fix hciattach, enjoy.
Great, thank you a lot!
Have you tried using sleep / nosleep option with hciattach? I'm curious whether this could resolve this as well.