araczkowski

Members
  • Content count

    16
  • Joined

  • Last visited


Reputation Activity

  1. Like
    araczkowski reacted to mantabernd in AP6212a - Bluetooth Audio Streaming Timeouts in audio bus   
    Thank you for your fast reply.
     
    I kinda got it working. I thought it's enough to set the uart speed once but you need to make it on every boot. So I wrote  startscript what sets the uart speed to 1500000 bit/s and it's working without timeouts. 
    It's not my goal yet because the AP6212a datasheet says that it's possible to work with 3000000 bit/s. Unfortunately I'm not able to set this speed.
     
     Furthermore Bluteooth audio streaming is not running very stable. I know it from Raspberry Pi with 4.x kernel and it was really easy and smooth. It seems that it's a problem connected to 3.4 kernel.
     
    Can you give me any info about how to activate blutooth on 4.x kernel? I already tried to make it work but with 4.x mainline release you don't have this fex file to activate the hardware modules. I got stucked with building a new device tree.  Maybe you can give me some more info about it?
     
    Do you know when a 4.x kernel will be officially available for Nano Pi Neo Air?
     
    Thanks a lot
    Regards
    Bernhard
  2. Like
    araczkowski reacted to Rob Tìgeir in Chromium browser fails to launch   
    You can download the older deb
     
    http://launchpadlibrarian.net/319181475/chromium-browser_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb
     
    But it also requires the exact chromium-codecs-ffmpeg-extra package
     
    I did somehting along the lines of this...
    sudo apt remove chromium-browser mkdir tempforinstall cd tempforinstall wget http://launchpadlibrarian.net/319181475/chromium-browser_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb wget http://launchpadlibrarian.net/319181477/chromium-codecs-ffmpeg-extra_58.0.3029.110-0ubuntu0.14.04.1176_armhf.deb sudo dpkg -i *.deb sudo -s echo chromium-browser hold | dpkg --set-selections This removes the 59 version, downloads 58 versions, installs them and then locks the browser so it doesn't get upgraded. I'm sure someone could do this in less lines but it worked for me.
     
    I don't get the Lock option in synaptic for some reason.
     
  3. Like
    araczkowski reacted to wimsop in Chromium browser fails to launch   
    Yes, I actually reported the problem only after doing a fresh install on another card first. So vanilla Armbian_5.30_Orangepipc_Ubuntu_xenial_default_3.4.113_desktop.img with single updated package as stated above.
     
    Sure thing. What logs do you need, specifically? Nothing in syslog or systemd journal though. I'm not aware of any logging done by chromium, but I'm sure you can point me in the right direction there.
    For the actual error message, see above. Card is a 16GB Sandisk Ultra UHC-I card I took from another SBC. PSU is the old Xunlong 3A one.
     
    How so? Apt-get tells me
    E: Version '58.0.3029.110-0ubuntu0.16.04.1281' for 'chromium-browser' was not found
  4. Like
    araczkowski reacted to AndrewK in S/PDIF output on NanoPI M1   
    Here is a short instruction how to enable S/PDIF digital audio output on NanoPI M1 board running Debian Jessie with legacy kernel.  This instruction can be applied to other H3 based boards but connect S/PDIF output hardware to GPIOA17 can be tricky (soldering miniature camera connector pins). Operations can be done over serial console or ssh.   Login as root Get a .fex file and open it in editor: bin2fex /boot/script.bin /tmp/script.fex nano /tmp/script.fex Search a csi0 (camera) section an disable it: [csi0] vip_used = 0 Search a S/PDIF section and enable it: [spdif0] spdif_used = 1 Get the name of the file pointed by the /boot/script.bin link and convert modified .fex to it: ls -la /boot/script.bin ----- /boot/script.bin -> bin/nanopim1.bin fex2bin /tmp/script.fex /boot/bin/nanopim1.bin Open /etc/modules to instruct Jessie to load S/PDIF modules at boot: nano /etc/modules Add module names near the end of file: sunxi_spdif  sunxi_spdma   sndspdif   sunxi_sndspdif Reboot system: sync reboot After reboot login as root again Get the list of ALSA devices available: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 []   Subdevices: 1/1   Subdevice #0: subdevice #0 card 1: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 []   Subdevices: 1/1   Subdevice #0: subdevice #0 card 2: sndspdif [sndspdif], device 0: SUNXI-SPDIF sndspdif-0 []   Subdevices: 0/1   Subdevice #0: subdevice #0  
    To connect board S/PDIF output to my favorite DAC i use an optical S/PDIF module soldered out from dead DVD player:
     

     
    There are 3 wires connected to board 40-pin connector: GND (pin 6), VDD_5V (pin 2) and SPDIF-OUT/GPIOA17 (pin 26)
     

     
    Module pinout can be found in datasheet http://www.mouser.com/catalog/specsheets/totx177(f,t).pdf
     
    Modules come in 2 types: 6-MBit (up to 24 bit / 96KHz) and 15-MBit (up to 24 bit / 192KHz). Most likely from DVD or SAT receiver You get the 6-MBit module. 15-MBit modules can be purchased at Digikey, etc.
     
    When listening to music, I faced with spontaneous fadings. This is due to some problem of the CPU speed switching. To this do not happen, I banned the clock frequency of 240 MHz in the /etc/default/cpufrequtils:
    MIN_SPEED=480000
  5. Like
    araczkowski reacted to tkaiser in Orange Pi Zero 2+ H3, start with USB OTG in dual mode   
    There's a serial console available on the Micro USB port just with every other device lacking Ethernet that's supported by Armbian. So connect the device to an USB3 port of a PC running Linux or a Mac (USB3 is important since these ports provide 900mA and not just 500mA) and then do something like this after waiting 60 seconds
    minicom -D /dev/cu.usb* -b 115200 screen /dev/cu.usb* 115200 And you're in (this was for OS X, on Linux the device name might look different and I've absolutely no clue at all how that works with Windows).
     
    TL;DR: The additional investment in Xunlong's $2 Expansion Dock is pretty smart when buying any of those Orange Pi Zeros.
  6. Like
    araczkowski got a reaction from Igor in OPI PC: Possible to directly upgrade from server to desktop version?   
    I'm writing this post from Orange Pi Zero 2+ H3 so it works
    I downloaded the desktop image from "other download options and archive"
    In my opinion the  Ubuntu desktop – legacy kernel can be added to the "Orange Pi Zero 2+ H3" download page
    During the installation I had only one problem with USB OTG - I will describe it in detail in separate thread.
    PS
    I'm traing to switch the device in my project from OPiPC+ to PPiZero2+H3(because of the bluetooth and small size) I will share the experiences.
    Thanks again @Igor the Armbian is awesome!

  7. Like
    araczkowski got a reaction from Igor in OPI PC: Possible to directly upgrade from server to desktop version?   
    I'm writing this post from Orange Pi Zero 2+ H3 so it works
    I downloaded the desktop image from "other download options and archive"
    In my opinion the  Ubuntu desktop – legacy kernel can be added to the "Orange Pi Zero 2+ H3" download page
    During the installation I had only one problem with USB OTG - I will describe it in detail in separate thread.
    PS
    I'm traing to switch the device in my project from OPiPC+ to PPiZero2+H3(because of the bluetooth and small size) I will share the experiences.
    Thanks again @Igor the Armbian is awesome!

  8. Like
    araczkowski reacted to Ford Prefect in microphone not working on Orange Pi Zero   
    Hi
    There seems to be a ground connection missing
    here is the schematic from OrangePI PC

  9. Like
    araczkowski reacted to zador.blood.stained in CAN BUS support orange pi zero   
    It will display as nightly but it still will not have required changes. And I checked the configuration, nightly images are not enabled for your board (Orange Pi Plus 2). Sorry.
  10. Like
    araczkowski reacted to tkaiser in Orange Pi Zero Plus 2 available   
    And I was wrong, the first take with adjusting the settings was already sufficient so no idea how I wasted my time a few days back then. Igor gave it a try and it worked flawlessly. Now I built an Armbian OMV image and can confirm: Wi-Fi just works (nmtui is all that's needed). According to Igor BT also works already.
     
    Seems official OS images will be available soon.
  11. Like
    araczkowski reacted to Igor in Orange Pi Zero Plus 2 H3 & H5   
    Yes, exactly this way.
     
    H5 is operational but still in development.  Get it if you plan to play with it deeply and join R&D, while go for H3 if you plan just to use it ... and perhaps do minor adjustments. We still wait for those boards to come here, than we need to make few minor adjustment, few tests, create an entry in conf+download page ... it's "just" a question of time.