kutysam

Members
  • Content Count

    29
  • Joined

  • Last visited


Reputation Activity

  1. Like
    kutysam got a reaction from GusAntoniassi in Guide: How to use Touchscreen + LCD on H3 devices   
    FAQ / Personal Experiences
    Q1) If you wish to do manual testing, without rebooting, we have to rmmod and then modprobe manually [Make sure you have already done all the steps till depmod
    sudo rmmod fbtft_device sudo rmmod fbtft sudo rmmod ads7846_device sudo rmmod ads7846 sudo modprobe ads7846 sudo modprobe ads7846_device model=7846 cs=1 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900 sudo modprobe fbtft sudo modprobe fbtft_device rotate=90 name=piscreen speed=16000000 gpios=reset:2,dc:71 txbuflen=32768 fps=25  
    Q2) My mainline kernel suddenly doesn't show me that my device is touchable through evtest. I experienced this and i did the following
    Remove all on boot loading for ads7846 and fbtft
    sudo rm /etc/modules-load.d/ads7846.conf sudo rm /etc/modprobe.d/ads7846_device.conf sudo rm /etc/modprobe.d/fbtft.conf sudo rm /etc/modules-load.d/fbtft.conf After which, lets manually 'automatically' load them through rc.local
    nano /etc/rc.local modprobe ads7846 modprobe ads7846_device model=7846 cs=1 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900 modprobe fbtft modprobe fbtft_device rotate=90 name=piscreen speed=16000000 gpios=reset:2,dc:71 txbuflen=32768 fps=25 con2fbmap 1 0 Take note that con2fbmap is either 1 0 or 1 1 for mainline (1 0 --> orange pi lite or devices without AVOUT, 1 1 --> for devices with AVOUT like orange pi zero)
    For advanced users, check /dev/ and see what is your fbX
     
    Q3) I have installed a GUI for my mainline kernel but touch stops at times.
    I experience this too and I have no idea on how to fix it.
     
    Q4) I need to calibrate it
    Yes, me too. However, my device isn't working very well. You need tslib and stuff to do the calibration.
  2. Like
    kutysam got a reaction from GusAntoniassi in Guide: How to use Touchscreen + LCD on H3 devices   
    Mainline Kernel [You can use BOTH LCD and TOUCH]
    1) Enable overlays for spi and cs1
    sudo nano /boot/armbianEnv.txt add the following to the bottom overlays=spi-spidev spi-add-cs1 param_spidev_spi_bus=0 param_spidev_spi_cs=1 2) Reboot your device
     
    LCD
    1) Load fbtft and fbtft_device on boot
    sudo nano /etc/modules-load.d/fbtft.conf fbtft fbtft_device 2) Load fbtft_device options
    nano /etc/modprobe.d/fbtft.conf options fbtft_device rotate=90 name=piscreen speed=16000000 gpios=reset:2,dc:71 txbuflen=32768 fps=25 3) Since there is no GUI in mainline, lets enable the console to be displayed to LCD instead
    sudo nano /etc/rc.local con2fbmap 1 1 For some others, you may wish to try con2fbmap 1 0 [If your device has no AVout]
     
    4) Reboot your device (sudo reboot) and you screen should be lit up
    ===========================================================================
    TOUCH
    1) Download ads7846 touch driver (compatible with xpt2046)
    mkdir ds7846 cd ds7846 wget https://sourceforge.net/p/openipmi/linux-ipmi/ci/master/tree/drivers/input/touchscreen/ads7846.c?format=raw mv ads7846.c?format=raw ads7846.c 2) Create a makefile (Take note that it is TABS instead of spaces before the $(MAKE))
    nano Makefile Insert the below in without the ----- -------------------------------- obj-m := ads7846.o KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd) all: $(MAKE) -C $(KDIR) M=$(PWD) modules clean: $(MAKE) -C $(KDIR) M=$(PWD) clean install: $(MAKE) -C $(KDIR) M=$(PWD) modules_install -------------------------------- 3) Exit nano and run the following
    sudo make sudo make install sudo depmod 4) Download and compile and install ads7846_device
    cd .. git clone https://github.com/notro/fbtft_tools/ cd fbtft_tools/ads7846_device make sudo make install sudo depmod 5) Load ads7846 and ads7846_device on boot
    sudo nano /etc/modules-load.d/ads7846.conf ads7846 ads7846_device 6) Load ads7846_device options
    nano /etc/modprobe.d/ads7846_device.conf options ads7846_device model=7846 cs=1 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900  
  3. Like
    kutysam got a reaction from GusAntoniassi in Guide: How to use Touchscreen + LCD on H3 devices   
    First of all, credits goes to https://4pda.ru/forum/lofiversion/index.php?t750921-2560.html
    Device that I used for this guide: https://www.aliexpress.com/item/3-5-Inch-TFT-LCD-Moudle-For-Raspberry-Pi-2-Model-B-RPI-B-raspberry-pi/32707058182.html
    Pinout: http://www.waveshare.com/3.5inch-rpi-lcd-a.htm (Yes, the device is a waveshare knockoff)
    How to place the device? For Orange pi lite/one it is reversed. For the rest, it should be normal.
    Refer to https://forum.armbian.com/index.php?/topic/724-quick-review-of-orange-pi-one/ for more info.
     
    There are two sections to this guide.
    Legacy / Mainline


    Legacy Kernel [You can only EITHER use touch or LCD due to issues with spi chip select]

    LCD

    1) Load fbtft and fbtft_device on boot

    sudo nano /etc/modules-load.d/fbtft.conf fbtft fbtft_device
    2) Load fbtft_device options

    nano /etc/modprobe.d/fbtft.conf options fbtft_device rotate=90 name=piscreen speed=16000000 gpios=reset:2,dc:71 txbuflen=32768 fps=25
    3) Make sure X11 loads to the correct framebuffer (fb8 for legacy)

    nano /etc/X11/xorg.conf.d/50-fbturbo.conf find fb0 and change to fb8
    4) Reboot your device (sudo reboot) and you screen should be lit up


    ============================================
    TOUCH

    1) Download ads7846 touch driver (compatible with xpt2046)

    mkdir ds7846 cd ds7846 wget https://raw.githubusercontent.com/raspberrypi/linux/rpi-3.6.y/drivers/input/touchscreen/ads7846.c
    2) Create a makefile (Take note that it is TABS instead of spaces before the $(MAKE))

    nano Makefile Insert the below in without the ----- -------------------------------- obj-m := ads7846.o KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd) all: $(MAKE) -C $(KDIR) M=$(PWD) modules clean: $(MAKE) -C $(KDIR) M=$(PWD) clean install: $(MAKE) -C $(KDIR) M=$(PWD) modules_install --------------------------------
    3) Exit nano and run the following

    sudo make sudo make install sudo depmod
    4) Download and compile and install ads7846_device

    cd .. git clone https://github.com/notro/fbtft_tools/ cd fbtft_tools/ads7846_device make sudo make install sudo depmod
    5) Load ads7846 and ads7846_device on boot

    sudo nano /etc/modules-load.d/ads7846.conf ads7846 ads7846_device
    6) Load ads7846_device options

    nano /etc/modprobe.d/ads7846_device.conf options ads7846_device model=7846 cs=0 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900
    7) Reboot your device and run evtest
    sudo reboot sudo evtest Find your touch device and happy touching. Every touch should generate an event.
  4. Like
    kutysam got a reaction from Orfait in How do I make arecord work in Mainline (Opi Zero)   
    Problem solved.
     
    For Mainline, do this
    1) alsamixer
    2) press TAB (Make sure it falls to F4: CAPTURE)
    3) Move to Mic1 (Use arrow keys)
    4) Press SPACE and (L R Capture will appear)
    Quit and you are good to go.
  5. Like
    kutysam got a reaction from Igor in How to start a sound?   
    You need to enable audio overlay
    nano /boot/armbianEnv.txt
    overlays=analog-codec
     
    then try aplay. For arecord, refer here https://forum.armbian.com/index.php?/topic/4714-how-do-i-make-arecord-work-in-mainline-opi-zero/&tab=comments#comment-35741
  6. Like
    kutysam reacted to Igor in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    Froze kernel upgrading in armbian-config and than apt-upgrade won't upgrade system packages ( kernel, uboot, bsp, ...)
  7. Like
    kutysam reacted to Igor in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    Updated dev / testing image for Opi Zero, wireless + upstream patches included: https://dl.armbian.com/orangepizero/Ubuntu_xenial_dev.7z
  8. Like
    kutysam reacted to giri@nwrk.biz in [Program] Move Composite AV Video Output to fix Overscanning   
    Hey folks!
     
    On monday I was able to fix the overscanning issue of my Orange Pi zero (read here).
    Because fiddling around with the register values can be pretty harsh some times I decided to created a small programm to move the picture of the composite video output. You can find the project page here: https://projects.nwrk.biz/projects/allwinner-tvout
     
    With this tool you can easily move the picture relative to its actual position by just calling :
    $ sudo tvout -m -x <value in px> -y <value in px>  
    To reset the position you can use:
    $ sudo tvout -r  
    I hope some of you may find this useful.
    If I have enough spare time i will add more features to this project (like changing the resolution, etc.). If you have any questions or ideas please feel free to tell me in this thread!

     
  9. Like
    kutysam reacted to giri@nwrk.biz in PSA: Orange Pi Zero expansion board tv-out not working solution   
    Yeah!! I managed to fix the overscanning issue!  (Credits go to this guy here for pointing me to the right direction!).
     
    All in all my Picture was Overscanning 20 px on every edge.
     
    At first I changed my resolution from the detected 720x576 to 680x536 (2 * -20 px = -40 px) in the script.bin. This results in an visible edge at the bottom of the screen and an visible edge on the right hand side (with a small black border!).
    $ bin2fex /boot/script.bin ~/script.fex $ nano ~/script.fex find these lines: fb0_width = 0 fb0_height = 0 and change them to: fb0_width = 680 fb0_height = 536 then: $ fex2bin ~/script.fex ~/script.bin $ sudo cp ~/script.bin /boot $ sudo reboot  
    Now the picture needs to be moved down and to the right by 40px to be fully visible!
     
    Next I needed to manipulate TV ENCODER RE-SYNC PARAMETERS REGISTER of the H2+ SoC. For this I used a little tool called devmem2 which helped me to directly read and write to the memory, and thus allowed me to manipulate the H2+ registers!
     
    devmem2 can be installed by using following commands:
    wget http://free-electrons.com/pub/mirror/devmem2.c gcc ./devmem2.c sudo mv ./a.out /usr/local/bin/devmem2  
    After Installing devmem2 I was able to shift the picture by manipulating the value on following Address: 0x01E00130! (=TV ENCODER RE-SYNC PARAMETERS REGISTER, this may differ depending on your SoC, check the Datasheet!)
    First I read back the actual value (so I could revert back changes in case I messed anything up!):
     
    $ sudo devmem2 0x01E00130 /dev/mem opened. Memory mapped at address 0xb6f0d000. Value at address 0x1E00130 (0xb6f0d130): 0x3005000A Now I was able to move the picture by writing a custom value to the register according to the R40 Datasheet: 
     
    TV ENCODER RE-SYNC PARAMETERS REGISTER Datasheet entry:
     
    Here is how I calculated this value with the help of the Datasheet:
    31 ... Re-Sync Field => 0b 
    30 ... Re-Sync Disable => 0b
    29:27 ... not used => 000b
    26:16 ... Vertical => 40d px => 0000101000b
    15:11 ... not used => 00000b
    10:0 ... Horizontal => 40d px => 0000101000b
     
    All in All: 000000000101000000000000101000b => 0x00140028
    So I used this command to set my display:
    $ sudo devmem2 0x01E00130 w 0x00140028 EDIT: I created a small tool which does the work above for you
     
    Finally I saved the command above in my rc.local file to shift the picture during boot.
    $ sudo nano /etc/rc.local paste following line: devmem2 0x01E00130 w 0x00140028 This is a dirty workaround and should be fixed within the driver!
     
    Pictures:
     
     
    Hope this helps to correct your overscanning issues! This should also work with many other Allwinner based Boards. I read that some Bananapi users had a pretty similar problem with overscanning on AV out.
  10. Like
    kutysam reacted to ldiaz in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    This was my original proposal to use an overlay I posted one initial version that I wan't able to make work but I'm not a DTS expert maybe someone can simply aling it with the patch that @martinayotte created.
     
     
  11. Like
    kutysam reacted to ldiaz in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    That would be even better. do you think @martinayotte will be able to do it from his private build?
     
  12. Like
    kutysam reacted to raschid in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    I am fully aware that that there have been issues in the past with some peoples expectations regarding this driver.
    But this very thread shows that a significant fraction of users seem to be fine with its limited function and performance.
    The download page for the OPi Zero already provides ample warning regarding the "module quality".
     
  13. Like
    kutysam reacted to raschid in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    Nice - that fixed it.
     
    [ 74.030917] systemd[1]: apt-daily.timer: Adding 1h 13min 16.687045s random time. [ 177.557914] xradio_wlan mmc1:0001:1: missed interrupt [ 236.371472] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 283.880879] wlan0: authenticate with 80:1f:02:d0:__:__ [ 283.880976] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (0)IEEE80211_CONF_CHANGE_IDLE (1) [ 283.883019] wlan0: send auth to 80:1f:02:d0:__:__ (try 1/3) [ 283.897534] wlan0: authenticated [ 283.907946] wlan0: associate with 80:1f:02:d0:__:__ (try 1/3) [ 283.911220] wlan0: RX AssocResp from 80:1f:02:d0:__:__ (capab=0x411 status=0 aid=5) [ 283.911463] ieee80211 phy0: vif 0, configuring tx [ 283.911941] ieee80211 phy0: vif 0, configuring tx [ 283.912366] ieee80211 phy0: vif 0, configuring tx [ 283.912788] ieee80211 phy0: vif 0, configuring tx [ 283.915753] wlan0: associated [ 283.915973] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 284.018331] ieee80211 phy0: CCMP_PAIRWISE keylen=16!  
    No more "xradio_wlan mmc1:0001:1: received frame has no key status" message spamming the logs.
     
    Great. Thx, Zador
     
     
  14. Like
    kutysam got a reaction from gungsukma in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    For those whom want 4.10 LAST nightly for OPIZero where xr819 wifi is working, the link is here.
    https://drive.google.com/file/d/0B8aNiHBlMQ9cbnpaUHJMa2pyWUk/view?usp=sharing
    I never deleted this thankfully. 
  15. Like
    kutysam got a reaction from devman in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    For those whom want 4.10 LAST nightly for OPIZero where xr819 wifi is working, the link is here.
    https://drive.google.com/file/d/0B8aNiHBlMQ9cbnpaUHJMa2pyWUk/view?usp=sharing
    I never deleted this thankfully. 
  16. Like
    kutysam got a reaction from JL604 in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    For those whom want 4.10 LAST nightly for OPIZero where xr819 wifi is working, the link is here.
    https://drive.google.com/file/d/0B8aNiHBlMQ9cbnpaUHJMa2pyWUk/view?usp=sharing
    I never deleted this thankfully. 
  17. Like
    kutysam reacted to tkaiser in orange pi zero reaches 85 degrees with heatsink!   
    That works surprisingly well even with zero airflow around. If you use the search function you'll find numbers.
     
    Wrt real topic: https://forum.armbian.com/index.php?/topic/4313-new-opi-zero-yet-another-high-temperature-issue/ (nobody uses search function here and nobody tries to nail the culprit down)
     
  18. Like
    kutysam reacted to martinayotte in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    @kutysam, I don't think that patch is the only requirement, since I've tried it several weeks ago, but driver was still failing.