• Content Count

  • Joined

  • Last visited

About jistycs

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It was weird for me as well, that's why I firstly thought it was a bigger issue. And I just ended up with this solution with "let's try to see what happens if..."
  2. The following issue occurs on kernel 4.13.9. I haven't tested any other version, but martinayotte commented it wasn't happening on 4.11 Helo, If you installed a brand new image you'll notice that there's an I2C device by default which shows inexistent devices, like: root@orangepione:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This can be fixed adding the i2c0 overlay at boot. Make sure this 2 lines are written in /boot/armbianEnv.txt: overlay_prefix=sun8i-h3 overlays=i2c0 After rebooting, you'll find that i2c-0 bus works properly, while there's now a new i2c-1 which has the same problem mentioned above. It also fixed some problems I was having with a multitouch screen, somehow, so have it in mind if you're suffering this kind of issue. For anyone who has troubles with the BMP280 sensor: Enable modules by modprobe (or /etc/modules): bmp280-i2c bmp280 Create the device by writing: echo "bmp280 0x76" > /sys/bus/i2c/i2c-0/new_device Now the sensor can be accessed at: /sys/bus/i2c/devices/0-0076/iio:device1
  3. I'm using this one. There's a reference here http://linux-sunxi.org/GPIO#C.2FC.2B.2B_program, but don't remember where I found it because it seems there's no such link in that page. The lib itself are only 2 files: a .h and a .c, and there's also a .c which is an example. I've been using it on a Vanilla Desktop image (legacy kernel) on an Orange Pi One, and I haven't found any troubles so far. I hope this helps gpio.zip
  4. UPDATE: I built the dev branch and both screen and touchscreen works perfectly on: uname -a Linux orangepione 4.11.12-sun8i #5 SMP Mon Oct 16 22:53:23 ART 2017 armv7l armv7l armv7l GNU/Linux So it's gotta be a bug in the legacy kernel. I tried a fresh 5.25 Legacy Armbian Desktop to test, and same results than on 5.31. So, the only solution I've currently found is to use Mainline builds. Now I really need Mali Drivers to be released for Mainline because I need HW acceleration . Nevertheless, I hope this research helps someone. I'll update with anything future I achieve.
  5. I just uploaded my compilation if someone want to try it. I use it perfectly on my Orange Pi One with Armbian 5.31. It has QtQuick 2. https://mega.nz/#!6ZMi2JjZ!dr5X2hchlAhKlBzZ4mvouo16ij0mIMFO9HPClISxSNE I won't (currently) upload de source code because it takes 550mb and it's the original without any modification but the sunxi file found everywhere. I have that folder in /usr/share, and you've gotta use /usr/share/Qt-5.9.0/bin/qmake in your project's folder to create the right makefile. Then simply use make
  6. I'll attach a notes file I made when I was compiling it. I made it with 5.8 and 5.9, running QtQuick over X11 (can't make EGLFS work) You can find linux-sunxi-g++ file at http://linux-sunxi.org/. I don't remember which page exactly. Also, I had to try "make" many times because it runs out of memory. I compiled it on an Orange Pi One, and it takes more than 12 hours. But once done, you back that folder up and it's already done for further installations [ Compiled in Armbian Desktop 5.24 and Qt 5.8 ] 1. Download Qt Source-code (Qt Everywhere) 2. Copy linux-sunxi-g++ folder to QtSrcDir/qtbase/mkspecs/devices/ 3. Install packages: apt-get install gcc-4.8 g++-4.8 zlib1g-dev libxcb1 libxcb1-dev libx11-xcb1 libx11-xcb-dev libxcb-keysyms1 libxcb-keysyms1-dev libxcb-image0 libxcb-image0-dev libxcb-shm0 libxcb-shm0-dev libxcb-icccm4 libxcb-icccm4-dev libxcb-sync0-dev libxcb-render-util0 libxcb-render-util0-dev libxcb-xfixes0-dev libxrender-dev libxcb-shape0-dev libxcb-randr0-dev libsqlite3-dev libxcb-glx0-dev libxcb-xinerama0-dev libgles2-mesa-dev libpcre16-3 3.1. If copying QtDir on new installation, just install: apt-get install libgles2-mesa-dev libpcre16-3 4. cd QtSrcDir/ 5. ./configure -release -opensource -confirm-license -no-use-gold-linker -nomake examples -nomake tests -nomake tools -no-cups -no-pch -linuxfb -skip multimedia -skip webengine -opengl es2 -eglfs -system-xcb -system-zlib -no-harfbuzz -device linux-sunxi-g++ -device-option CROSS_COMPILE=arm-linux-gnueabihf- [ Notes ] Some components have to be compiled appart (i.e. QtQuickComponents(2), QtGraphicalEffects) Fonts are not included in Qt and must be placed in $QTDIR/lib/fonts/ (TrueType fonts) [ Useful Links ] https://forum.armbian.com/index.php?/topic/1627-successfully-compile-qt57-on-orangepi-lite-on-armbian/ http://linux-sunxi.org/Qt5_For_Mali_Binaries FreeType error https://codereview.qt-project.org/#/c/175598/ (fixed in 5.8.1) I'll try later compiling with gold linker
  7. It comes with them installed by default, so no need to install them
  8. Now I'm facing another issue. I can get the touchscreen detected by kernel and by evdev, but it won't go further. Running on Armbian 5.31 - Ubuntu. Untouched kernel I can get a raw input by doing: root@orangepione:~# cat /dev/hidraw0 <dirty ascii chars, but response variates if I put different amount of fingers on it, so I know the touch itself is working (besides testing it on Windows)> This are my usb devices: root@orangepione:~# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 003: ID 0483:5750 STMicroelectronics Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Evtest output: root@orangepione:~# evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: vmouse /dev/input/event1: sunxi-gpiokey /dev/input/event2: sunxi-ths /dev/input/event3: sunxi-ir /dev/input/event4: MCE IR Keyboard/Mouse (sunxi-ir) /dev/input/event5: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 Select the device event number [0-5]: 5 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x483 product 0x5750 version 0x110 Input device name: "深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 0 Max 800 Event code 1 (ABS_Y) Value 0 Min 0 Max 480 Event code 24 (ABS_PRESSURE) Value 0 Min 0 Max 255 Event code 47 (ABS_MT_SLOT) Value 0 Min 0 Max 9 Event code 53 (ABS_MT_POSITION_X) Value 0 Min 0 Max 800 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min 0 Max 480 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min 0 Max 65535 Event code 58 (ABS_MT_PRESSURE) Value 0 Min 0 Max 255 Properties: Property type 1 (INPUT_PROP_DIRECT) Testing ... (interrupt to exit) It dies there. It only prints Event: time 1507570294.157946, -------------- SYN_REPORT ------------ the first time after connection. It will not print that again unless I disconnect and reconnect it. Dmesg: [ 176.072783] hid-multitouch 0003:0483:5750.0002: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on usb-sunxi-ohci-1/input0 This touchscreen ended up being way more difficult than what I expected, but the last fix (for video output) was really easy, so I hope this one too. I googled everywhere and I couldn't find anything. I also tried testing it with X11, xinput_calibrator, but no response. Thanks in advance!
  9. I couldn't find any side effect yet, so it seems to work properly. Way easier than patching the kernel and way easier to maintain with further updates
  10. This made the trick! Thank you all very much for your comments. I tried this before the other solutions because it was the simplest, and it worked perfectly! No needs to recompile the kernel or so. Just in case, I had to update this through the bin2fex and fex2bin because the armbian-config fex editor didn't save that setting.
  11. I know, but afaik there are some people who made it work using some patches or so. I need graphics acceleration, so mainline isn't a choice (unless you can tell me that QtQuick works good on there, without Mali drivers, which I doubt because it runs on OpenGL)
  12. Hello! I recently bought a generic Waveshare 800x480 HDMI (B) USB Touchscreen (rev 3.0), and I'm having problems to make it work properly on Armbian. After a long research, I ended up realizing it's a common problem, and yet I haven't been able to find a solution. It seems there was a patch somewhere, but that link is not available anymore. I'm using the Armbian Desktop 5.31 , running on an Orange Pi One. I've already set it up using h3disp -m 800x480 -d, and tried everything but it won't work. Vertical resolution seems to be right, but horizontal only fits around 3/4 of screen and it's noisy (the same problem everyone seems to have). I have tried this with my PC and works totally right, so it's not screen's fault. Also, xrandr gives the right dimensions. Despite I'm using TTY, originally it was a Desktop image, and I didn't delete any driver cat /dev/random > /dev/fb0 Noise can be seen better running xterm FEX configs: [disp_init] disp_init_enable = 1 disp_mode = 0 screen0_output_type = 3 screen0_output_mode = 31 screen1_output_type = 3 screen1_output_mode = 31 fb0_format = 0 fb0_width = 800 fb0_height = 480 fb1_format = 0 fb1_width = 800 fb1_height = 480 screen0_out_color_range = 1 hdcp_enable = 1 hdmi_cts_compatibility = 0 [hdmi_para] hdmi_used = 1 hdmi_power = "vcc-hdmi-18" hdcp_enable = 0 hdmi_cts_compatibility = 1 hdmi_x = 800 hdmi_y = 480 Thanks in advance!