-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenVFD: Failed to verify VFD config file, attempt using device tree #13
Comments
Very hard for me to understand what you were trying to do, but in the last dmest output, you can see that it successfully started the driver. |
I am unaware of the addon, so i’ll try it when I get the chance. In the example though I am only trying to set up the module with modprobe, and then I try running the service. The services manages to run successfully the second time (even though it fails and errors out the first time), and it seems like the biggest issue at hand is failure to read vfd.conf parameters. Some background on my system since I forgot to mention… im running armbian on a tx mini 3 box with a S905W chip and an FD6551 controller. I’ve noticed other people succeeded in controlling the LCD with the same model so I should be able to do the same. |
Ah sorry, I reread what you did. |
Regardless of how I declare the display type, it still has issues with vfd.conf. Here's after changing the conf file, modprobe, and starting the openvfd service :
Notice if I run systemctl start openvfd.service right after, it magically succeeds and starts the service. This time I set it to the right controller, but it still bugs out and refuses to actually do anything when I run the demo code:
dmesg:
It seems you're right about the conf file in that it does get passed the second time around. Executing the test demo however always results in this:
At 87 I ran the demo script and it instantly changed the controller. |
Update: I enabled openvfd.service with systemctl so it starts on boot. It got rid of the error modprobe throws me, and it seems that the module + service are working fine. When I run the demo, however, I get the exact same issue as #6. |
|
That seems to be the case. I have a TX 3 mini yet the vfd.conf file from this library, as well as the one from this library don't seem to work. Service runs properly and identifies the FD6551 controller- just no output. |
After executing
So it seems that my LCD is connected through GPIO 178 and 180, with 147 being the stb pin? |
FD65xx series use I2C-type of protocol, only pins 178 and 180 are used. |
Again thank you for the quick follow up. Since it uses I2C and is different
from other controllers- what pin specifications should I use? Do I assume 23 is clock and 25 is data or vice versa?
|
Figured it out. I set my clock and data pins as follows (for the FD6551 controller):
and ran |
So does that work now? |
It displays stuff but irregularly. I’m playing around with the display type and vfd chars setting but no luck so far. Running a tx3 mini with a FD6551 controller. Setting the last display type variable to 0x06 successfully selects the controller, but the display still makes little sense and i’m unsure how to assign ‘vfd_chars’ |
Try different combinations of 0x0600000x. |
And also, the unused (stb) pin should be |
@arthur-liberman I will try it out tomorrow. Also, shouldn’t the last value be 06, as in |
No. The MSB represents the controller, the LSB represents the display type. |
My stb pin was indeed set to 0, 0, 0xFF as you stated. It seems like my display type is most likely 0x0600002 as it succeeded in displaying all the numbers and letters in test mode. I've properly configured Now I'm curious how I can make it display custom messages instead of just time. |
Take a look at this repo for more info: |
Entirely unsure what to do with that repo- it's a kodi addon and I'm on armbian. I'll go over the source code to see what I can do. |
It's python, and you basically write to a sysfs file. |
Seems like im missing a kodi library |
What I meant is that the code is in python, you can read it to understand what to do. |
Hello arthur, the similar issue with this topic on my tanix tx6 box which is allwinner H6 SOC based, I am running on android, the LED controller is FD650 and no indication on the LED. The dmesg copied below, I used the contents from vfd.conf and phased in sysconfig.fex (device tree for android) for android rom pack. The dmesg always show "OpenVFD: Select Dummy controller" and I cannot switch to controller FD650. Can you please have a look? Thank you. vfd.conf: vfd_gpio_clk='1,229,0' ;chars: vfd_chars='2,4,3,2,1' ;dot_bits: vfd_dot_bits='0,1,2,3,4,5,6' ;display_type: vfd_display_type='0x01,0x00,0x00,0x03' dmesg: |
Closing due to lack of activity. Please let me know if you still have an issue with the latest commits pushed recently. |
I have already viewed issue #3 and unfortunately did not find a solution there. Keep in mind I added some variables to the DTB as an attempt to go around using the config file, but to no avail. Here is my dmesg after modprobe openvfd:
DTB looks like this:
When starting openvfd the first time:
If I start openvfd again right after, it somehow manages to run. If I try running the demo, it freezes here:
dmesg:
Understandably, it's writing but nothing actually writes to the LCD. I've tried changing the config file location, changing its permissions, moving the config to the dtb, but not luck.
The text was updated successfully, but these errors were encountered: