I uploaded new test images for A10:
LibreELEC-A10.arm-9.80-devel-20200216105054-0b8cbed-mele.img.gz
LibreELEC-A10.arm-9.80-devel-20200216111916-0b8cbed-inet97fv2.img.gz
It turns out that A10 has Cortex A8 with vfpv3 for floating point coprocessor as opposed to Cortex A7 and vfpv4 on A20. This means optimizations were set wrong for A10 and of course init script crashed.
uh, A10 is Cortex-A8, but A20 is Cortex-A7. So probably A10 really needs new device type with proper CPU settings. I'll rework project a bit and upload new test image.
what would I need to clean to make either of these changes apply in the resulting image?
for second one you need just to rebuild busybox package, but for first one I suggest you rebuild whole image.
lumpi Sorry, it seems dmesg overflow, that produces much more output than anticipated. Can you re-run with "drm.debug=0x16"?
Would dmesg and kodi log as you suggested before help? Then i can try it.
yes, especially dmesg after you appended kernel arguments with that debug command
You tell then the h3 defaults to a 4k signal?
Depends on TV/monitor connected. If EDID is read, then it switches to recommended resolution. If not, it switches to 1024x768 and no sound. My TV is 4K, so it will switch to that. In your case, it should switch to 1080p. EDID should be readable even if TV/monitor is turned off, but I'm not sure if that means only in standby or also when unplugged.
Is there a way to check that it (and busybox executable) is actually on the built image..?
Not sure, but currently initramfs is in cpio archive, which starts with "070701" string.
Well, my experience is opposite. I often leave TV (LG B8) turned off and only power on SBC (doesn't matter if A64, H3 or H6). When Kodi starts, TV turns on and image is what you would expected - Kodi GUI and resolution is 4K. I heard that some devices disable DDC when they're powered off. If that's what your TVs do, then your situation is (almost) expected. Although hearing sound would suggest otherwise. Provide Kodi debug log and dmesg output and I'll check if there is anything which would explain behaviour you observed. Even better, add "drm.debug=0x1f" to extlinux.conf and get that dmesg output.
Am I doing this right? I decompiled the DTB, set status="disabled" on the first enabled usb node (and the phy which the subsequent attempt to boot complained about), compiled and replaced sun4i-a10-a1000.dtb.
yes, seems good.
but the error message is the same:
So wifi just appears to be last driver loaded, but not the cause.
jernej , which /init is this referring to? This one?
Yes.
CEC is activated in the TV, I checked.
CEC itself yes, but maybe "turn on by CEC signal" isn't? My TV has this option and it works with OPi 3.
HDMI-CEC is activated and I can navigate in Kodi with my remote control (this using the same HDMI-CEC feature, right?). Still the screen stays black if the television is off on boot time and only turned on subsequently.
I can think only two possibilities - either that function is disabled on TV or in Kodi. I would bet on the former. Well, there is still a possibility of a driver bug.
Not supported in Thoradia repo in LE OPi 3?
I wouldn't know.
Is there a way to turn on HDMI output on boot although the connected television is off?
Yes, turn on HDMI-CEC support on your TV. Note that this feature can have different name, depending on TV manufacturer. Do some research.
My question is - is it possible to get a TV out working? I found some patchwork regarding it for u-boot (and quick look at the source code revealed that there is in fact some tve related stuff), and I also found some patches for mainline armbian.
It is, it's just not a priority.
vermus Lima PR was merged few moments ago. Please test next nightly cubietruck image when it appears (~24h).
roel note that tablets can use parallel, DSI or LVDS interface. You have to check fex file to see which one is actually used on your device.
What would be a simple way to prevent jernej's build from loading the Realtek wifi drivers, to check if that's the culprit here?
The easiest that I could think of it to edit DT and remove USB node connected to wifi.
But now you say this will not work on LE because it doesn't us simple-fb?
Problem is that Kodi expects full DRM driver in order to work correctly. simple-fb is fbdev driver. You would see LibreELEC splash screen but I don't think Kodi would start.
How can I make LE picture through the projector then?
Would you say: don't bother, don't waist your time. Because this would means that LE will not work on any tablet, right?
Anything can run LE if it uses DRM driver and GPU driver which supports GBM interface. You just need to figure how to properly describe LCD panel in device tree. But I'm not right person to help you with that, I don't have experience with any output besides HDMI.
So, there is no way to add this drivers at LibreELEC? I mean myself.
You can. Just check one of those closed PRs.
it seems to activate a lcd screen it has to happen in uboot.
simple-fb (U-Boot initialized screen) is not useful for LibreELEC.
So if I build a new custom uboot, can I use a already flashed image and just dd the new uboot to the sd-card like this:
you can.
