2740 replies to this topic

[engineerkhan15]

I would request Persian Prince to replace dts files included in the recipes with the following:

Attached Files

•  DTS Files for K1 Pro K2Pro-s905 K1 Plus.zip   28.35KB   16 downloads

Edited by engineerkhan15, 24 July 2018 - 17:48.

[algdu83]

Problem lies with the dts files included with the recipes. I replaced with the dts obtained from decompiled dtb from CoreELEC, then it boots OK. But now remote is not working, while it was working OK with last night's image.

I will share new test images shortly.

Use webif for test scan

[engineerkhan15]

New test images:

 

K1 Pro:

http://www.mediafire...24-3_sdcard.zip

 

K2 Pro (S905):

http://www.mediafire...24-2_sdcard.zip

 

K1 Plus:

http://www.mediafire...24-2_sdcard.zip

[frankviana]

New test images:

 

K1 Pro:

http://www.mediafire...24-3_sdcard.zip

 

K2 Pro (S905):

http://www.mediafire...24-2_sdcard.zip

 

K1 Plus:

http://www.mediafire...24-2_sdcard.zip

 

Good to rename this files.

 

testing now last (3) - k1 pro and k2 pro (s905)

 

I'll try to set with this command line:

 

echo "options smsmdtv default_mode=0" | tee /etc/modprobe.d/smsmdtv.conf

 

mode 0: dvb-s

mode 1: dvb-t

 

I don't know if is necessary choose, but I did this when testing my ISDB-T tuner

 

https://forums.openp...ndpost&p=884119

[frankviana]

Last image your (version 2), remote no work and no channels too (choosing too smsdtv.conf - not necessary too)

 

Downloading and testing this your (version 3). Coming soon I'll send my results (remote and scan)

Edited by frankviana, 24 July 2018 - 19:21.

[frankviana]

Testes with k1 pro

 

no remote working, no scan channels (no signal)

[moham96]

Problem lies with the dts files included with the recipes. I replaced with the dts obtained from decompiled dtb from CoreELEC, then it boots OK. But now remote is not working, while it was working OK with last night's image.

I will share new test images shortly.

I did use the coreelec dtbs in the meta-amlogic repo, the official coreelec dtbs don't have remote support because they use lirc for remote which uses meson-ir driver , while we use remotecfg tool which uses meson-remote driver, I enabled meson-remote  in the latest commits https://github.com/P...1f3af751b876686

Also I just diffed the dts files you uploaded against the dts files produced by openpli and there is no important difference, only the openvfd node that coreelec added recently(which is not important for boot) so whatever is preventing booting the dts files are not the problem

▶ diff gxbb_p200_k1_plus.dts k1plusopen 
1100,1102c1100,1102
< 	le-vfd {
< 		compatible = "le,vfd";
< 		dev_name = "le-vfd";
---
> 	openvfd {
> 		compatible = "open,vfd";
> 		dev_name = "openvfd";

~/Downloads/DTS                                                                                                                               ⍉
▶ diff gxbb_p200_k2_pro.dts k2proopen 
1100,1102c1100,1102
< 	le-vfd {
< 		compatible = "le,vfd";
< 		dev_name = "le-vfd";
---
> 	openvfd {
> 		compatible = "open,vfd";
> 		dev_name = "openvfd";

 

while it was working OK with last night's image.

can you tell which commit that made the images not bootable? try to build an image and test boot it with each commit and see what commit caused the images to not boot

 

https://github.com/P...commits/develop

0 Links

[moham96]

no boot  KI pro

 

 

k1 plus no boot

 

can you guys give more info? does the device stay on the amlogic logo or does it become black screen or what exactly ? if you guys have serial Uart output that would be great

 

Here are new test images for K1 Pro, K2 Pro (S905) & K3 Pro, compiled after latest changes.

 

K1 Pro:

http://www.mediafire...24-2_sdcard.zip

Impossible to test

not boot + problem with resolution

 

How did you know there is problem with resolution if you say it doesn't boot

[frankviana]

New test images:

 

K1 Pro:

http://www.mediafire...24-3_sdcard.zip

 

K2 Pro (S905):

http://www.mediafire...24-2_sdcard.zip

 

K1 Plus:

http://www.mediafire...24-2_sdcard.zip

 

K1 pro tests:

 

 k1.png   34.33KB   10 downloads

 

 k1.2.png   24.7KB   8 downloads

 

Log enigma2 when testing manual scan (attach)

Attached Files

•  K1 PRO_2018-07-24_16-02-30.log   26.81KB   3 downloads

[sauna]

The k1 plus logo blinks twice. The next becomes a black screen.

[frankviana]

The k1 plus logo blinks twice. The next becomes a black screen.

 

Here, k1 pro boot ok, image ok too - no necessary reinsert HDMI cable and no change skin to PLI-HD. The problem now is Grab screenshot (webif), remote and no channels scan.

[sauna]

load only when I change kernel.itb from image 01/07/2018.

[frankviana]

Automatic scan (single satellite 58ºW C Band - DVB-S)

 

Log:

Attached Files

•  K1 PRO_2018-07-24_16-38-50.log   75.76KB   9 downloads

[moham96]

 

The k1 plus logo blinks twice. The next becomes a black screen.

 

Here, k1 pro boot ok, image ok too - no necessary reinsert HDMI cable and no change skin to PLI-HD. The problem now is Grab screenshot (webif), remote and no channels scan.

 

for remote check to see if you have /dev/amremote node ?

[frankviana]

 

 

The k1 plus logo blinks twice. The next becomes a black screen.

 

Here, k1 pro boot ok, image ok too - no necessary reinsert HDMI cable and no change skin to PLI-HD. The problem now is Grab screenshot (webif), remote and no channels scan.

 

for remote check to see if you have /dev/amremote node ?

 

 

No... only /etc/amremote

 

See when appear remote (log e2)

 

[eRCInputEventDriver] devicename=meson-ir
[eRCInputEventDriver] devicename=meson-ir
[eRCDeviceInputDev] device "meson-ir" is a remotecontrol

[moham96]

The k1 plus logo blinks twice. The next becomes a black screen.

this might be an issue with the framebuffer setting up, can you reach the device in any other way (telnet, ssh) ?

[moham96]

 

 

 

The k1 plus logo blinks twice. The next becomes a black screen.

 

Here, k1 pro boot ok, image ok too - no necessary reinsert HDMI cable and no change skin to PLI-HD. The problem now is Grab screenshot (webif), remote and no channels scan.

 

for remote check to see if you have /dev/amremote node ?

 

 

No... only /etc/amremote

 

See when appear remote (log e2)

 

[eRCInputEventDriver] devicename=meson-ir
[eRCInputEventDriver] devicename=meson-ir
[eRCDeviceInputDev] device "meson-ir" is a remotecontrol

 

then you used the old  dtb, update and build image again

[frankviana]

 

 

 

 

The k1 plus logo blinks twice. The next becomes a black screen.

 

Here, k1 pro boot ok, image ok too - no necessary reinsert HDMI cable and no change skin to PLI-HD. The problem now is Grab screenshot (webif), remote and no channels scan.

 

for remote check to see if you have /dev/amremote node ?

 

 

No... only /etc/amremote

 

See when appear remote (log e2)

 

[eRCInputEventDriver] devicename=meson-ir
[eRCInputEventDriver] devicename=meson-ir
[eRCDeviceInputDev] device "meson-ir" is a remotecontrol

 

then you used the old  dtb, update and build image again

 

 

Thank you.

 

I'm using this image: https://forums.openp...ndpost&p=910968

 

Here, to build the last image, my ubutnu past more 2 days,

[sauna]

 on k1plus with the old kernel.itb amremote node no.and with native kernel.itb I can not check, black screen.via telnet, ssh, too, there is no connection

Edited by sauna, 24 July 2018 - 21:38.

[moham96]

 on k1plus with the old kernel.itb amremote node no.and with native kernel.itb I can not check, black screen.

forget about the screen for now, after you boot and see black screen try to access the device from ssh or telnet if you can the the device has booted but there is a problem with framebuffer setting

Also if you can try to use a different screen