Nazar Gerasymchuk

Members
  • Content Count

    10
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by Nazar Gerasymchuk

  1. I have few of i2c devices that was successfully tested working with RPi Zero W (Tiny RTC, BME280), but no one is visible to NanoPi Neo Air board with Armbian. I can't get it to work on latest few versions of Armbian. As soon as I add i2c0 to overlays there appears two of i2c devices (both silent): $ ls -la /dev/i2c* crw-rw---- 1 root i2c 89, 0 Jan 28 14:58 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 Jan 28 14:58 /dev/i2c-1 I need to admit that scan itself took quite significant amount of time. $ sudo time i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 0.00user 0.04system 3:59.62elapsed 0%CPU (0avgtext+0avgdata 1036maxresident)k 0inputs+0outputs (0major+64minor)pagefaults 0swaps Since it could be a problem with pull-up resistors, I've tried to add 4K7 resistors to SDA and to SCL lines, but situation remains the same. What am I doing wrong? What step is missed? Will appreciate any help. Thank you.
  2. Thank you for quick response, @martinayotte > Could be that you mistakenly crossed SDA and SCL ? Checked and re-checked for a lots of times, tried different jumpers and different breadboards. Unfortunately I have no oscilloscope to check if i2c bus is working, but are there any ways to test the bus? E.g.: what does it means if i2cdetect scan takes so much time? Could it signalize something?
  3. Ok, got it. Thanks for quick response!
  4. Good day, What is the best and easiest way to deal with situation: The following packages have unmet dependencies: armbian-config : Depends: debconf-utils but it is not going to be installed Depends: html2text but it is not going to be installed Depends: html2text but it is not going to be installed mc : Depends: mc-data (= 3:4.8.18-1) but it is not going to be installed nfs-kernel-server : Depends: libtirpc1 (>= 0.2.4) but it is not going to be installed Depends: nfs-common (= 1:1.3.4-2.1) but it is not going to be installed Depends: keyutils but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Ign:1 http://httpredir.debian.org/debian stretch InRelease Ign:2 http://security.debian.org stretch/updates InRelease Ign:3 http://apt.armbian.com stretch InRelease Ign:4 http://httpredir.debian.org/debian stretch-updates InRelease Err:5 http://security.debian.org stretch/updates Release 500 Internal Server Error Ign:6 http://httpredir.debian.org/debian stretch-backports InRelease Err:7 http://apt.armbian.com stretch Release 500 Internal Server Error Err:8 http://httpredir.debian.org/debian stretch Release 500 Internal Server Error Err:9 http://httpredir.debian.org/debian stretch-updates Release 500 Internal Server Error Err:10 http://httpredir.debian.org/debian stretch-backports Release 500 Internal Server Error Reading package lists... Done E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://apt.armbian.com stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. When trying to build Armbian?
  5. Is there any way to configure alternative sources and/or timeout options and/or any general recommendations?
  6. Sorry if this is silly question, but I can't find any straight-forward documentation on this topic. I've seen that Mali drivers was available for older kernel, but what about mainline? Asking this especially in context with this finding -- Maxime Ripard's article "Mali OpenGL support on Allwinner platforms with mainline Linux". Currently on clean Armbian install on NanoPi Neo Air I can't load mali: $ modinfo mali modinfo: ERROR: Module mali not found.
  7. Nazar Gerasymchuk

    Is Mali GPU driver available in Mainline for H3?

    Customers: for example me and you (I suppose), since we both purchased H3 boards, and its GPU can't be used with mainline. I'm Ok with running closed-sourced or partially open-sourced drivers, but how can I do it on H3 with mainline? If this is possible, I'd like to ask you to share any useful documentation here. Thanks.
  8. Nazar Gerasymchuk

    Is Mali GPU driver available in Mainline for H3?

    @Tido Thank you for your quick answer. I've heard about Lima, and I can see that it is in deep development right now (at least as it is stated on Sunxi site http://linux-sunxi.org/Mali). My main confusion came from situation that there are lots of H3 boards that works quite well with mainline kernel, and there is no option to use GPU. from customer side it looks very strange. --- One more (silly) question, what does it means that there is dts already in mainline kernel -- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/sun8i-h3.dtsi#n156? Doesn't it make usable Mali driver?
  9. Nazar Gerasymchuk

    Nazar Gerasymchuk

  10. Hello @Igor! I'm ready for testing. Have few of NanoPi Neo Air and will be able to find some spare time for it.
  11. My problem is that each time I try to do anything related to LCD over frame buffer I got next error: ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device LCDs (ili9341, st7735s) I'm able to test behave exactly the same way -- every time lighted up white screen, but nothing more. I have NanoPi Neo Air with Armbian (5.59 Nanopiair Debian stretch 4.14.65) on it. All packages in system already updated to latest available versions. Problem remains as on stable kernel, same on nightly build. Currently I have: $ uname -a && cat /etc/issue Linux nanopiair 4.14.74-sunxi #330 SMP Mon Oct 8 00:57:54 CEST 2018 armv7l GNU/Linux Debian GNU/Linux 9 \n \l I'm successfully loading SPI: $ grep spi /boot/armbianEnv.txt overlays=spi-spidev usbhost1 usbhost2 param_spidev_spi_bus=0 param_spidev_spi_cs=0 Here is the way I'm trying to load fbtft_device (e.g. Waveshare 1.44 which is st7735s): modprobe fbtft_device name=fb_st7735r speed=16000000 busnum=0 cs=0 gpios=reset:1,dc:201,led:200,cs:67 custom=1 fps=60 bgr=1 custom=1 verbose=3 width=128 height=128 Wiring was already rechecked for few times already. As a result I can see in dmesg: [ 171.665158] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 171.670433] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 171.671639] spidev spi0.0: spidev spi0.0 1000kHz 8 bits mode=0x00 [ 171.671746] spidev spi0.0: Deleting spi0.0 [ 171.672721] fbtft_device: GPIOS used by 'fb_st7735r': [ 171.672735] fbtft_device: 'reset' = GPIO1 [ 171.672739] fbtft_device: 'dc' = GPIO201 [ 171.672743] fbtft_device: 'led' = GPIO200 [ 171.672749] fbtft_device: 'cs' = GPIO67 [ 171.672765] spi spi0.0: fb_st7735r spi0.0 16000kHz 8 bits mode=0x00 [ 171.684388] fb_st7735r: module is from the staging directory, the quality is unknown, you have been warned. [ 172.603112] Console: switching to colour frame buffer device 16x16 [ 172.603392] graphics fb0: fb_st7735r frame buffer, 128x128, 32 KiB video memory, 4 KiB buffer memory, fps=100, spi0.0 at 16 MHz And there is /dev/fb0. But unfortunately next actions can't draw anything on screen: sudo head --bytes 153600 /dev/urandom > /dev/fb0 yes | head --bytes 76800 > /dev/fb0 The only way to get at least some error is to run (from user of from sudo): $ fbset -i -v ioctl FBIOGET_VSCREENINFO: Inappropriate ioctl for device I'll appreciate any help. Thanks.