PiotrO
Members-
Posts
48 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Having this bard will be really helpful for me to add support for this board in my 2 distros: https://github.com/warpme/minimyth2 (MythTV multimedia appliance; 13 diff SoC supported; 21 arm SBC boars supported) https://github.com/warpme/miniarch (Enabler of ArchLinux ARM on 21 different arm SBC boars)
-
Having this bard will be really helpful for me to add support for this board in my 2 distros: https://github.com/warpme/minimyth2 (MythTV multimedia appliance; 13 diff SoC supported; 21 arm SBC boars supported) https://github.com/warpme/miniarch (Enabler of ArchLinux ARM on 21 different arm SBC boars)
-
@Pic55 great you find time to play with this. many thx! i'm really surprised about hang of tx6-p model. ideally will be to see what logging on UART says. Is armbian working ok on this box? btw: I suspect hang is at wifi driver. Interesting will be to -mount sd card ROOTFS partition under Linux -delete /rootfs-ro/lib/modules/5.17.0-rc6/kernel/drivers/net/wireless/* -see is it booting
-
Pic55: many many thx! May you spent more 2..3 minutes on this? If yes - pls make sure that file minimyth.conf on partition BOOT has uncommented entry MM_LCDPROC_ENABLED='openvfd' (probably you download SD card image variant in which this var is not set by default. i corrected this approx 12:45 CET) Re: TX6-P: did box get IP addr at all or rather i.e. hang on DHCP stage? If it is failing on Eth - you can try with WiFi. 1. leave Eth unconnected 2. set in minimyth.conf MM_WLAN_SSID='your net' and MM_WLAN_PASS='your pass' sorry dragging you with all this!
-
@awawa thx for keeping eye on this! i opened my box and look with oscilloscope on sda/scl pins on fd650. -with factory android: led display works; 3.3v + every 0.5sec series of to low polarity pulses -with yours armbian: led display black; constant 3.3v without any pulses -with mine distro: led display black; constant 3.3v without any pulses So for me it looks like: -issue is not due missed pull-ups -issue is because my board uses different gpio i don't believe issue is i.e.due miss-working gpio controller as i have working i.e. wifi which uses near gpio pin228. Now i see: you have tanix-tx6-p while i have tanix-tx6. This may explain: in fact we have different devices. I dumped boot/system/vendor/dtbo partitions from factory Android - and i want to extract android dtb to see what gpio are used to drive fd650 on my box. Has anybody any hint what is easiest way to do this? (playing mkdtboimg.py or...?) In the meantime i want to see how population of various tanix-tx6 variants looks like. Are users of tanix-tx6 may give me favour please and: -download my distro (https://github.com/warpme/minimyth2/releases/download/v11.28.3-master-Pre-122-g6a79086179/MiniMyth2-armv8-master-11.28.3.r122-board-h6.tanix_tx6-board-s912-SD-Image.img.xz) -burn to SD card -if lcd display not works: telnet to box (user is root; no password) and provide me pls dmesg + possible box details thx in advance!
-
Pls find dmesg from armbian running on my tanix-tx6: [ 3723.481800] OpenVFD: Version: V1.4.1 [ 3723.481839] OpenVFD: vfd_gpio_clk: #0 = 0x01; #1 = 0xE5; #2 = 0x00; [ 3723.481857] OpenVFD: vfd_gpio_dat: #0 = 0x01; #1 = 0xE6; #2 = 0x00; [ 3723.481873] OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481889] OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481905] OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481921] OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481936] OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481950] OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00; [ 3723.481969] OpenVFD: vfd_chars: #0 = 0x02; #1 = 0x04; #2 = 0x03; #3 = 0x02; #4 = 0x01; [ 3723.481992] OpenVFD: vfd_dot_bits: #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06; [ 3723.482011] OpenVFD: vfd_display_type: #0 = 0x01; #1 = 0x00; #2 = 0x00; #3 = 0x03; [ 3723.482026] OpenVFD: Detected gpio chips: 300b000.pinctrl, 7022000.pinctrl. [ 3723.482037] OpenVFD: "300b000.pinctrl" chip found. base = 0, pin count = 256, pin = 229, offset = 229 [ 3723.482055] OpenVFD: "300b000.pinctrl" chip found. base = 0, pin count = 256, pin = 230, offset = 230 [ 3723.482071] OpenVFD: Skipping vfd_gpio_stb evaluation (0xFF) [ 3723.482080] OpenVFD: Skipping vfd_gpio0 evaluation (0xFF) [ 3723.482088] OpenVFD: Skipping vfd_gpio1 evaluation (0xFF) [ 3723.482096] OpenVFD: Skipping vfd_gpio2 evaluation (0xFF) [ 3723.482104] OpenVFD: Skipping vfd_gpio3 evaluation (0xFF) [ 3723.482662] OpenVFD: Select FD650 controller [ 3723.482777] OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups off) On my box with my distro i tried multiple ways: 1. by providing all data in DT 2. by inserting openvfd.ko with params taken from https://github.com/arthur-liberman/vfd-configurations/blob/master/tanix-tx6-allwinner-h6-vfd.conf 3. by adding in /etc/modprobe.d file openvfd.conf with content like this: # This file must be renamed to vfd.conf and placed in the /storage/.config/ folder. # # Tanix TX6 - Allwinner H6 configuration #-------------------- #gpio_xxx: # [0] 0 = &gpiochip0, 1 = &gpiochip1. # [1] pin number # [0] Reserved - must be 0. options openvfd vfd_gpio_clk=1,229,0 options openvfd vfd_gpio_dat=1,230,0 options openvfd vfd_gpio_stb=0,0,0xFF options openvfd vfd_gpio_chip_name="300b000.pinctrl" #chars: # < DHHMM > Order of display chars (D=dots, represented by a single char) options openvfd vfd_chars=2,4,3,2,1 #dot_bits: # Order of dot bits. Typical configurations: # Display Type 0, 1 usually has Alarm, USB, Play, Pause, Col, Ethernet, Wifi dots # Alarm = 0, USB = 1, Play = 2, Pause = 3, Col = 4, Eth = 5, Wifi = 6 # Display Type 2 usually has APPS, USB, SETUP, CARD, Col, HDMI, CVBS dots # APPS = 0, USB = 1, SETUP = 2, CARD = 3, Col = 4, HDMI = 5, CVBS = 6 # Display Type 3 Power, LAN, Col, Low Wifi, High Wifi # N/A = 0, N/A = 1, Power = 2, LAN = 3, Col = 4, Low Wifi = 5, High Wifi = 6 options openvfd vfd_dot_bits=0,1,2,3,4,5,6 #display_type: # [0] - Display type. # [1] - Reserved - must be 0.. # [2] - Flags. (bit 0 = '1' - Common Anode display) # [3] - Controller. options openvfd vfd_display_type=0x01,0x00,0x00,0x03 on every case i examined dmesg to make sure module loads ok. no matter what - display is black for me most probable issue is in bus from SOC to fd650: gpio wrong lines or logic state voltages are out of working levels. i don't believe tanix changed gpio between board versions.... but it is highly probable i.e. some Chinese manager decided to save 0.01$ by not soldering 2 pull-up resistors. or soldered resistors with way too high resistance... thats why i'm curious what board you have? (mine is H6-06_V1.0 2019-07-10)
-
@awawa Since few days i'm trying to get openvfd working on tanix-tx6 in my project. i'm on 5.17 kernel and dmesg's openvfd entires are looking like expected - but display is black. Hw is ok as under factory android led disp. works ok. I installed latest armbian from your git, kick systemctl start openvfd and...display is also black. I verified LED IC on my tanix-tx6: it is fd650. As you have it working + my box failing on sources build 5.17+openvfd1.4.1 nor on your armbian not with jernej's i2c with py code - i see 2 possible reasons: -my box is using different gpio's -my box has missing pull-ups on SDA/SCL (so wire OR not works) What board version you have in your box?