2740 replies to this topic

[moham96]

another thing, pay attention to the led on the tv box, it should blink blue and red after about 10 to 15 second of booting, if it does then there is definitely something wrong with the framebuffer

[sauna]

No blinking. Only the blue LED lights up. It's not possible to connect to telnet.

[moham96]

No blinking. Only the blue LED lights up. It's not possible to connect to telnet.

very strange, I see no error on my side, and I don't see anything in the repo that might be causing the issue, We should wait for engineerkhan15 to bisect the commits since he knows how to build and he can reproduce the issue.

[engineerkhan15]

 

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

 

Yes I can try that, can you guide how to disable all commits and enable one by one for building the image?

Since I have only K1 Pro, so I will try this for K1 Pro only, so that I may test those images myself.

[Persian Prince]

Since now we have k2pro (old version = s905) and k2prov2 (new version = s905d), so update and use new names please

 

For aio-grab I think you need to investigate this: https://github.com/O...ter/main.c#L287

[ftp21_]

To speed up the avl6862 test how i can compile only this kernel modules? 

 

 

How i can add dvbtools utilities?

Edited by ftp21_, 25 July 2018 - 07:36.

[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

 

Yes I can try that, can you guide how to disable all commits and enable one by one for building the image?

Since I have only K1 Pro, so I will try this for K1 Pro only, so that I may test those images myself.

 

well if you're not familiar with git then wait untill i finish the build I'm running and I will build iimages for each commit if I can and you guys can test it

I had to reset the build so It is building from start so this might take some time, sit tight

[Persian Prince]

There is no need to remove the "build" directory completely, just use https://github.com/P...leanup-build.sh and cleanup old machines

[moham96]

There is no need to remove the "build" directory completely, just use https://github.com/P...leanup-build.sh and cleanup old machines

I didn't remove the build directory, I added multilib for my local.conf so I can have 32bit and 64bit libraries (to investigate the dvb problem more) which caused the build to rebuild every package

[moham96]

To speed up the avl6862 test how i can compile only this kernel modules? 

 

 

How i can add dvbtools utilities?

avl6862 and r848a drivers are part of the coreelec kernel so you'd have to build the kernel, but if you want you can clone the coreelec kernel and only build the modules from that(outside bitbake world) and then push the resulting .ko files to the device and load them with insmod avl6862.ko(remember to rmmod the already loaded modules)

[ftp21_]

 

To speed up the avl6862 test how i can compile only this kernel modules? 

 

 

How i can add dvbtools utilities?

avl6862 and r848a drivers are part of the coreelec kernel so you'd have to build the kernel, but if you want you can clone the coreelec kernel and only build the modules from that(outside bitbake world) and then push the resulting .ko files to the device and load them with insmod avl6862.ko(remember to rmmod the already loaded modules)

 

 

If i execute this command

MACHINE=k1pro bitbake -C compile -f virtual/kernel 

where i find ko modules?

[moham96]

 

 

To speed up the avl6862 test how i can compile only this kernel modules? 

 

 

How i can add dvbtools utilities?

avl6862 and r848a drivers are part of the coreelec kernel so you'd have to build the kernel, but if you want you can clone the coreelec kernel and only build the modules from that(outside bitbake world) and then push the resulting .ko files to the device and load them with insmod avl6862.ko(remember to rmmod the already loaded modules)

 

 

If i execute this command

MACHINE=k1pro bitbake -C compile -f virtual/kernel 

where i find ko modules?

 

well If you build with bitbake it's easier to use the ipk packages which you can find here

build/tmp/deploy/ipk/k2pro_s905/kernel-module-avl6862-3.14.29_3.14.29-.2_k2pro_s905.ipk

of course replace k2pro_s905 with your machine

the above file is for the avl6862 demodulator module

for dvb on mecool device you need avl6862, r848a, aml and aml_fe. 

build/tmp/deploy/ipk/k2pro_s905/kernel-module-aml-3.14.29_3.14.29-.2_k2pro_s905.ipk
build/tmp/deploy/ipk/k2pro_s905/kernel-module-aml-fe-3.14.29_3.14.29-.2_k2pro_s905.ipk
build/tmp/deploy/ipk/k2pro_s905/kernel-module-avl6862-3.14.29_3.14.29-.2_k2pro_s905.ipk
build/tmp/deploy/ipk/k2pro_s905/kernel-module-r848a-3.14.29_3.14.29-.2_k2pro_s905.ipk

copy those files to the target and use opkg install to install each one of them

[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

 

Yes I can try that, can you guide how to disable all commits and enable one by one for building the image?

Since I have only K1 Pro, so I will try this for K1 Pro only, so that I may test those images myself.

 

Ok can you try these images and tell me which one works and which one doesn't ?(these are k1 pro images)

https://drive.google...DtRaQt2tpO7ZVUE

[moham96]

For aio-grab I think you need to investigate this: https://github.com/O...ter/main.c#L287

the osd screenshot can be solved easily, for video capture It's more tricky I think we need correct /proc/stb/vmpeg/0/xres and /proc/stb/vmpeg/0/yres nodes to be able to capture video

[ftp21_]

How i can i add dvbtools like scan or w_scan ?

I'm at office and i cant attach hdmi to scan

[moham96]

How i can i add dvbtools like scan or w_scan ?

I'm at office and i cant attach hdmi to scan

MACHINE=k1pro bitbake dvblast
MACHINE=k1pro bitbake dvbsnoop
MACHINE=k1pro bitbake wscan
MACHINE=k1pro bitbake dvbtune
MACHINE=k1pro bitbake bitstream

I think those are the only available tools for dvb (we should add dvb-apps recipe)

 

[ftp21_]

 

How i can i add dvbtools like scan or w_scan ?

I'm at office and i cant attach hdmi to scan

MACHINE=k1pro bitbake dvblast
MACHINE=k1pro bitbake dvbsnoop
MACHINE=k1pro bitbake wscan
MACHINE=k1pro bitbake dvbtune
MACHINE=k1pro bitbake bitstream

I think those are the only available tools for dvb (we should add dvb-apps recipe)

 

 

I'm investigating a lot on avl driver.

The driver don't switch the mode and we have the error.

 

I'm trying to modify to add 3 frontend (S/T/C)

[mrvica]

https://packages.deb...utils/dvb-tools

https://packages.deb...sid/main/w-scan

yüo´ll probably need some libs, you can download them there too

[moham96]

 

 

How i can i add dvbtools like scan or w_scan ?

I'm at office and i cant attach hdmi to scan

MACHINE=k1pro bitbake dvblast
MACHINE=k1pro bitbake dvbsnoop
MACHINE=k1pro bitbake wscan
MACHINE=k1pro bitbake dvbtune
MACHINE=k1pro bitbake bitstream

I think those are the only available tools for dvb (we should add dvb-apps recipe)

 

 

I'm investigating a lot on avl driver.

The driver don't switch the mode and we have the error.

 

I'm trying to modify to add 3 frontend (S/T/C)

 

That would be great, I have many updates for mecool devices that I hesitate to push without a working dvb drivers

[sauna]

may be useful for your work.

 

https://yadi.sk/d/GnnSoGTo3ZbFmE