Jump to content

guidol

Members
  • Posts

    1769
  • Joined

  • Last visited

Reputation Activity

  1. Like
    guidol reacted to raschid in H2: Sunvell R69 Android TV Box (AliExpress)   
    @guidol: Does the boot-stability improve, when you replace build/patch/u-boot/u-boot-sunxi/add-sunvell-r69.patch with the attached file (reduces DRAM clck to 408)?
    If stability improves, could you copy the OS to eMMC via armbian-config and check boot-stability?
    add-sunvell-r69.patch
  2. Like
    guidol reacted to JMCC in H6 boards: Orange Pi One Plus, Orange Pi 3 Plus and Pine H64   
    First linux image for H6 Orange Pi boards available: http://www.orangepi.org/downloadresources/
  3. Like
    guidol reacted to Allwonder in H2: Sunvell R69 Android TV Box (AliExpress)   
    Armbian images for R69 on Google Drive.
  4. Like
    guidol reacted to raschid in H2: Sunvell R69 Android TV Box (AliExpress)   
    Mainline kernel vers. 4.14.17 also works quite well (supporting eth, wifi, both usb-ports, emmc, ir, audio, ...). You could build it yourself with the armbian build system (https://docs.armbian.com/Developer-Guide_Build-Preparation/)
    # git clone --depth 1 https://github.com/armbian/build # cd build # ./compile.sh BOARD=sunvell-r69 for media stuff you better stay with the legacy kernel though ...
  5. Like
    guidol reacted to manuti in Kickstarter: Allwinner VPU support in the official Linux kernel   
    Founded. I like to bet for death horses!
    And the First additional stretch goal is reached 22.943 € Monday, February 5.
  6. Like
    guidol reacted to evilalex2 in Orange Pi Plus 2 support...   
    Hi, 
    You can use the OPi + image on the +2, thats what i do.
    The only divrence between them are the ram and emmc size, 1GB/8GB vs 2GB/16GB.
    After booting armbian wil display it has 2GB ram.
  7. Like
    guidol reacted to koval in Problem with WiFi (MT7601U) NanoPiNeo ( ARMBIAN 5.38 3.4.113-sun8i)   
    I've installed system with 4x kernel and now it works. 
     
    Thank you! 
  8. Like
    guidol reacted to Muhammad Rizqi E in orange pi zero plus2 H5 - HDMI - audio   
    yea, I had that issues too, my audio is not working even tried both HDMI and 3.5mm port.
    but I found out the solution that my sound is working using USB sound card. give it a try!
  9. Like
    guidol reacted to Luca Bertoncello in Reboot loop with cloned SD-card   
    Hi again!
     
    Problem solved!
    I connected the SD card on my PC and tried to run fsck, but it bleats something about wrong partition size.
    After a resize2fs fsck worked without any problem.
    Now the BPI bootet with the new SD card.
     
    Hope this help someone other!
    Luca
  10. Like
    guidol reacted to James Kingdon in H6 boards: Orange Pi One Plus, Orange Pi 3 Plus and Pine H64   
    My OPi one+ arrived. I burned the ubuntu image with etcher and it worked fine. I had to manually resize the fs but you expect a few rough edges with a new board.
     
    The bare board runs on the hot side, idling at a reported (but unconfirmed) 48C. Benchmarks quickly push it into throttling at 70C, but even so it is faster (just) than any of my other 4 core boards. I'll add a heatsink and fan and see if I can get the temps under control. If so, and if the board remains reliable it seems like excellent value for money. The H6 looks very promising.
  11. Like
    guidol reacted to Igor in Debian Builds for Orange Pi Win in the pipeline?   
    Ubuntu is Debian based, but the main difference is packages selection and their versions. Since we also define the package base, most of the packages are the same but they are certainly not the same version. This means certain application might not work out of the box and you need to solve dependencies on your own. This can be simple or a true nightmare. In this case, it's better to start with a proper base, whether Ubuntu or Debian. One good example is OMV - it does not work at all on Ubuntu - at least not out of the box. Stable version requires Debian Jessie, while current development is based on Stretch. For a board, which might be used as OMV (Helios4), we provide both, Jessie and Stretch and it's up to the user to decide which OMV version he will go for.
     
    In the x86 world, a change between releases/distribution is usually also on a kernel branch, while here we don't have this luxury. We have to use what is available and since there is no better working kernel than 3.10.y for this board we simply can't provide Stretch. We could Jessie ... but since we provide a simple and easy to use build tools, this is not that urgent either.
  12. Like
    guidol reacted to Jota79 in Orange Pi Zero Plus / H5 Chip   
    uooohhhh!!!!!   What a tiny "big" CPD!!!!!  ;-) Thank you very much, guidol. It is a very good reference for me.  Now, I have moved my orange pi zero plus H5 to a very  open-space ( it was inside a very closed furniture before.... ). I have moved it behind my plasma TV ;-).  And now, almost idle, temperature is in normal values ( with 21C room temperature ):
     
    root@zeus:~# armbianmonitor -m
    Stop monitoring using [ctrl]-[c]
    Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
    22:02:28:  816MHz  0.36  10%   1%   1%   3%   3%   0% 47.2°C  0/2
    22:02:33:  816MHz  0.33   4%   1%   2%   0%   0%   0% 44.4°C  0/2
    22:02:38:  816MHz  0.31   2%   1%   1%   0%   0%   0% 45.0°C  0/2
    22:02:43:  816MHz  0.28   2%   1%   1%   0%   0%   0% 42.2°C  0/2
    22:02:49:  816MHz  0.34   2%   0%   1%   0%   0%   0% 44.3°C  0/2
    22:02:54:  816MHz  0.31   3%   1%   2%   0%   0%   0% 45.3°C  0/2
    22:02:59:  816MHz  0.29   2%   1%   1%   0%   0%   0% 46.2°C  0/2
    22:03:04:  816MHz  0.34   2%   0%   1%   0%   0%   0% 43.0°C  0/2
    22:03:09:  816MHz  0.32   6%   1%   5%   0%   0%   0% 47.2°C  0/2
    22:03:14:  816MHz  0.29   2%   1%   1%   0%   0%   0% 44.5°C  0/2
    22:03:19:  816MHz  0.27   3%   1%   1%   0%   0%   0% 43.9°C  0/2
    22:03:24:  816MHz  0.25   3%   1%   1%   0%   0%   0% 45.4°C  0/2
    22:03:29:  816MHz  0.23   2%   1%   1%   0%   0%   0% 44.9°C  0/2
    22:03:34:  816MHz  0.21   5%   1%   3%   0%   0%   0% 45.4°C  0/2
    Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
    22:03:39:  816MHz  0.19   2%   1%   1%   0%   0%   0% 44.2°C  0/2
    22:03:44:  816MHz  0.17   2%   1%   1%   0%   0%   0% 44.6°C  0/2
    22:03:50:  816MHz  0.16   3%   1%   1%   0%   0%   0% 44.3°C  0/2
     
    I use my OP Zero for NAS Server ( samba/nfs ) and for p2p downloads with mldonkey.
     
    You can see my brico-project with an old celeron heatsink ( I am very worried with temperatures, perhaps I am a little friki... ):
     



  13. Like
    guidol reacted to Igor in Problems with 5.38 update   
    Replacing bootloader on your eMMC
     
    Boot from SD card.
    mkdir tmp cd tmp # replace this URL with the one for your board! This is for Orange pi plus 2e wget http://apt.armbian.com/pool/main/l/linux-u-boot-orangepiplus2e-default/linux-u-boot-orangepiplus2e_5.39_armhf.deb dpkg -x *.deb .  root_uuid=$(sed -e 's/^.*root=//' -e 's/ .*$//' < /proc/cmdline) root_partition_device=$(blkid | tr -d '":' | grep ${root_uuid} | awk '{print $1}' | tr -d '"/dev') emmc="/dev/"$(cat /proc/partitions | grep -v ${root_partition::-2} | grep mmcblk | awk '{print $4}' | head -1) # adjust the path accordingly to your board - downloaded file dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$emmc bs=1024 seek=8 status=noxfer If you want to flash your SD card on external SD card reader:
    sdcard=/dev/sda # make sure this is SD card and not your hard drive!! dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$sdcard bs=1024 seek=8 status=noxfer  
  14. Like
    guidol got a reaction from chwe in Problems with 5.38 update   
    I think as OPi+ he means the https://www.armbian.com/orange-pi-plus/
    The only "pi" with eMMC at my side is the NPi Neo Core2, but also with mainline (image of the NPi Neo Plus2 is working here with eMMC-support, but Iam running this from uSD).
     
    My OPi One is using legacy kernel (as Pi-Hole Server) but hasnt a eMMC.
     
     
  15. Like
    guidol got a reaction from Igor in Can you install Armbian to NanoPi Neo Core eMMC?   
    I dont think you could name it Nano pi Neo2 / Core, but you could name
    Nano Pi Neo Air     -> Nano Pi Neo Core/Air (H3)
    Nano Pi Neo Plus2 -> Nano Pi Neo Core2/Plus2 (H5)
    because
    Nano Pi Neo Core   is a Nano Pi Neo  (H3)  with eMMC = like a NanoPi Neo Air without BT/WiFi  and
    Nano Pi Neo Core2 is a Nano Pi Neo2 (H5) with eMMC = like a NanoPi Neo Plus2 without BT/WiFi
     
    Nano Pi Neo (H3) (without extension) and Neo2 (H5) (without extension) are without eMMC/BT/WiFi
     
    PS: I didnt got a SSD on the Core2 - so armbian could read the size - I think
  16. Like
    guidol reacted to Igor in BPi M2 Berry with BPi M2 Ultra image   
    Great job that you tried to do this.  As you can see there are still a lot of obvious problems and mainline is not yet useful on this board. Not even for simple cases since its lack of network support. Wens made progress on this, so you can try even more complex job by adding few of those patches to userpatches/kernel/sunxi-next and recompile the kernel. Monitor debug/patching, adjust patches if necessary ... Patch is downloaded from Github by adding .patch to the commit URL, for example:
    https://github.com/wens/linux/commit/48f1bef6c0b43defca07edd4d6e1962f272fe9d6.patch Have fun!
  17. Like
    guidol reacted to Igor in apt upgrade   
    chmod -x /etc/cron.d/armbian-updates should fix this.
  18. Like
    guidol reacted to DoubleHP in OrangePi Zero, mainline kernel, SPI LCD + touchscreen   
    In the end, what worked for me:
     
    0: my system: "ARMBIAN 5.35 user-built Debian GNU/Linux 8 (jessie) 4.13.16-sunxi" (called next)
    1: I am not going to try using the touch layer.
    2: wire things as described (with LED directly on 3.3V)
    3: aptitude install linux-headers-next-sunxi
    4: copy the content of "Configuration for the first spi bus" from initial post, except last line about EOF, into /root/myili9431.dts
    5: armbian-add-overlay myili9431.dts
    6: edit /boot/armbianEnv.txt and edit this line (some parts may be useless or overkill) overlays=usbhost2 usbhost3 spi-spidev spidev myili9431 (this appeared to be useless)
    7: reboot
    8: modprobe fbtft_device custom name=fb_ili9341 gpios=dc:3,reset:0,led:6 speed=16000000 busnum=1
    ... and immediately the LCD turned from all white, into classic console (black background with prompt at the top)
     
    Here is my dmesg:
     
    [ 166.951033] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 166.962129] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 166.967576] fbtft_device: GPIOS used by 'fb_ili9341': [ 166.967602] fbtft_device: 'dc' = GPIO3 [ 166.967627] fbtft_device: 'reset' = GPIO0 [ 166.967649] fbtft_device: 'led' = GPIO6 [ 166.967703] spi spi1.0: fb_ili9341 spi1.0 16000kHz 8 bits mode=0x00 [ 166.983929] fb_ili9341: module is from the staging directory, the quality is unknown, you have been warned. [ 167.341354] Console: switching to colour frame buffer device 30x40 [ 167.344793] graphics fb0: fb_ili9341 frame buffer, 240x320, 150 KiB video memory, 16 KiB buffer memory, fps=20, spi1.0 at 16 MHz https://kaspars.net/blog/linux/spi-display-orange-pi-zero mentions rotate=90 ... could be usefull for someone
     
    9: xinit worked immediately
  19. Like
    guidol reacted to adrb in OrangePi Zero, mainline kernel, SPI LCD + touchscreen   
    It's simple guide, presenting how to setup LCD (ili9431) with integrated touchscreen (tsc2046) on mainline kernel (4.11). It may be not fully "armbian way", since I'm pretty new in armbian
     
    In case that somebody is interested, I recently bought couple those displays from here
     
    Few basic informations:
     
    1. OrangePiZero has two SPI buses. First one is usually occupied by build in memory. So we can only use bus1
    2. tsc2046 chip is fully compatible with ads7846, and we have drivers for it since years now
    3. Maximum clock frequency for ads7846 is 3.25Mhz, but don't expect that it will work with that.  Reasonable value is something beetween 0.5-2Mhz. Lower frequency, if you observing misbehavior.
    4. Probably most important information  ili9431 and tsc2046 poorly cooperate on shared bus. I don't know exactly why, because I don't have access to logic analyzer,  but it's proven fact (at least on my equipment). You have to lower bus frequency to 2MHz (highest common value), and even then it work very unstable.  My educated guess is that, missed interrupt from touchscreen (when SPI is busy with sending data to LCD) makes it stop making further attempts to communicate. Or maybe there is some incompatibility on electrical level, I really don't know.
    5. My electrical setup (keep in mind it's 3.3V)
     
    OPIZ - LCD (ili9431)
    PA13 - CS
    PA14 - SCK
    PA16 - SDO
    PA15 - SDI
    PA03 - DC
    PA00 - RESET
    PA06 - controls transistor which is driving current to LCD pin. You may also connect LCD pin to VCC, and leave PA06 floating.
     
    And here is part for touchscreen. We are going to use emulated spi bus with bitbang. At this point bitbang isn't compiled in armbian kernel - we will take care of this later.
     
    OPIZ - LCD (tsc2046)
    PA10 - T_CS
    PA18 - T_IRQ
    PA19 - T_CLK
    PA11 - T_DIN
    PA12 - T_DO
     
    Configuration for the first spi bus:
     
    Configuration for touchscreen driver:
     
    Compile and add those DTS with "armbian-add-overlay" command.
    Next, download armbian sources and cross compile kernel - without any modifications, just to make sure that everything is compiling without issues:
    # mkdir armbian # cd armbian # git clone https://github.com/armbian/build.git # git clone https://github.com/igorpecovnik/lib # cp lib/compile.sh . # ./compile.sh BRANCH=dev BOARD=orangepizero KERNEL_ONLY=yes PROGRESS_DISPLAY=plain RELEASE=jessie Enable required modules :
    echo "CONFIG_SPI_BITBANG=m" >> lib/config/kernel/linux-sun8i-dev.config echo "CONFIG_SPI_GPIO=m" >> lib/config/kernel/linux-sun8i-dev.config ... and recompile kernel, then install deb packages from output directory. You may also copy drivers, it may be faster for testing but it's not advised for "serious" deployment.
    Loading modules at startup:
    # cat > /etc/modprobe.d/fb_ili9341.conf << _EOF_ options fbtft_device custom name=fb_ili9341 gpios=dc:3,reset:0,led:6 speed=16000000 busnum=1 _EOF_ # echo fbtft_device >> /etc/modules # echo ads7846 >> /etc/modules If you connected LED pin to VCC, then you should omit that ",led:6" in configuration above. 
     
    I hope that this will help anyone who want to connect LCD display and build simple touchscreen based Orange Pi Zero terminal

     
     
  20. Like
    guidol reacted to raffaele in SwiftBoard-Data Rockchip NAS board   
    Hi there,
    I've been contacted by KoVu Inc. regarding their RK3328 "SwiftBoard", which should be a great candidate for NAS applications. Any thoughts?
     
    https://www.board-db.org/news/2018/01/08/kovu-swiftboard-data-nas-single-board-computer-sata-hdmi-2-0-emmc-gbe-android-armbian-openmediavault/
     
    P.S.: I should receive a sample of this board in the next weeks, if you're interested in further updates.
     
    Cheers!
  21. Like
    guidol got a reaction from Christian_ in ESPTerm - a nice Idea fore the Debug-Port   
    Yesterday I came across the following - for me - fine project (Demo-Page):
    ESPTERM Release 2.3.0 Cricket
    https://espterm.github.io/term.html
     
    GitHub-Page:
    https://github.com/espterm/espterm-firmware
     
    Downloads:
    https://github.com/espterm/espterm-firmware/releases
     
    Its a VT100-Webpage-Terminal on a ESP8266-Microcontroller which opens a Accesspoint.
    You could connect via this VT100-Webpage-Terminal to the TTL-Port of the ESP8266.
     
    TTL-Connection is done (like allways in TTL-Connections) with RX,TX and GND
     
    I connected my Orange Pi R1 via TTL and 115200 Baud and could "work" at a (max.) Terminal-Size of 80x25
    (80x25 is max. in the downloadable binary - if you do compile by yourself mor is possible.... 132x50 would be fine )
     
    So if you have a misconfigured Network-Connection (missed the /24 in the IP of the server in nmtui) and you dont want to use a USB-serial-Dongle because every Dongle wats its own driver  - here a second solution


  22. Like
    guidol reacted to PaddleStroke in Custom H3 prototypes, not starting   
    That was the trick! Added a pull up resistor to AP-RESET# it was enought. The boards are booting now. Starting boot at least  
    I'll have to modify few things I guess
  23. Like
    guidol got a reaction from manuti in No boot text by HDMI on Orange pi lite   
    You could try to use the info from the following thread:
    - edit  /boot/armbianEnv.txt
    - change "console=both" to console=display
    - save
    - reboot
     
  24. Like
    guidol reacted to mz-fuzzy in Pine64+ & Pine64so - uboot - no ethernet   
    cool mechanism.
     
    After patching the code, mainline pine64+ seems to be working for me including ethernet!
     
    Is it ok to submit that patch as a pull request to armbian?
     
    Thanks!
    -bob-
  25. Like
    guidol reacted to Igor in Pine64+ & Pine64so - uboot - no ethernet   
    Yes. The network is broken due to changes in the upstream kernel driver code. I managed to port this fix to H3 & H5 from 4.15.y while AFAIK A64 is still broken. Perhaps @montjoie know more about this?
×
×
  • Create New...