CSC Armbian for RK3318/RK3328 TV box boards

[fabiobassa]

Hello all nice people, let me do this post since I repute it very important.
There is a lot of people actively deploying things on rk 322x and rk 3318, some  media oriented things ( libreelec, kodi ) some desktop and servers applications.
Now.......it happens that @jock and my self are actively working on those two platforms because I was so lucky in the past to buy for really few bucks ( and i say FEW )  more than 50 different boards reputed faulty, and there were not, just wrong firmware.
But in this big STOCK of boards mostly were 322x ( 3228 3228a 3229 ) and ONLY ONE was 3318,and again I repeat just ONE 3318
 

So it happens that quite EVERY  question on 322x we can answer with sufficient level of accurancy, but on 3318 our experience is limited on HK1,  that is a circle box without display.
Every single help, every single uart log, bootlog any elselog is a mine of infos for us, in particular @jock , but at the same time is really hard provide you a satisfactory answer without debug info, our crystal ball is actually broken

Help us to help you providing as much infos possible and not just saying " it doesn't boot" because in that way is a hard stuff to solve.

Thanks

 

[Dragao]

1 minute ago, fabiobassa said:

Hello all nice people, let me do this post since I repute it very important.
There is a lot of people actively deploying things on rk 322x and rk 3318, some of media oriented things ( libreelec, kodi ) some on desktop and servers applications.
Now.......it happens that @jock and my self are actively working of those two platforms because I was so lucky in the past to buy for really few bucks ( and i say FEW )  more than 50 different boards reputed faulty, and there were not, just wrong firmware.
But in this big STOCK of boards mostly were 322x ( 3228 32238a 3229 ) and ONLY ONE was 3318,and again I repeat just ONE 3318
 

So it happens that quite EVERY  question on 322x we can answer with sufficient level of accurancy, but on 3318 our experience is limited on HK1,  that is a circle box without display.
Every single help, every single uart log, bootlog any elselog is a mine of infos for us, in particular @jock , but at the same time is really hard provide you a satisfactory answer without debug info, our crystal ball is actually broken

Help us to help you providing as much infos possible and not just saying " it doesn't boot" because in that way is a hard stuff to solve.

Thanks

 

I do understand your post (and perhaps some frustration). 

 

I have only one excuse  I am NOOB  

I am more that happy to give you any log I can get.. The problem is my expertise on armbian (and putting it on tvboxes) is very fresh/new.. 

 

I would love to get some logging if I only new how.. 

Googling isn't really helping me (probably searching faulty)  

 

I am also having trouble running/compiling a new image for RK3318 using paolosabatino/armbian-build and I have no clue where to start looking  (but that's a different story i think) 

 

I would also get the dtb from the running Android. to help you out. 

 

if I can do anything to help I would be very happy to.

 

[fabiobassa]

@Dragao
hello ty for answer but this is not pointing finger on one person or on another person,  it isn't in my style point finger because me too have been noob , is merely an explication why things on 322x are very " mature" and on 3318 is still some head bumping in the wall

lack of hardware !!!!

We experimented on just ONE , but accordling to rockchip philosofy discover on one is half road to port on others of same family
And don't worry, I didn't knew NOTHING of compile until no more than 2 years ago, and you can understand frustration because I would have my personal success !!!!

I can only say that( JUST ONE EXAMPLE ) the uart pad of my 3318 were HIDDEN under heat sink of cpu and I discovered only because I never give up and because I own oscilloscope and other tools so i tested every single pad of the circuitry and finally discovered. As you can imagine, night and nights sleepless for......what ? Just discovering were the devilish uart signal was

But, in other way, if people not even knows how to attach a uart - ttl converter , or doesn't own one , at actual state is more a guessing than a " developing"

[Dragao]

@fabiobassa

 

If there is anything I can do.. ( I do own a H96max which should contain rk3318) 

just let me know

 

(and I know you are not pointing any fingers:P I was merely offering my help  ) 

 

[kruzer]

1 hour ago, fabiobassa said:

... every single uart log, bootlog any elselog is a mine of infos for us, in particular @jock , but at the same time is really hard provide you a satisfactory answer without debug info, our crystal ball is actually broken

 

I use h96max, it looks like this:

inside:

 

Here are logs from armbianmonitor -u

http://ix.io/3nfR

it is working pretty stable, it would be nice to do something useful with that front display.

 

[Dragao]

@kruzerDid you had a working (bootable) image?  I have the same device would like to test

If you have an image, care to share ?

[jock]

8 hours ago, kruzer said:

it is working pretty stable, it would be nice to do something useful with that front display.

Yeah, I'm moving on that front now, the driver is working but it is not really in a shape I really like for most things. Did you see the post where I gave instructions to @lucky62 on how to compile the driver to make it work at least for displaying time and turning on/off leds?

That requires a bit of manual handling because there are several led driver chips (I have FD6551, @lucky62 has TM1628, can't read yours from the photo) supported by the driver. They work mostly with the same protocol, but each chip has its own differences and each board wires the led driver chip on different gpios, so you need to take a look into the original dtb.

 

edit: just took a look into the logs you posted... very strange that from the photo your box apparently has an AP6334/BCM4334 clone but the chip declares itself as an AP6330/BCM4330 to the kernel. I may guess that the photo is of another board or chinese are also faking fake chips

[lucky62]

@jock, something is wrong with the driver.
dtbo is ok, compiled and loaded. But driver is not loaded automatically and modprobe is reporting the error:

 

# modprobe openvfd

Message from syslogd@rk3318-box at May 19 09:36:20 ...
 kernel:[ 3667.209338] Internal error: Oops: 96000004 [#1] PREEMPT SMP
Segmentation fault

Message from syslogd@rk3318-box at May 19 09:36:20 ...
 kernel:[ 3667.235479] Code: 32000000 39016420 f9401a60 f9404be1 (f9406022) 

 

EDIT: Adding complete kernel messages:

May 19 09:36:20 rk3318-box kernel: [ 3667.199649] openvfd: loading out-of-tree module taints kernel.
May 19 09:36:20 rk3318-box kernel: [ 3667.200658] openvfd: module verification failed: signature and/or required key missing - tainting kernel
May 19 09:36:20 rk3318-box kernel: [ 3667.204261] OpenVFD: Detected gpio chips:	gpio0, gpio1, gpio2, gpio3, ff100000.syscon:grf-gpio.
May 19 09:36:20 rk3318-box kernel: [ 3667.204298] openvfd openvfd: using device tree configuration parameters
May 19 09:36:20 rk3318-box kernel: [ 3667.204422] OpenVFD: gpio-clk: pin = 83, flags = 0x00
May 19 09:36:20 rk3318-box kernel: [ 3667.204477] OpenVFD: gpio-dat: pin = 86, flags = 0x00
May 19 09:36:20 rk3318-box kernel: [ 3667.204531] OpenVFD: gpio-stb: pin = 82, flags = 0x00
May 19 09:36:20 rk3318-box kernel: [ 3667.204547] OpenVFD: gpio0 pin entry not found
May 19 09:36:20 rk3318-box kernel: [ 3667.204561] OpenVFD: gpio1 pin entry not found
May 19 09:36:20 rk3318-box kernel: [ 3667.204574] OpenVFD: gpio2 pin entry not found
May 19 09:36:20 rk3318-box kernel: [ 3667.204587] OpenVFD: gpio3 pin entry not found
May 19 09:36:20 rk3318-box kernel: [ 3667.204650] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000c0
May 19 09:36:20 rk3318-box kernel: [ 3667.205445] Mem abort info:
May 19 09:36:20 rk3318-box kernel: [ 3667.205711]   ESR = 0x96000004
May 19 09:36:20 rk3318-box kernel: [ 3667.206006]   EC = 0x25: DABT (current EL), IL = 32 bits
May 19 09:36:20 rk3318-box kernel: [ 3667.206609]   SET = 0, FnV = 0
May 19 09:36:20 rk3318-box kernel: [ 3667.206911]   EA = 0, S1PTW = 0
May 19 09:36:20 rk3318-box kernel: [ 3667.207203] Data abort info:
May 19 09:36:20 rk3318-box kernel: [ 3667.207473]   ISV = 0, ISS = 0x00000004
May 19 09:36:20 rk3318-box kernel: [ 3667.207833]   CM = 0, WnR = 0
May 19 09:36:20 rk3318-box kernel: [ 3667.208120] user pgtable: 4k pages, 48-bit VAs, pgdp=000000002a8d4000
May 19 09:36:20 rk3318-box kernel: [ 3667.208701] [00000000000000c0] pgd=0000000000000000, p4d=0000000000000000
May 19 09:36:20 rk3318-box kernel: [ 3667.209338] Internal error: Oops: 96000004 [#1] PREEMPT SMP
May 19 09:36:20 rk3318-box kernel: [ 3667.209842] Modules linked in: openvfd(OE+) rfcomm bnep hantro_vpu(C) v4l2_h264 videobuf2_dma_contig brcmfmac v4l2_mem2mem sg brcmutil videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 hci_uart cfg80211 videobuf2_common snd_soc_spdif_tx btqca btrtl videodev btbcm gpio_ir_recv btintel mc snd_soc_hdmi_codec bluetooth snd_soc_rk3328 snd_soc_simple_card rfkill snd_soc_simple_card_utils snd_soc_rockchip_i2s snd_soc_rockchip_spdif snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore cpufreq_dt zram binfmt_misc ip_tables x_tables autofs4 dw_hdmi_i2s_audio dw_hdmi_cec dwmac_rk stmmac_platform stmmac rockchipdrm pcs_xpcs dw_mipi_dsi dw_hdmi analogix_dp lima gpu_sched drm_kms_helper cec rc_core gpio_syscon drm drm_panel_orientation_quirks adc_keys uas
May 19 09:36:20 rk3318-box kernel: [ 3667.216246] CPU: 1 PID: 2552 Comm: modprobe Tainted: G         C OE     5.10.37-rockchip64 #trunk
May 19 09:36:20 rk3318-box kernel: [ 3667.217038] Hardware name: Rockchip RK3318 BOX (DT)
May 19 09:36:20 rk3318-box kernel: [ 3667.217488] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
May 19 09:36:20 rk3318-box kernel: [ 3667.218095] pc : openvfd_driver_probe+0xc00/0xd0c [openvfd]
May 19 09:36:20 rk3318-box kernel: [ 3667.218662] lr : openvfd_driver_probe+0xbe0/0xd0c [openvfd]
May 19 09:36:20 rk3318-box kernel: [ 3667.219170] sp : ffff800014ca38a0
May 19 09:36:20 rk3318-box kernel: [ 3667.219475] x29: ffff800014ca38a0 x28: ffff800009484a60 
May 19 09:36:20 rk3318-box kernel: [ 3667.219974] x27: 0000000000000007 x26: fffffdfffe700180 
May 19 09:36:20 rk3318-box kernel: [ 3667.220471] x25: ffff0000006a0800 x24: ffff800011391318 
May 19 09:36:20 rk3318-box kernel: [ 3667.220968] x23: ffff00007fbbc8d0 x22: ffff800009481ea8 
May 19 09:36:20 rk3318-box kernel: [ 3667.221465] x21: ffff0000006a0810 x20: ffff800009484508 
May 19 09:36:20 rk3318-box kernel: [ 3667.221962] x19: ffff8000094881f0 x18: ffff8000118ded68 
May 19 09:36:20 rk3318-box kernel: [ 3667.222455] x17: 0000000000000010 x16: 0000000000000000 
May 19 09:36:20 rk3318-box kernel: [ 3667.222948] x15: 00000000000004f3 x14: ffff800014ca3560 
May 19 09:36:20 rk3318-box kernel: [ 3667.223442] x13: 00000000ffffffea x12: ffff80001194eda0 
May 19 09:36:20 rk3318-box kernel: [ 3667.223937] x11: 0000000000000007 x10: 0101010101010101 
May 19 09:36:20 rk3318-box kernel: [ 3667.224432] x9 : ffffffffffffffff x8 : 7f7f7f7f7f7f7f7f 
May 19 09:36:20 rk3318-box kernel: [ 3667.224925] x7 : fefefeff646c606d x6 : 0111080bf6e6e4ac 
May 19 09:36:20 rk3318-box kernel: [ 3667.225421] x5 : 2c6466760b081101 x4 : 8080808000000000 
May 19 09:36:20 rk3318-box kernel: [ 3667.225916] x3 : 0000000000000001 x2 : 0000000000000000 
May 19 09:36:20 rk3318-box kernel: [ 3667.226408] x1 : 0000000000000000 x0 : ffff00002aa75f00 
May 19 09:36:20 rk3318-box kernel: [ 3667.226904] Call trace:
May 19 09:36:20 rk3318-box kernel: [ 3667.227193]  openvfd_driver_probe+0xc00/0xd0c [openvfd]
May 19 09:36:20 rk3318-box kernel: [ 3667.227684]  platform_drv_probe+0x54/0xa8
May 19 09:36:20 rk3318-box kernel: [ 3667.228062]  really_probe+0xe8/0x4d0
May 19 09:36:20 rk3318-box kernel: [ 3667.228396]  driver_probe_device+0xf4/0x160
May 19 09:36:20 rk3318-box kernel: [ 3667.228785]  device_driver_attach+0x74/0x80
May 19 09:36:20 rk3318-box kernel: [ 3667.229175]  __driver_attach+0xa4/0x170
May 19 09:36:20 rk3318-box kernel: [ 3667.229531]  bus_for_each_dev+0x74/0xc8
May 19 09:36:20 rk3318-box kernel: [ 3667.229887]  driver_attach+0x24/0x30
May 19 09:36:20 rk3318-box kernel: [ 3667.230220]  bus_add_driver+0x1a0/0x238
May 19 09:36:20 rk3318-box kernel: [ 3667.230575]  driver_register+0x64/0x120
May 19 09:36:20 rk3318-box kernel: [ 3667.230933]  __platform_driver_register+0x48/0x58
May 19 09:36:20 rk3318-box kernel: [ 3667.231402]  openvfd_driver_init+0x3c/0x1000 [openvfd]
May 19 09:36:20 rk3318-box kernel: [ 3667.231875]  do_one_initcall+0x4c/0x2c0
May 19 09:36:20 rk3318-box kernel: [ 3667.232231]  do_init_module+0x58/0x220
May 19 09:36:20 rk3318-box kernel: [ 3667.232578]  load_module+0x2110/0x23e0
May 19 09:36:20 rk3318-box kernel: [ 3667.232926]  __do_sys_finit_module+0xc0/0x128
May 19 09:36:20 rk3318-box kernel: [ 3667.233329]  __arm64_sys_finit_module+0x20/0x30
May 19 09:36:20 rk3318-box kernel: [ 3667.233753]  el0_svc_common.constprop.2+0x8c/0x190
May 19 09:36:20 rk3318-box kernel: [ 3667.234192]  do_el0_svc+0x24/0x90
May 19 09:36:20 rk3318-box kernel: [ 3667.234509]  el0_svc+0x14/0x20
May 19 09:36:20 rk3318-box kernel: [ 3667.234799]  el0_sync_handler+0x90/0xb8
May 19 09:36:20 rk3318-box kernel: [ 3667.235153]  el0_sync+0x158/0x180
May 19 09:36:20 rk3318-box kernel: [ 3667.235479] Code: 32000000 39016420 f9401a60 f9404be1 (f9406022) 
May 19 09:36:20 rk3318-box kernel: [ 3667.236037] ---[ end trace 9ff4cdec9663d47d ]---

 

[jock]

@lucky62 don't know what's wrong with that, but consider that it is an heavy work in progress, much like an experiment, so anything can be wrong.

With the kernel headers in place you should be able to compile the original kernel module too, but the makefile may require some adjustment and surely the dtb properties are defined in another way.

 

If you don't have developer skills I would suggest to wait for something more proper; if you want to investigate further maybe go with original kernel module and ask the author for more details, because I had to guess some things that are not in the documentation digging in the source code myself.

 

[kruzer]

5 hours ago, Dragao said:

@kruzerDid you had a working (bootable) image?  I have the same device would like to test

If you have an image, care to share ?

Yes. I've tried two images from the first page of this thread (kernel 5), both were working ok. My logs are from Ubuntu Focal (kernel 5.10.32). Current links lead to kernel 5.10.34, images were updated, i suppose. I'll check in the evening

[kruzer]

3 hours ago, jock said:

Yeah, I'm moving on that front now, the driver is working but it is not really in a shape I really like for most things. Did you see the post where I gave instructions to @lucky62 on how to compile the driver to make it work at least for displaying time and turning on/off leds?

Yeah, I'll try to build it

 

 

 

3 hours ago, jock said:

edit: just took a look into the logs you posted... very strange that from the photo your box apparently has an AP6334/BCM4334 clone but the chip declares itself as an AP6330/BCM4330 to the kernel. I may guess that the photo is of another board or chinese are also faking fake chips

This is exactly my board inside, I will take better photos. 

 

[jock]

Just now, kruzer said:

This is exactly my board inside, I will take better photos. 

Don't worry, it was just a side consideration about the wifi chip. You may take a look to find the name of the led driver chip instead (that's the long one on the back of the board in the upper right corner, near the led panel)

[Dragao]

1 hour ago, kruzer said:

Yes. I've tried two images from the first page of this thread (kernel 5), both were working ok. My logs are from Ubuntu Focal (kernel 5.10.32). Current links lead to kernel 5.10.34, images were updated, i suppose. I'll check in the evening

hmm strange.... I have tried 2 files from the first post.. Both of them are not booting.. I must be doing something wrong.    I will have to find out how to connect serial to the box for debugging

 

[kruzer]

4 hours ago, Dragao said:

hmm strange.... I have tried 2 files from the first post.. Both of them are not booting.. I must be doing something wrong.    I will have to find out how to connect serial to the box for debugging

 

Ok, I've installed updated image from first post:

• Armbian 21.08 - Ubuntu Focal desktop [xfce] - mainline kernel 5.10.34 - Build date: 2021-05-05

Burned to emmc with multitool, and it works, connected to wifi without issues. Logs from this kernel: http://ix.io/3njG

After the first reboot it had a problem with starting X (restart loop). Solved it with connecting via ssh, and:

sudo apt update
sudo apt-get install lightdm
> ...
> Preparing to unpack .../lightdm_1.30.0-0ubuntu4~20.04.1_arm64.deb ...
> Unpacking lightdm (1.30.0-0ubuntu4~20.04.1) over (1.30.0-0ubuntu3.1) ...
> Setting up lightdm (1.30.0-0ubuntu4~20.04.1) ...
> ...

I noticed one problem with apt - it is very slow, not while downloading, but later, it takes minutes while "Reading package list ..., Building dependency tree .. " etc.

 

[kruzer]

5 hours ago, jock said:

Don't worry, it was just a side consideration about the wifi chip. You may take a look to find the name of the led driver chip instead (that's the long one on the back of the board in the upper right corner, near the led panel)

Yes, this board has FD6551 chip.

9 hours ago, jock said:

edit: just took a look into the logs you posted... very strange that from the photo your box apparently has an AP6334/BCM4334 clone but the chip declares itself as an AP6330/BCM4330 to the kernel. I may guess that the photo is of another board or chinese are also faking fake chips

I am not sure if you are reffering to this chip, but it looks like it is covered with a metal plate with inscription "HCY6334"

 

Edited May 19, 2021 by kruzer

[kruzer]

14 hours ago, jock said:

Yeah, I'm moving on that front now, the driver is working but it is not really in a shape I really like for most things. Did you see the post where I gave instructions to @lucky62 on how to compile the driver to make it work at least for displaying time and turning on/off leds?

I followed the instructions, I wasn't sure howto prepare the overlay, but I used armbian-add-overlay with the dts file you prepared for @lucky62. The result of modprobe is similar:

openvfd: loading out-of-tree module taints kernel.
openvfd: module verification failed: signature and/or required key missing - tainting kernel
OpenVFD: Detected gpio chips:	gpio0, gpio1, gpio2, gpio3, ff100000.syscon:grf-gpio.
openvfd openvfd: using device tree configuration parameters
OpenVFD: gpio-clk: pin = 83, flags = 0x00
OpenVFD: gpio-dat: pin = 86, flags = 0x00
OpenVFD: gpio-stb: pin = 82, flags = 0x00
OpenVFD: gpio0 pin entry not found
OpenVFD: gpio1 pin entry not found
OpenVFD: gpio2 pin entry not found
OpenVFD: gpio3 pin entry not found
Unable to handle kernel NULL pointer dereference at virtual address 00000000000000c0
Mem abort info:
  ESR = 0x96000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
Data abort info:
  ISV = 0, ISS = 0x00000004
  CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=000000003f330000
[00000000000000c0] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 96000004 [#1] PREEMPT SMP
Modules linked in: openvfd(OE+) rfcomm algif_hash algif_skcipher af_alg bnep snd_soc_hdmi_codec joydev apple_mfi_fastcharge hantro_vpu(C) brcmfmac v4l2_h264 videobuf2_dma_contig brcmutil v4l2_mem2mem videobuf2_vmalloc videobuf2_memops hci_uart videobuf2_v4l2 cfg80211 btqca videobuf2_common btrtl snd_soc_spdif_tx btbcm videodev btintel bluetooth mc gpio_ir_recv dw_hdmi_cec dw_hdmi_i2s_audio snd_soc_rk3328 snd_soc_simple_card rfkill snd_soc_simple_card_utils lima gpu_sched snd_soc_rockchip_spdif snd_soc_rockchip_i2s snd_soc_core snd_pcm_dmaengine snd_pcm cpufreq_dt snd_timer snd soundcore zram sch_fq_codel ip_tables x_tables autofs4 dwmac_rk stmmac_platform stmmac pcs_xpcs gpio_syscon rockchipdrm analogix_dp dw_hdmi dw_mipi_dsi drm_kms_helper cec rc_core drm drm_panel_orientation_quirks adc_keys hid_apple
CPU: 1 PID: 3209 Comm: modprobe Tainted: G         C OE     5.10.37-rockchip64 #trunk
Hardware name: Rockchip RK3318 BOX (DT)
pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
pc : openvfd_driver_probe+0xae0/0xd00 [openvfd]
lr : openvfd_driver_probe+0xac0/0xd00 [openvfd]
sp : ffff8000151638a0
x29: ffff8000151638a0 x28: ffff80000944d8f8 
x27: ffff800009446e60 x26: ffff800009449a60 
x25: 0000000000000007 x24: fffffdfffe700180 
x23: ffff0000007f0800 x22: ffff800009446e28 
x21: ffff0000007f0810 x20: ffff800009449508 
x19: ffff80000944d1f0 x18: ffff8000118ded68 
x17: 0000000000000000 x16: 0000000000000000 
x15: 00000000000002b2 x14: ffff800015163560 
x13: 00000000ffffffea x12: ffff80001194eda0 
x11: 0000000000000007 x10: 0101010101010101 
x9 : fffffffffffffffc x8 : 7f7f7f7f7f7f7f7f 
x7 : fefefeff646c606d x6 : 0111080bf6e6e4ac 
x5 : 2c6466760b081101 x4 : 8080808000000000 
x3 : 0000000000000001 x2 : 0000000000000000 
x1 : 0000000000000000 x0 : ffff00000448a300 
Call trace:
 openvfd_driver_probe+0xae0/0xd00 [openvfd]
 platform_drv_probe+0x54/0xa8
 really_probe+0xe8/0x4d0
 driver_probe_device+0xf4/0x160
 device_driver_attach+0x74/0x80
 __driver_attach+0xa4/0x170
 bus_for_each_dev+0x74/0xc8
 driver_attach+0x24/0x30
 bus_add_driver+0x1a0/0x238
 driver_register+0x64/0x120
 __platform_driver_register+0x48/0x58
 openvfd_driver_init+0x3c/0x1000 [openvfd]
 do_one_initcall+0x4c/0x2c0
 do_init_module+0x58/0x220
 load_module+0x2110/0x23e0
 __do_sys_finit_module+0xc0/0x128
 __arm64_sys_finit_module+0x20/0x30
 el0_svc_common.constprop.2+0x8c/0x190
 do_el0_svc+0x24/0x90
 el0_svc+0x14/0x20
 el0_sync_handler+0x90/0xb8
 el0_sync+0x158/0x180
Code: 32000000 39016420 f9401a60 f9404be1 (f9406022) 
---[ end trace dec8129f81b80a72 ]---

 

[lucky62]

good news, today I succesfuly compiled the openvfd driver.

This is my DT Overlay:

/dts-v1/;
/plugin/;
/ {
   fragment@0 {
      target-path = "/";
      __overlay__ {
         openvfd {
            compatible = "open,vfd";
            dev_name = "openvfd";
            openvfd_gpio_clk = <&gpio2 0x13 0x00>;
            openvfd_gpio_dat = <&gpio2 0x16 0x00>;
            openvfd_gpio_stb = <&gpio2 0x12 0x00>;
            openvfd_chars = [04 00 01 02 03];
            openvfd_dot_bits = [00 01 02 03 04 05 06];
            openvfd_display_type = <0x03>;
            status = "okay";
         };
      };
   };
};

Driver is working without any changes.

 

[Dragao]

ok, I have something else now..  

 

As my box was running android 10 (non root) I downgraded the box to Android 9 (have to check if it is rooted now) 

The problem now is, I cannot boot from SD anymore  That is, my multitool sd does not boot.

 

Are there any ways to force an SD boot ?

 

edit: ok, it seemed the SD card was not inserted correctly... I got it working

 

Edited May 20, 2021 by Dragao

[Dragao]

Question: Does anyone know what it means when red/blue led is flashing (alternating) ?

[kruzer]

18 hours ago, lucky62 said:

good news, today I succesfuly compiled the openvfd driver.

Congratulations  , but unfortunatelly this dto doesn't work for me

[lucky62]

23 minutes ago, kruzer said:

Congratulations  , but unfortunatelly this dto doesn't work for me

Different board needs different DTO...

[jock]

On 5/19/2021 at 6:34 PM, kruzer said:

I am not sure if you are reffering to this chip, but it looks like it is covered with a metal plate with inscription "HCY6334"

Yes, I was talking about that one. From the plate you may guess it is an AP6334 clone, but instead the kernel detects it as an AP6330. No big deal though, AP6334 is just a bit better than AP6330.

 

3 hours ago, kruzer said:

Congratulations  , but unfortunatelly this dto doesn't work for me

True, it can't because you got an fd6551 chip (like my box) and the gpio pins are different too. I don't have the board near me now, I will try to post a suitable dts tomorrow!

[kruzer]

1 hour ago, jock said:

True, it can't because you got an fd6551 chip (like my box) and the gpio pins are different too. I don't have the board near me now, I will try to post a suitable dts tomorrow!

That would be great :-)

Anyway, I hope I've correctly extracted dts from android backup made with multitool from my box. I am attaching it with the dmesg output from running android firmware.

h96max.dts

android_dmesg.txt

[jock]

18 minutes ago, kruzer said:

That would be great :-)

Anyway, I hope I've correctly extracted dts from android backup made with multitool from my box. I am attaching it with the dmesg output from running android firmware.

h96max.dts 83.48 kB · 0 downloads android_dmesg.txt 151.58 kB · 0 downloads

 

Great, so I think that this dts should work for you with the original driver:

/dts-v1/;
/plugin/;
/ {
   fragment@0 {
      target-path = "/";
      __overlay__ {
         openvfd {
            compatible = "open,vfd";
            dev_name = "openvfd";
            openvfd_gpio_clk = <&gpio2 0x16 0x00>;
            openvfd_gpio_dat = <&gpio2 0x15 0x00>;
            openvfd_gpio_stb = <&gpio2 0x14 0x00>;
            openvfd_chars = [00 04 03 02 01];
            openvfd_dot_bits = [00 01 03 02 04 05 06];
            openvfd_display_type = [06 00 00 00];
            status = "okay";
         };
      };
   };
};

 

It's just a base to start from, probably you need to change the chars and dot_bits order, but display_type and gpios should be right. Be sure that the log message on dmesg tells you the driver is using fd6551 controller (the enum is defined here)

 

edit: quite interestingly, your original firmware is based upon kernel 4.19, cool! Did the original vendor provide an original pristine firmware? It could be interesting for some updated firmware binaries.

[kruzer]

On 5/20/2021 at 10:46 PM, jock said:

Great, so I think that this dts should work for you with the original driver:

 @jock thank you very much, it is working  👍 

[Dragao]

As I am fairly new to this.. 

I am kinda lost in what to do next... 

 

I want to create my own armbian image (running ubuntu focal) but I am currently unable to find the thing I need to do. 

 

I have extracted the dtb file from the android. Should I also get the u-boot and/or trust img ? 

 

maybe someone can point me in the direction of a manual ? 

 

Regards

[kruzer]

2 minutes ago, Dragao said:

I am kinda lost in what to do next... 

 

The first post in this thread is good point to start. 

1. Burn the image with ubuntu focal to sd card and boot it. Follow the "Quick installation instructions to boot from SD Card"

2. If it is running ok, burn the same image to emmc. "Quick installation instructions on eMMC"

[Dragao]

Just now, kruzer said:

The first post in this thread is good point to start. 

1. Burn the image with ubuntu focal to sd card and boot it. Follow the "Quick installation instructions to boot from SD Card"

2. If it is running ok, burn the same image to emmc. "Quick installation instructions on eMMC"

well there lies my problem,

none of these image boot on my device.. 

So I guess I have t o create my own... I need info on how to do that.. 

[kruzer]

1 minute ago, Dragao said:

none of these image boot on my device.. 

If that is the case, you should connect a serial console to the board and log messages (errors) from booting process (they are available before hdmi output is established). It may help to detect the reason of booting problem.

[Dragao]

Just now, kruzer said:

If that is the case, you should connect a serial console to the board and log messages (errors) from booting process (they are available before hdmi output is established). It may help to detect the reason of booting problem.

ok, then I will go on a search on how to connect a serial reader to the box.

thanks