Jump to content

CSC Armbian for RK3318/RK3328 TV box boards

jock

By jock
in Rockchip CPU Boxes

 Share

Recommended Posts

fabiobassa

fabiobassa

Posted
Posted

@Wester_Minsk
 

  Quote

....or share a link to a simple instruction

Expand  


I suppose you want to build a uboot for supporting booting from usb3 .
This isn't a simple task and if it was simple,  somebody else already could had done for all of us. It is needed deep knowledge of processes undergoing the compilation and the modding of c sources. It isn't just a flag " boot from usb3..." but a chain on changes to do to the code, if someone already has written a code for it

By the way here is the link
https://github.com/rockchip-linux/u-boot

but then don't ask for assistance in what when and where apply patch since if this infos were clear and well known uboot already had have usb3 support.

But you really welcome to study and share your results

1
Wester_Minsk

Wester_Minsk

Posted
Posted
  On 1/15/2022 at 10:27 AM, fabiobassa said:

@Wester_Minsk
 


I suppose you want to build a uboot for supporting booting from usb3 .
This isn't a simple task and if it was simple,  somebody else already could had done for all of us. It is needed deep knowledge of processes undergoing the compilation and the modding of c sources. It isn't just a flag " boot from usb3..." but a chain on changes to do to the code, if someone already has written a code for it

By the way here is the link
https://github.com/rockchip-linux/u-boot

but then don't ask for assistance in what when and where apply patch since if this infos were clear and well known uboot already had have usb3 support.

But you really welcome to study and share your results

Expand  

Thanks for the link!
A very interesting topic for me.
Jokingly speaking - "@ I have "Windows" of the brain."
I've been goofing around in xp,7,10 for 25 years. Linux is difficult for me so far, but I'm trying and moving a little.

I've done some experiments. 1 was successful.
I erased the eMMC, burned the image to SD and deleted the USR and VAR folders from it and inserted it into the board. Then I recorded the same image on an SSD and connected it to USB 3. The system started and works very well and quickly until the first reboot, then u-boot no longer sees the kernel on the SSD:

  Reveal hidden contents

After overwriting the SD and SSD images, the system starts again.

Can such a method be workable?

Maybe you can build an image with a u-boot without a kernel?
I'll continue the tests.
If this is a lot of work for you, then I'll try again.

0
Wester_Minsk

Wester_Minsk

Posted
Posted

a few tests on cpu 1000

https://storage.jamesachambers.com/

     Category                  Test                      Result
HDParm                    Disk Read                 290.29 MB/s
HDParm                    Cached Disk Read          256.37 MB/s
DD                        Disk Write                90.2 MB/s
FIO                       4k random read            12256 IOPS (49024 KB/s)
FIO                       4k random write           5804 IOPS (23219 KB/s)
IOZone                    4k read                   26091 KB/s
IOZone                    4k write                  16847 KB/s
IOZone                    4k random read            16587 KB/s
IOZone                    4k random write           24202 KB/s

                          Score: 5507

my raspberry have 7,590

if up cpu is on the board, the result will be about with pi4

0
Zippy

Zippy

Posted
Posted
  On 1/15/2022 at 9:40 AM, jock said:

First post: there is a list of things useful for support and debug.

Expand  

Thanks for the direction .
since i am allow of one post / day let hope i have all the info.

Photo : https://imgur.com/a/nSiPiN2
DTB  i cant attache file yet ... but it is the rk3318-box.dtb from the Armbian 21.11 - Debian Bullseye desktop [xfce] - mainline kernel 5.15.2 - Download
armbianmonitor -u : http://ix.io/3Mgd

 

i can ssh to the box via wired 
i am running from sd for now, i did not move to emmc for now.

 

hope that will help

Thanks

0
curse

curse

Posted
Posted
  On 1/15/2022 at 8:09 PM, Wester_Minsk said:


I erased the eMMC, burned the image to SD and deleted the USR and VAR folders from it and inserted it into the board. Then I recorded the same image on an SSD and connected it to USB 3. The system started and works very well and quickly until the first reboot, then u-boot no longer sees the kernel on the SSD:

 

After overwriting the SD and SSD images, the system starts again.

 

 

Expand  

Correct me if I'm wrong. But you want to run the system from a USB3 SSD?

If so, I think the easiest would be to just have the boot on eMMC or SD-card, and the rest of the system on the SSD, then "almost" everything would be running from the fast SSD.

0
Wester_Minsk

Wester_Minsk

Posted
Posted
  On 1/16/2022 at 1:11 AM, curse said:

Correct me if I'm wrong. But you want to run the system from a USB3 SSD?

If so, I think the easiest would be to just have the boot on eMMC or SD-card, and the rest of the system on the SSD, then "almost" everything would be running from the fast SSD.

Expand  

You understood correctly.  I see it like this: U-boot (no kernel) with sd/emmc , kernel on SSD.

0
jock

jock

Posted
  • Author
Posted
  On 1/16/2022 at 6:35 AM, Wester_Minsk said:

You understood correctly.  I see it like this: U-boot (no kernel) with sd/emmc , kernel on SSD.

Expand  

Well not just the kernel, but the whole rootfs must sit on SSD.

Plus if you cloned you sdcard on SSD, both sdcard rootfs and SSD rootfs have the same UUID, and this may confuse the kernel about which rootfs use at boot.

This is pretty normal if you think about it: how does the kernel can know if you want to boot from sdcard or boot from SSD when both contain the same bootable system?

The rootfs UUID is specified in /boot/armbianEnv.txt.

 

There are several approaches:

  • You clone the sdcard on SSD, then you remove the rootfs partition from the sdcard
  • Install just the bootloader on the eMMC erasing the eMMC and then copying the first 4 megabytes of the sdcard (/dev/mmblk0) on the eMMC (/dev/mmcblk2)
  • Change the UUID of the sdcard rootfs, but this will prevent the sdcard rootfs from full boot

The most clean approach is #2, taking in account that you should not plug both sdcard and SSD at the same time when the same cloned filesystem is on them for the usual UUID reason of above.

2
Wester_Minsk

Wester_Minsk

Posted
Posted
  On 1/16/2022 at 9:47 AM, jock said:

Well not just the kernel, but the whole rootfs must sit on SSD.

Plus if you cloned you sdcard on SSD, both sdcard rootfs and SSD rootfs have the same UUID, and this may confuse the kernel about which rootfs use at boot.

This is pretty normal if you think about it: how does the kernel can know if you want to boot from sdcard or boot from SSD when both contain the same bootable system?

The rootfs UUID is specified in /boot/armbianEnv.txt.

 

There are several approaches:

  • You clone the sdcard on SSD, then you remove the rootfs partition from the sdcard
  • Install just the bootloader on the eMMC erasing the eMMC and then copying the first 4 megabytes of the sdcard (/dev/mmblk0) on the eMMC (/dev/mmcblk2)
  • Change the UUID of the sdcard rootfs, but this will prevent the sdcard rootfs from full boot

The most clean approach is #2, taking in account that you should not plug both sdcard and SSD at the same time when the same cloned filesystem is on them for the usual UUID reason of above.

Expand  

Thank you.

I will work with it.

0
Wester_Minsk

Wester_Minsk

Posted
Posted

There was a simple way, and it was in front of my nose.


This is the standard way from the official instructions of the Armbian:

 

Start the install script:

nand-sata-install

I chose:
of booting from eMMC/NAND, system to SATA/USB

 

The system migrates to a USB3 SSD
Restart and boot the system from USB3

 

now a stable start with USB3

1
Wester_Minsk

Wester_Minsk

Posted
Posted

I have done a lot of hardware tests to start with USB 3 on my RK3318 board
result:
I have 3 usb 3.0 to sata controllers, only one worked on my board via usb 3, on the core 5.12.2. But at the same time, after migrating from eMMC to SSD, this controller loaded the system poorly, I had to switch to hot so that u-boot could see the system partition. I connected another controller, u-boot reads it perfectly and the system starts stably.

At the moment, I have a confident start with usb3 ports, and continue testing.

0
glenb

glenb

Posted
Posted (edited)

I have Armbian_21.11.0-trunk_Rk3318-box_hirsute_edge_5.14.14_xfce_desktop running on a Z28 (original). This has the RK3328 SoC with an RTL8188 WifI chip. Quite acceptable.

 

I replaced xfce with mate following:

and a lot of tweaking.

 

I also am running the xRDP server following https://www.hiroom2.com/ubuntu-2004-xrdp-mate-en and https://github.com/neutrinolabs/pulseaudio-module-xrdp/wiki/README , with a bit of tweaking.

 

I can give more details if anyone expresses interest.

.

There are two issues that I would like some help with if anyone has any info to share:

 

1. RTL8188 WiFi chip is not recognized

 

2. My (admittedly cheap) HDMI TV is recognized as 1080P 30Hz. However other devices I connect to it do use 1080P 60Hz. These refresh rates are as reported by the TV in an info panel that reports the HDMI connectivity status.

Edited by glenb
specify WiFi chip in point 1.
0
jock

jock

Posted
  • Author
Posted
  On 1/17/2022 at 1:02 PM, Wester_Minsk said:

There was a simple way, and it was in front of my nose.


This is the standard way from the official instructions of the Armbian:

 

Start the install script:
nand-data-installation

I chose:
of booting from eMMC/NAND, system to SATA/USB

 

The system migrates to a USB3 SSD
Restart and boot the system from USB3

 

now a stable start with USB3

Expand  

Much better, I totally forgot about nand-sata-install script, mostly because I never tested it on rk3318 boards :)

0
Wester_Minsk

Wester_Minsk

Posted
Posted
  On 1/18/2022 at 7:17 AM, jock said:

Much better, I totally forgot about nand-sata-install script, mostly because I never tested it on rk3318 boards :)

Expand  

 

I have done the migration to SSD several times. It works well.
I also noticed that armbian-config started to work incorrectly. As I understand it, the path to the folder with scripts has changed, it does not work to change the language or region. I think this is a solvable problem.

Otherwise, everything is OK! :) 🍺

 

0
paradigman

paradigman

Posted
Posted

I'm trying to use the 7-segment display on my H96 Max box.
The display is controlled by an FD6551 driver IC.
I'm using Armbian 21.11 - Debian Bullseye minimal-mainline kernel 5.15.2. It was very difficult, but I managed to compile a driver for it, which resulted in an openvfd.ko kernel module. I put this in the /lib/modules/5.15.2-rockchip64 directory. I tried different config files and placed them in the /etc/modprobe.d directory called vfd.conf. When I try to load the module (modprobe openvfd), this error always occurs:

libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 10: ignoring bad line starting with 'vfd_gpio_clk='0,65,0''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 11: ignoring bad line starting with 'vfd_gpio_dat='0,64,0''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 12: ignoring bad line starting with 'vfd_gpio_stb='0,0,0xFF''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 17: ignoring bad line starting with 'vfd_chars='0,4,3,2,1''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 28: ignoring bad line starting with 'vfd_dot_bits='0,1,3,2,4,5,6''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 36: ignoring bad line starting with 'vfd_display_type='0x00,0x00,0x00,0x00'

Unfortunately, I'm stuck here, I can't find more information on how to install openvfd properly.

0
lucky62

lucky62

Posted
Posted
  On 1/19/2022 at 8:14 PM, paradigman said:

I'm trying to use the 7-segment display on my H96 Max box.
The display is controlled by an FD6551 driver IC.
I'm using Armbian 21.11 - Debian Bullseye minimal-mainline kernel 5.15.2. It was very difficult, but I managed to compile a driver for it, which resulted in an openvfd.ko kernel module. I put this in the /lib/modules/5.15.2-rockchip64 directory. I tried different config files and placed them in the /etc/modprobe.d directory called vfd.conf. When I try to load the module (modprobe openvfd), this error always occurs:

libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 10: ignoring bad line starting with 'vfd_gpio_clk='0,65,0''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 11: ignoring bad line starting with 'vfd_gpio_dat='0,64,0''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 12: ignoring bad line starting with 'vfd_gpio_stb='0,0,0xFF''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 17: ignoring bad line starting with 'vfd_chars='0,4,3,2,1''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 28: ignoring bad line starting with 'vfd_dot_bits='0,1,3,2,4,5,6''
libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/vfd.conf line 36: ignoring bad line starting with 'vfd_display_type='0x00,0x00,0x00,0x00'

Unfortunately, I'm stuck here, I can't find more information on how to install openvfd properly.

Expand  

BAD LINE means that your syntax is wrong...
Also try to check in hex form if there are some "hidden" chars (usually when you did copy/paste from web pages). Sometimes also the type of EOL (End of Line) chars can be a problem.
 

0
jock

jock

Posted
  • Author
Posted

Minor upgrade!

 

Not so many fancy things, this time, but those interested in rtl8723cs, rtl8703bs and ssv6051 wifi chips may give a look into!

 

I upgraded the Debian Bullseye Minimal image (not the others) to kernel 5.15.16 kernel.

Also deb packages have been updated for manual upgrade to avoid system reinstall (instruction on first page, as usual).

 

@Zippy may be particularly interested in this.

 

Enjoy and give feedback! ;)

1
paradigman

paradigman

Posted
Posted
  On 1/20/2022 at 7:25 AM, lucky62 said:

BAD LINE means that your syntax is wrong...
Also try to check in hex form if there are some "hidden" chars (usually when you did copy/paste from web pages). Sometimes also the type of EOL (End of Line) chars can be a problem.
 

Expand  

i opened the config file with notepad ++ but i don't see any unusual hidden characters. The file is utf-8 encoded anyway.

 

  Reveal hidden contents

 

0
Zippy

Zippy

Posted
Posted
  On 1/20/2022 at 8:33 PM, jock said:

@Zippy may be particularly interested in this.

 

Enjoy and give feedback! ;)

Expand  

Hey @jock thanks for this upgrade....
it is chrismas in January :)

the upgrade works nicely and the wireless show up after reboot:
  

3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:e0:4c:05:67:86 brd ff:ff:ff:ff:ff:ff

 

i have this in the log but i think it is related to bluetooth :
  

Jan 20 16:32:58 olivia dbus-daemon[1651]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.2' (uid=0 pid=592 comm="/bin/brltty --no-daemon ")
Jan 20 16:32:58 olivia systemd[1]: Condition check resulted in Bluetooth service being skipped.


Now i can check on the vfd , but this is really secondary
I will move to the EMMC with
  

nand-sata-install

 

Do you need any data, or me to test anything. my Box is a pretty standard box T9 people was throwing away :) i hate waste
Thanks again for this great work.
Z.

0
jock

jock

Posted
  • Author
Posted

@Zippy Glad to hear it works!

For bluetooth there is the need for some more bits in the kernel config and a device tree overlay.

Everything is already working for rk322x board series so I need to find some time to transpose the things on rk3318, hoping it works the very same way.

 

You may find some instructions here and there to get bluetooth up and running using only userland applications for realtek. I'm not experienced with realtek, but I can say that for broadcom it required quite a bit of time to get things squared out.

 

0
Zippy

Zippy

Posted
Posted
  On 1/20/2022 at 9:51 PM, jock said:

@Zippy Glad to hear it works!

For bluetooth there is the need for some more bits in the kernel config and a device tree overlay.

Everything is already working for rk322x board series so I need to find some time to transpose the things on rk3318, hoping it works the very same way.

 

You may find some instructions here and there to get bluetooth up and running using only userland applications for realtek. I'm not experienced with realtek, but I can say that for broadcom it required quite a bit of time to get things squared out.

 

Expand  

Yeah Thanks 
i am reading a lot , not yet comfortable with the tree overlay, but i guess it will come.
the wireless was the more annoying...

I think i will work on the vfd for now seems more reachable for me , as i am new to that... (i mean this kind of chip) not new to linux tho ;) , even if it is quite a while since i play with kernel :) i will probably reveal my age if i tell you the first kernel i built was 0.98 on a slak :)
Thanks again

0
paradigman

paradigman

Posted
Posted (edited)
  On 1/20/2022 at 9:59 PM, Zippy said:

I think i will work on the vfd for now ..

Expand  

I'm really pushing, it would be nice to finally have some advice that works in practice.

 

Edit:
meanwhile I realized that I shouldn't use a config file, since my dts contains the same data that I included in the config file.

Edited by paradigman
add plus information
0
MarcoFdN

MarcoFdN

Posted
Posted

@jock

Your latest Debian Bullseye Minimal image doesn't include armbian-config.

 

Which is great! It is tiny and super fast to flash on the box!

But at the same time, it breaks the installation instructions and makes it more difficult for noobs like me who relies on WiFi connection.

 

Simple instructions to install armbian-config: 

sudo iwconfig
sudo iwlist [interface from previous command] scan | greo ESSID
nmcli d wifi connect [your network name from previous command] password [your wifi password]
sudo apt update
sudo apt install armbian-config

 

Somehow this failed with 404 for versioning issues, so I installed it manually: 

wget https://imola.armbian.com/apt/pool/main/a/armbian-config/armbian-config_21.11.0-trunk.85_all.deb
sudo apt install ./armbian-config_21.11.0-trunk.85_all.deb

 

Maybe this will be useful for someone (maybe the instructions for minimal images can indicate how to connect over WiFi manually / install armbian-config?)

 

I still have no luck with bluetooth on this latest release. Any help would be appreciated!

rk3318-config says "No Wifi chip detected" (maybe a clue?) but Wifi works anyway

I enabled rk3318-box-wlan-ap6330 through armbian-config

"sudo hciconfig -a" indicate that the interface "hci0" is down

"sudo hciconfig hci0 up" returns "Operation not supported (95)"

In dmesg, I see "Direct Firmware load for brcm/brcmfmac4330-sdio.rockchip,rk3318-box.bin failed with error -2". I previously was able to correct this (maybe?) by creating a symlink but that didn't fix the BT issue so not sure if I should mess up with that again.

 

My box: x88Pro-B-RK3318-D4-V1.2 4G/32G, (the same as @Huafu and @lucky62)

Wifi/BT chip: Sp6330

 

Any pointers in which direction I should dig to get Bluetooth working? I don't think my box is that uncommon...

Except the command written above, I am on a brand new Armbian_22.02.0-trunk_Rk3318-box_bullseye_edge_5.15.16_minimal installation

 

Thanks!

 

0
paradigman

paradigman

Posted
Posted

@jock:

Today I compiled a new kernel module for openvfd again. The compilation went smoothly, but when I later tried to load it with insmod during a new installation, this error occurred:
version magic '3.14.29 SMP mod_unload aarch64' should be '5.15.16-rockchip64 SMP preempt mod_unload aarch64'
Maybe the kernel for the new image was created without CONFIG_LOCALVERSION?

Edit: 
back to the whole thing, the former error was due to an accidentally trying to load a compiled kernel module last time. It does not load the current freshly baked module, It now writes:

Message from syslogd@rk3318-box at Jan 21 21:48:32 ...
 kernel:[  591.624102] Internal error: Oops: 96000004 [#1] PREEMPT SMP

Message from syslogd@rk3318-box at Jan 21 21:48:32 ...
 kernel:[  591.968480] Code: 32000000 39016420 f9401a60 f9404be1 (f9406022)
Segmentation error

0
fabiobassa

fabiobassa

Posted
Posted

@paradigman

you need sources for your kernel that is 5.15.16-rockchip64
you compiled from sources that are 3.14.29 SMP

in few words wrong sources so the module will never fit and it isn't a problem of CONFIG_LOCALVERSION
Is a problem you are usign wrong one

0
jock

jock

Posted
  • Author
Posted

@MarcoFdN

Yes, armbian-config is not included in any Armbian minimal releases (not just mine), because if it was it would not be minimal  anymore: armbian-config requires lots of dependencies and, for this reason, it is undergoing a vast refactoring which I don't know when it will be ready.

 

In the meantime, no armbian-config for minimal images.

Plus minimal images are for more experienced debian users, since target is server-like tasks.

 

dmesg log is essential for such issues: x88 boards have wifi over "external" sdmmc controller, thus rk3318-config should already have warned you that you had to configure, reboot and then run again rk3318-config to get wifi and bluetooth detected and working.

 

wifi can be configured either from command line with nmcli, but also with nmtui which provide a nice and simpler text-based UI even on minimal distros.

1
Wester_Minsk

Wester_Minsk

Posted
Posted

I switched to - Armbian 22.02 - Debian Bullseye minimal - mainline kernel 5.15.16


Everything is ok on my board.


I migrated the system to a usb3 ssd drive, and connected a usb3 hub with a 1 Gbit LAN.


On the new version of the image, the armbian-config works fine after migration.

 

Thank you so much for the new release!!!

1
MarcoFdN

MarcoFdN

Posted
Posted

@jock

Thanks!

 

rk3318-config is never detecting my WiFi card, it always ask to reconfigure and reboot again.

 

I found the issue with rk3318-config!

My wifi device dev path is /sys/bus/sdio/devices/mmc4:0001:1 instead of mmc1 or mmc3.

After modifying the rk3318-config script, it now detects my WiFi card and configure Bluetooth!

(maybe another lookup path should be added in rk3318-config?)

 

However, same issue as before, I cannot power up Bluetooth:

sudo hciconfig hci0 up

Returns "Can't init device hci0: Operation not supported (95)"

 

Any other directions I can explore?

 

Relevant logs in dmesg:

[    9.315966] Bluetooth: hci0: BCM: chip id 62
[    9.316820] Bluetooth: hci0: BCM: features 0x0f
[    9.318676] Bluetooth: hci0: BCM4330B1
[    9.318722] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    9.321515] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch
[    9.487098] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard. Quota mode: none.
[    9.487270] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)
[    9.543657] brcmfmac: F1 signature read @0x18000000=0x16044330
[    9.566771] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.567115] brcmfmac mmc4:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.rockchip,rk3318-box.bin failed with error -2
[    9.569469] usbcore: registered new interface driver brcmfmac
[    9.865889] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.866233] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[    9.867427] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104

 

In a previous install, I created a symlink to bypass the "failed with error -2" but that didn't help with Bluetooth.

 

Additional information:

Hardware:

Android TV Box 10.0 4GB 32GB by "C Cosycost" available on Amazon for $40

 

Full dmseg in case I missing something:

  Reveal hidden contents

 

armbianEnv.txt

  Reveal hidden contents

 

Decompiled dtd from the original Android OS (the file was called rockchip,rk3328-box-liantong.dtb):

  Reveal hidden contents

 

0
lucky62

lucky62

Posted
Posted

Hello again..
I have the working LCD display - openvfd driver and service compiled and installed.
When service is running then it is showing the current time.

I can switch on/off particular other LEDs (Wifi-Hi, Power, LAN) by commands e.g.:
  

echo eth > /sys/class/leds/openvfd/led_on
echo eth > /sys/class/leds/openvfd/led_off

 

I would like to LEDs showing the actual status - mainly LAN and WiFi (power is not very important).
I was reading some docs about the LED triggers but I don't know how to get it working.
This is some info from running system: 

# ls -l /sys/class/leds/
total 0
lrwxrwxrwx 1 root root 0 Jan 24 20:14 openvfd -> ../../devices/platform/openvfd/leds/openvfd
lrwxrwxrwx 1 root root 0 Jan  1  1970 working -> ../../devices/platform/gpio-leds/leds/working

# ls -l /sys/class/leds/openvfd/
total 0
-rw-r--r-- 1 root root 4096 Jan 24 20:19 brightness
lrwxrwxrwx 1 root root    0 Jan 24 20:19 device -> ../../../openvfd
-rw-rw---- 1 root root 4096 Jan 24 20:19 led_cmd
-rw-rw---- 1 root root 4096 Jan 24 20:16 led_off
-rw-rw---- 1 root root 4096 Jan 24 20:16 led_on
-r--r--r-- 1 root root 4096 Jan 24 20:19 max_brightness
drwxr-xr-x 2 root root    0 Jan 24 20:19 power
lrwxrwxrwx 1 root root    0 Jan 24 20:19 subsystem -> ../../../../../class/leds
-rw-r--r-- 1 root root    0 Jan 24 20:19 trigger
-rw-r--r-- 1 root root 4096 Jan 24 19:59 uevent

# cat /sys/class/leds/openvfd/trigger
[none] usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport mmc0 mmc2 disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic mmc4 rfkill-any rfkill-none bluetooth-power hci0-power rfkill0 rc-feedback rfkill1 stmmac-1:00:link stmmac-1:00:100Mbps stmmac-1:00:10Mbps


Has anyone something working?
Can someone to help me?

Thanks in advance.


 

0
paradigman

paradigman

Posted
Posted
  On 1/24/2022 at 7:27 PM, lucky62 said:

Hello again..
I have the working LCD display - openvfd driver and service compiled and installed.
When service is running then it is showing the current time.

  ...

Expand  

Hello, could you share a few details on how you were able to display the clock? If I could get here, maybe I could help you with your problem.

This is because after compiling the driver, when I load the .ko module, it shows me:


Message from syslogd @ rk3318-box at Jan 21 21:48:32 ...   kernel: [591.624102] Internal error: Oops: 96000004 [# 1] PREEMPT SMP

Message from syslogd @ rk3318-box at Jan 21 21:48:32 ...   kernel: [591.968480] Code: 32000000 39016420 f9401a60 f9404be1 (f9406022)
Segmentation error

 

I saw that you had this error before, but then you didn't write what fixed it.

 

0

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept