I just updated my
MiniMx 2g/16g S905 Non Branded Beelink
LE Internal 7.0.3.012eNever connects to Wifi unless i toggle Wifi settings off/on
Lost Bluetooth as well. Cannot see my keyboard.
Logs, please... You can downgrade to previous versions without data wipe.
My question is how do I find which type of memory my box has Nand or eMMC ??? I have not yet had time to take the rsik and try the nand dtb yet but though I would ask first here to see where I can discover what type my MXQ M12cx S905X metal cased box has.
The answer is quite simple: if the installtointernal script works you don't have to worry about this. If it fails finding internal memory you will see errors but nothing bad will happen.
I have pushed an updated Python patch to my libreelec-7.0 branch (updated by Raybuntu) so that you won't have to remove Python patches when building for aarch64. I will do the same in libreelec-8.0 branch.
For kernel config you can simply create a symlink in linux folder linux.aarch64.conf -> linux.arm.conf so that with every pull/checkout it will link to latest kernel config.
The build issues you are facing seem to be your machine-specific, I didn't push any changes that could break building in that way.
Unfortunately I cannot check building for aarch64 every time as I don't have enough resources to do that - I compile on my laptop and building for different arch requires a whole new build folder that consumes quite a few GBs. That said I try not to do any changes that can break aarch64.
Would this be ok to compile with 32bit userspace? "PROJECT=S905 ARCH=arm make amlpkg" (and again with ARCH=aarch64 for 64bit userspace?)
Source code is ready to compile 32-bit userspace only. To compile for aarch64 you need to delete this patch: Python-32bit-usespace-workaround.patch and rename (or copy) linux.arm.conf to linux.aarch64.conf. Remember that the main reason for 32-bit userspace is memory leak that has not been fixed.
Would changing "CONFIG_AML_TEMP_SENSOR" in linux.arm.conf be enough to compile with temp-sensor enabled vs disabled?
You also need to disable SARADC.
Are there any changes necessary to prepare for dual boot support or is the source code ready for SD boot as well as internal nand install?
It's ready.
OP updated with 7.0.3.012e build.
Hi kszaq,can you comment this?
Are you aware of these issues and will they be fixed in a future release?
Unfortunately I don't know much about the decoder, I can't promise they will be fixed. At the same time I don't see any frame skips except when browsing GUI during playback.
Will this auto install to internal nand or do I still need to ssh installtointernal?
What is the difference between the NAND version and the regular one?
I'm not sure you fully understand that this is a device tree. You should use it in case you have S905X box with NAND (not eMMC) and your internal memory is not detected using a regular device tree.
afl1 I undestand that you compiled TVHeadend in project without media_build, correct? I am trying to understand how I can fix my binary.
kszaq: Pls update in repository broken tvheadend42.
Where can I find a patch to fix it?
Also maybe it's a good idea to leave the init speed to the default http://git.kernel.org/cgit/bluetooth/blu...ach.c#n993
but the default final speed (3000000) doesn't seem to work. Maybe we should use standard baud rates for the final speed (thought I didn't try to optimize this yet) e.g.:
115200
230400
460800
921600
The speeds that we need to use is 115200 for initial communication and 2000000 afterwards. Thank you for the patch, I will include it in my next build!
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.
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?
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?
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.
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?
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.
Thanks for the info.But I did see very subtle micro-stutters during playback, is there another reason? Maybe some A/V syncing in the background?
There were no frame skips or drops.
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.
