Posts by The Coolest

hashmaker

add ; after fd628_display_type = /bits/ 32 <1>

It has to be like this:

fd628_display_type = /bits/ 32 <1>;

hashmaker

Ok, try this one.

hashmaker

Please attach the DTS file and I'll see if I can help you.

You have a T95M 1GB RAM?

Also post dmesg log. (SSH into the box, type in 'dmesg | paste'. Then copy the link here.

Tim_Taylor

Should work in 8.x, I have it running on 7.0

darioml  Tim_Taylor

Thanks for confirming that the DTB configuration is correct. I'll upload the source today after work.

GDPR-2

Sure. Thanks for the link.

b0mb

I think it would have been a lot more helpful if you also attached logs and perhaps ran 'top' from SSH to see which process is hogging the CPU.

darioml  Tim_Taylor

Does the LCD work correctly for you? Does it display time and icons? Is the time right side up?

GDPR-2

I'm making a list of device trees, but before I submit them I want to make sure that they work correctly. The only ones I'm positive about working correctly are for T95M, which I attached now, and you have the TX3 one. I'm not sure about this DTS being the final version either, the new 'display-type' property may require some more work.

I'm still working with someone to get the LCD to work correctly on his S912 X92 box, I think I got it, but waiting for his confirmation.

darioml  GDPR-2  Tim_Taylor

From the attached Android DTB, it looks like the GPIO pins are different, so the X92 DTB will not work for the display on the Veroke.

I adjusted the values according to the zip you attached, hopefully it'll work now, please try this DTB.

hashmaker GDPR-2

I believe that the FD628 section is identical to the one in used in my box too, which is a Sunvell T95M 2G/8G.
You can probably use the DTS I PMed you for this box too, only switch over to the gxl_p212_1gb DTS as the include.

hashmaker

Edit the LE DTB. You will have to figure out the correct values for the gpio configuration, you'll have to put the values in numerically.

You can get the pin numbers from the /proc/device_tree/fd628_dev folder when in Android.

But the port address may differ between Android and LE, so you'll have to find the number of your port by searching the decompiled DTB for 'bank' and 'ao-bank'. The 'phandle' value represents the port number.

Also you can use this file to reference the pin numbers to their names to see what port (bank) value you should use.

kernel/meson-gxl-gpio.h at master · openSUSE/kernel · GitHub

hashmaker

If you have linux on a computer, you can install 'dtc', it's a device tree compiler.

You'll be able to decompile your device tree, add the bit you need for the display and compile it back into a binary the box can use.

Quote from hashmaker

Can i try too if the display is not light up but the modules are loaded ?

You can try, but if the display doesn't light up at all, the app will probably do nothing.

Without the correct device tree, the display will not work.

GDPR-2

For everyone running the latest build/version with a box that has a display on the front:

If your display lights up (meaning the DTB is OK), but does not work correctly (e.g. incorrect character order, or weird symbols displayed instead of numbers, etc), I made a small test app that will help me/us figure out how the LCD is connected and mapped internally for your particular box.

See attachment for the app and instructions below:

1. Unzip it into the box (I used the downloads folder)

2. SSH into the box.

3. type in 'bash test_lcd.sh' and then enter.

This will unload the firmware LCD driver and load the test driver+app.

It will run through 2 tests:

1. It will light up all sections of each character, one by one. This will help us pin point which character is assigned to what numeric index. (like which char for index=0, which one for index=1 etc.)

2. It will light up one section in all chars, one by one. This should help us see the bitmap indexes of each char.

*. A video of the box cycling through this test app will be the best help for me to get it working on your display.

After you're done, simply reboot the box to go back to 'normal'.

Quote from adamg

LE7 is really old now, can you not update?

The dts is built with the kernel, if you 'cd' to the kernel directory you should be able to compile with 'make xxx.dtb'

You can build the service with 'scripts/create_addon fd628'

fd628-aml in packages/linux-drivers/amlogic/fd628-aml is the kernel driver package needed

fd628 in packages/addons/service/fd628 is the addon service needed

Display More

Thanks, I'll give that a try tomorrow after work.

I still have LE7 on this particular box because it's primarily used for watching IPTV, and it seems that it works a lot better than LE8.2. Channel switching is a lot quicker. My mother uses it most of the time, so stability is extremely important and also, having it "behave" a certain way is important too. For IPTV and a bit of YouTube LE7 works extremely well. The box I have connected to my TV is a T95N, so no display on it, it's also hidden from sight, and I have the latest 8.2 release on it.

Quote from adamg

Can you make a dts with the original values for the TX3 mini and use the GPIO settings here gxl_p212_2g_tx3mini.dts so I can test it on the TX3 mini, if you want your modified DTB to be included in all future builds send me a copy of it with the fd628_chars specified in it as well, thanks.

I will be doing 8.90.3 a little earlier than I expected so it would be nice to try and squeeze this in if it works well.

Edit: I've tested your changes along with an updated dtb for my device and they all work, so just send me your DTS, also make sure you install the fd628 service via addons if you want the extra icons lit up

Awesome! I'm excited to have been able to contribute something to the LE project

It was 6am, so I had to go to bed, I see that you accepted my changes. Cool

Attached is the DTS file I used for my box. Not sure whether the config on the 1g T95M is the same or not though.

I installed the service right away, and yeah, it works and the status dots are working.

On a related note. I wanted to ask, how can I build the DTS from the terminal? For my tests I copied over the DTS files, the dt-bindings folder, and though it worked, it was a bit of a pain.

And since I'm trying to get this to work seamlessly on LE7, I'm trying to figure out how to add the service.fd628 to the repo during the build. So that I can install it without having to install it manually from a zip file. I added it to the 'packages/addons/service' folder, exactly like it's in your master repo, but it doesn't seem to be included.

Quote from adamg

That's great, it looks similar to how anpaza is doing it in his vfd driver, I think we could use this to expand support to more devices with the display.

The whole driver needs cleaning up and beautifying really.

Where are you getting the values for fd628_chars and fd628_dot_bits?

Yeah, the code has a lot of junk, but I didn't want to touch it too much.

The fd628_dot_bits will probably just work out of the box for all boxes, but I added this property just in case.

The values in fd628_chars are set up to work with my box, but I hope it shouldn't be too difficult to configure them for other boxes. Each number represents the 'index' of the respective character on the display.

So for my box index 0 is the 'dots' character, 1 - the hour x10, 2 - the hours, etc.

For other boxes the order of these indexes will have to be different if they are wired differently internally.

GDPR-2

When you have time, please take a look at this:

GitHub - arthur-liberman/tx3mini_linux_fd628

(sorry for the mess with commits and merges, I'm still a bit new to github)

I added a sample.dts to show the new device tree properties.