Jump to content

Lamerjack

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

12284 profile views
  1. My Nanopi Neo3 after a reboot hangs. I have to remove power and apply again. I read that is due to Device Tree. Someone has a suggestion to fix it?
  2. I added to armbianENV.txt //after overlay_prefix=sun50i-h5 overlays=spi-spidev param_spidev_spi_bus=0 //at the second last line user_overlays=spilcd nano spilcd.dts and i copy inside content of your dts file then i have to compile it: dtc -I dts -O dtb -o spilcd.dtbo spilcd.dts mkdir/boot/overlay-user cp spilcd.dtbo /boot/overlay-user/ pin used 19 SPI_MOSI 21 SPI_MISO (Not ncessary) 23 SPI_CLK 15 LCD_D/C (GPIO A3 ) 7 LCD_RESET (GPIOA6) GND CS +3.3 LED_EN but: root@orangepipc2:~# dmesg |grep spi [ 2.045242] sun6i-spi 1c68000.spi: chipselect 0 already in use [ 2.045255] spi_master spi0: spi_device register error /soc/spi@1c68000/spidev@0 [ 2.045285] spi_master spi0: Failed to create SPI device for /soc/spi@1c68000/spidev@0 [ 2.045319] sun6i-spi 1c68000.spi: chipselect 0 already in use [ 2.045329] spi_master spi0: spi_device register error /soc/spi@1c68000/spi-flash@0 [ 2.045350] spi_master spi0: Failed to create SPI device for /soc/spi@1c68000/spi-flash@0 [ 2.699582] panel-ilitek-ili9341 spi0.0: get optional vcc failed [ 2.701226] [drm] Initialized ili9341 1.0.0 20210716 for spi0.0 on minor 2 [ 3.252030] panel-ilitek-ili9341 spi0.0: [drm] Initialized display serial interface [ 3.351215] panel-ilitek-ili9341 spi0.0: [drm] fb0: ili9341drmfb frame buffer device root@orangepipc2:~# lsmod | grep ili9341 ili9341 16384 0 panel_ilitek_ili9341 20480 2 drm_mipi_dbi 28672 2 ili9341,panel_ilitek_ili9341
  3. If someone other need a fix. I found this post: at the point 2 there is a working fix!
  4. Hi Mhel, Thank you for your post is very interesting... But can you add some info for who ha no experience with overlay? I was able to use a spi display with a legacy kernel and now i'm trying to use with a new kernel on orange pi PC2 i suppose that the pins to use are: 19 SPI_MOSI 21 SPI_MISO 23 SPI_CLK 15 LCD_D/C (GPIO A3 ) 7 LCD_RESET (GPIOA6) +3.3 LED_EN Is it correct? I suppose that for edit env i have to do: sudo nano /boot/armbianEnv.txt but what i have to do to add the overlay that you did? p.s. many of the examples that i found are only for H3 your is valid also for H5... do you think is possible to use also with a nanopi neo 3 that has this Soc: RockChip RK3328, Quad-core 64-bit high-performance Cortex A53? i suppose that i have to add the correct prefix to this line: compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; Is it correct?
  5. @djjerdog can you be more specific with - Replaced all usb2 references to usb0?
  6. In /etc/apt/sources.list i had to change deb http://security.debian.org/ bullseye/updates main contrib non-free to deb http://security.debian.org/debian-security bullseye-security main contrib non-free is it correct? the boot still say buster: lab1@192.168.0.14's password: ___ ____ _ ____ ____ / _ \| _ \(_) | _ \ / ___| | | | | |_) | | | |_) | | | |_| | __/| | | __/| |___ \___/|_| |_| |_| \____| Welcome to Armbian 21.02.3 Buster with Linux 5.10.60-sunxi System load: 65% Up time: 0 min Memory usage: 16% of 967M IP: 192.168.0.14 CPU temp: 49°C Usage of /: 27% of 15G but htop correctly report bullseye
  7. Works Fine! Also in 4k. Now i have a strange request. Maybe i'm ot... but maybe someone can give me suggestion or tell me that is not possible with OrangePI
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines