Search the Community

Showing results for tags 'research'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 67 results

  1. Recently, a new SBC, the Rock Pi S by Radxa, was launched. Here's it's wiki page: It's a 4 core A35 design. I'm debating getting one, but I can't find any information anywhere as to whether or not it's supported on Linux, or Armbian. Of course, if it's not listed in the download section it's not supported, but there's a difference between, "I need to add 100 lines of code and it will work." to "Geez, I need to redesign most of the Linux kernel after pulling my hair out." I did search the sunxi wiki and the local armbian wiki without success. Anyone know anything? Thanks!
  2. I have been playing around the Rock Pi S from radxa, and am stumbling at enabling the I2S output using a device tree overlay. (Building using current Armbain that uses @piter75's kernel branch) As per the data sheet and pinout, `i2s_8ch_0` should be broken out to the GPIO, but I don't seem to be getting far enabling it via the device tree. Any inputs? This is what I am playing around with atm, but `dmesg` doesn't show anything helpful atm, and no "I2S-Card" device turns up. Tried disabling the inbuilt audio codec ( connected to `i2s_8ch_2`), but still no dice. The closest example I could find was from `rk3308-ai-va-v10.dts`, that similarly enables the `i2s_8ch_0`, but am unable to mimic it. /dts-v1/; /plugin/; / { model = "Radxa ROCK Pi S"; compatible = "radxa,rockpis-rk3308", "rockchip,rk3308"; fragment@0 { target-path = "/"; __overlay__ { pcm5102a: pcm5102a { #sound-dai-cells = <0>; compatible = "ti,pcm5102a"; pcm510x,format = "i2s"; }; }; }; fragment@1 { target = <&i2s_8ch_0>; __overlay__ { status = "okay"; #sound-dai-cells = <0>; sound-dai = <&pcm5102a>; }; }; fragment@2 { target-path = "/"; __overlay__ { sound_i2s { compatible = "simple-audio-card"; simple-audio-card,name = "I2S-Card"; simple-audio-card,mclk-fs = <256>; simple-audio-card,format = "i2s"; status = "okay"; simple-audio-card,dai-link { format = "i2s"; codec { sound-dai = <&pcm5102a>; }; cpu { sound-dai = <&i2s_8ch_0>; }; }; }; }; }; };
  3. It says, that adding an usb ar9271 wifi card to a pinephone is not feasible because the wifi card uses to much power. How much power is acceptable for an usb ar9271 wifi card to use? I do not have extended equipment. I made the following arrangement. One pc. Connected an usb power meter. Connected an usb ar9271 wifi card to the usb power meter. Started an youtube video. After that downloaded an ubuntu image. Distance to router about 10yards. One brick wall. Usb power meter displayed about 5.1v and 0.16a. Is that much? To much to use on a pinephone? The modem on the pinephone has an usb connection. About the modem, why is the power consumption not a problem? I know connecting an usb ar9271 wifi card to a samsung i9100 replicant phone is working terrible. Infrequent disconnects, battery power level has to be above 90%. Thanks.
  4. Tanix TX6 is H6 based Android TV Box and it can boot from SD cards prepared with PhoenixCard. It should be possible to make it work with Armbian too, right? I tried a recent Lite2 image, it didn't work, but it also didn't boot main Android, which means SD boot takes priority. I don't think it's a normal behavior for other Android TV boxes, but maybe it is for those with H6 boards.
  5. Hi all. I've made a new video where I test all storage devices for the NanoPi M4. 8GB, 16GB and 32GB eMMC modules, NVMe drive, sd-card and SSD over USB3. Here's the video. Here's my gathered data. Storage speeds -------------- 8GB eMMC module read : 160 MB/s write : 11 MB/s 16GB eMMC module read : 175 MB/s write : 50 MB/s 32GB eMMC module read : 173 MB/s write : 111.6 MB/s 256GB NVMe read : 697.7 MB/s write : 401 MB/s (630MB/s for 2.5GB, then 300 MB/s) M4 sd-card read : 70 MB/s write : 20 MB/s M4 swap read : 1.9GB/s 0.01 msec access time Greetings, NicoD
  6. Hello, following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian. For those which are interested, at the moment it is available on github -> here <- It is still in a heavy work in progress status, but all the fundamentals are in place. Most of the love has been poured into supporting and bringing up the legacy rockchip 4.4 kernel, but in the near future the goal is to fully support the mainline kernel. What works now on legacy kernel: Two rk3229 tv box board (the signature on the PCB says R329Q and Chiptrip xt-mx4vr-v01), as a proof of concept Mainline u-boot OPTEE provided as Trusted Execution Environment All 4 cores are working Ethernet Serial UART (configured at 1.5 megabits/s, but will be switched back to 115200 bps soon) Thermals and frequency scaling OTG USB 2.0 port EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration (via RKMPP) NAND is available (but not as boot device due to mailine u-boot missing the rockchip NAND driver) SSV6051 wifi over SDIO (crappy driver, blacklist ssv6051 driver in /etc/modprobe.d/blacklist.conf in case your kernel crashes) Whatever is supported for other rockchip devices in legacy kernel, including possible graphics acceleration support Building: You can build your own image follow the common steps to build armbian for other tv boxes devices (ie: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "r329q" or "xt-mx4vr-v01" from the list). In case your board is not listed here, I suggest you to try with xt-mx4vr-v01 board, which has more chances to boot. Prebuilt images: If you don't want to build Armbian yourself, there are some prebuilt images already available: Armbian 19.11.5 Ubuntu Bionic Desktop 18.04 - kernel 4.4.189 Armbian 19.11.5 Debian Buster Server Minimal - kernel 4.4.189 As long as this is a work in progress, I suggest you to try building the image yourself for your board because every prebuilt image will become obsolete very soon. Quick installation instructions: In order to run armbian from an SD card you need to put the device in maskrom mode. To do so, follow the instructions below. Flash the image on the sdcard, plug it in and plug the power cord Wait some seconds, the led should start blinking soon. HDMI output during boot is not available yet, so just wait for the kernel log and login prompt; the first time the boot process will take a couple of minutes or so As usual, armbian default credentials are user: root password: 1234 Putting the device in maskrom mode: It is essential that the device is put in maskrom mode to let it boot from the external sd card. In order to do so, you need to erase the internal eMMC/NAND flash memory. If you don't want to erase the existing firmware, at the moment you can't proceed. You obviously need to do this step only once. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with vendor ID 2207 run ./rkdeveloptool -ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on Note: rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash corrupts or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Just google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver. I will continue to work on this project and refine both the legacy and mainline kernel and when the support will be in the same ballpark as other targets I will ask @Igor if it is a good idea to merge it into the main armbian repository. Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here)
  7. the main proposal of this research is to enable cached apt archives for docker build. first apt cache can be saved by a docker volume, but due to `${SDCARD}/var/cache/apt/archives` is not a constant, then we can't use `-v=apt-cache:${SDCARD}/var/cache/apt/archives` to enable it. so I use `-v=apt-cache:/root/.apt` as a tmp place for apt cache, when need `apt install` in `${SDCARD}`, use `mount -o bind /root/.apt ${SDCARD}/var/cache/apt/archives` and after install finishes, `umount ${SDCARD}/var/cache/apt/archives` this looks perfect, but after I check /root/.apt, everything is gone. I double checked whether *.deb are saved to /root/.apt, I can find them before `umount`, or even use apt-cache in another container: `docker run --privileged --rm -v=apt-cache:/test -it ubuntu:18.04 bash` I can find debs in /test folder, and gone after `umount` I really don't know why.
  8. As WiringPi was never meant to support other boards nor does the author like to support other boards and it is officially depreciated now ( I want to ask why not put some efforts into libmraa and put it into the Armbian repository. I have already a fork which fixes Rock Pi 4 on recent mainline 5.3 kernels with updated debian build scripts here:, so debian packages could be simple built using dpgk-buildpackage. Why I think it is a good idea to supply libmraa with the Armbian repository Supporting multiple boards is a desired goal of the project Supporting a board is really easy, for Rock Pi for example this is just the files src/arm/rockpi4.c include/arm/rockpi4.h and an entry in src/arm/arm.c, that's it Instead of multiple forks of wiringPi and different sources of different versions (or even different gpio implementations) just have one common implementation for all boards with wiringPi you need additional bridges if you want to code in other languages like Java or Python for example, with MRAA you have out of the box bindings for Python, Java, Javascript, C/C++ and NodeJS support What do you think? @Igor
  9. Just curious, it has exists as patches for years, is there anything prevent it from being merged into mainline? This chip is quite widely used in TV boxes.
  10. Free software is software you may use, share, modify and redistribute. Replicant has decided to investigate if they can port a replicant version to the phone. Replicant has said, they know of no phone better about free software. All modems on the market require non free software. Same about the modem in the pinephone. A downside of the pinephone is the wifi card, 8723cs, because it requires non free firmware software. On pinephone's irc I was told, they went for the 8723cs because pinephone could find no viable free software supported sdio wifi card. Is it the case, there is no free software supported sdio wifi card for sale? On pinephone's irc the ESP8089, ESP8266, ESP32 chips were mentioned. Are they computers like the ardinos? If they are, I expect they are not usable in a phone, because of power consumption. The chips were mentioned because it should not be inherently impossible to write free software drivers and firmware for them. Do you know about forums for such matters? Thanks.
  11. When building a kernel the device driver configuration asks which rtc should a system use for NTP and startup synchronisation . By default this is rtc0. The question is: In case there are more hardware RTCs in one embedded system ( in my case onboard RK808 and Dallas DS1307 over I2C), which one would be numbered as rtc0? Threre are several RTC device drivers available and checked by default, some marked as M and other as '*' , supposing 'module' or 'driver' respectively. Now if I have two hardware RTCs, I presume they should load as rtc0 and rtc1, but which part does numbering? I can't know this 'a priori' , I would like to use DS1307 for synchronisation.
  12. What script is used in Armbian to build ram init image uInitrd?
  13. mainline kernel support, libreelec is allready working. is there any chance on getting amrbian ported here, i allready did some test and made it boot, but network does not get an ip adress link with ethtool show up and 1 gbit. same for the eachlink device
  14. I'm creating this topic to track progress with support for EachLink H6 support. So far with patches in lines 127..202 in List of patches with patch files I was able to get: working: -boot with mainline 5.4 kernel -HDMI video (with correct DDC) -HDMI audio -Ethernet -GPU mali t720 -USB2/USB3 ports -CPU temp reading -DVFS (CPU freq scalling) -internal IR sensor (MCE remote works nicely) not tested: WiFi Blutooth This box might be cheap H6 box to become nice mediaplayer as current panfrost started to support really well t720 (I've got fully working GLES UI, playback with OpenG & yv12 renderers + GLSL based shader deinterlacers: OneFileld. LinearBlend & Kernel on mythtv). Only issue I had at this moment is insufficient cooling with stock cooler - so if You launch compute intensive tasks and Yours OPP has 1.8GHz cpu clock entries - after some time bow is self-reseting due overheated CPU. Solution seems to be: -lower max CPU clock in OPP tables to 1.4GHz or -add better cooler...
  15. Found an old (2015) Ugoos UT3+ / UT3 Plus with an rk3288 - the neat thing about this board is it has HDMI-IN ! Also has PIP Specs: I'm was eventually able to successfully screen capture @ 1920 x 1080 ~29 fps using the Android 5.1.1 firmware V3.0.7 for UT3+!cQpl0ICS!8EgHddI3_PXQsSe-TSrkHfxdHCmkbckNWBYuLhfuA7w The firmware crashes frequently and the painful part is the IR remote is required to start recording.. so I'll be porting gentoo / armbian to this device to turn this paper weight into a linux friendly screen capture device. It maybe also worthwhile to document the process and create an armbian porting guide. Aside, for those interested, its worth to mention the LKV373A HDMI / ethernet sender is a potential $30 HDMI screen capture alternate.
  16. Today I noticed something strange about packages : armbian-config and armbian-firmware (bionic all) Repository version becomes 19.11.3 (via apt update) but self built packages created via kernel build script are version 5.98 Other kernel packages are ok, version 4.19.85 What about this?
  17. I dont know if it real (but for me it feels like) that updating packaged (fetching/reading the list) takes much longer than on stretch or a bionic version. (also on buster creating locales via armbian-config - I use de,gb and us - does take longer to generate) While do a apt update I did see that buster do get package/content lists will come for armhf and aarm64 - is that OK or to much? Get:8 buster/main arm64 Packages [7728 kB] Get:9 buster/main armhf Packages [69.6 kB] Get:10 buster/main arm64 Packages [67.4 kB] Get:11 buster/main armhf Contents (deb) [2728 kB] Get:12 buster/main armhf Packages [7690 kB] Get:13 buster/main armhf Contents (deb) [35.2 MB] Get:14 buster/main arm64 Contents (deb) [2742 kB] Get:15 buster/buster-utils arm64 Packages [3459 B] Get:16 buster/buster-utils armhf Packages [3749 B] Get:17 buster/buster-utils arm64 Contents (deb) [572 B] Get:18 buster/buster-utils armhf Contents (deb) [572 B] Get:19 buster/buster-desktop arm64 Packages [403 B] Get:20 buster/buster-desktop armhf Packages [1531 B] Get:21 buster/buster-desktop arm64 Contents (deb) [60 B] Get:22 buster/buster-desktop armhf Contents (deb) [213 B] Get:23 buster/main arm64 Contents (deb) [35.3 MB]
  18. I do not wish to make this too political. But I do often get the question if we can trust all the images from board makers security wise. I personally try many images. I only use Hardkernel images on my Odroids. On my NVIDIA Jetson Nano I of course use the image from NVIDIA since it's got all the goodies. But on all other boards I use Armbian. Either official Armbian, or Balbes Armbian. I wanted to hear your thought about this.
  19. Hi every body I work with armbian on OPI & BPI fine but I'm looking for an improvment. First I install OS on SD, etc... but with limitations of R/W nb & sensibility if power disappears. I set a boot os SD and after switch on SSD connected on USB by moving directory and after discover a scipt whic do all automatically (thank's armbian). But customer calls me server don't restarts. I go on site (waste of time) burn a new SD etc.... and install a little eaton ups to prevent new failure. The server hosts a little bootstrap webserver, specific application server, cron scripts and nothing else. I need WIFI AP / Eth Gb & SSD and nothing else. I 'm searching for a mother board which boots directly on SSD (skip SD) with function above. Can you help me to choose ? Very thank's Best regards Fredéric
  20. BPi M1 A20 with kernel 5.3.7/5.3.8 there are some problems using the onboard-analog-audio mpg123/espeak is freezing and cant write to the analog-audio via alsa. A USB-Audio-dongle does work fine. (also EOS devices like PCDuino A10 and Lime A10 have audio sync-problems with kernel 5.3 (but do work) - but its "OK" they are EOS) The BPi M1 A20 has no problem with the analog-codec while using kernel 4.19.81-sunxi analog-codec seems to be always active, because if enabled as overlay or not the analog-soundcard s shown: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun4icodec [sun4i-codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Subdevices: 0/1 Subdevice #0: subdevice #0
  21. One month ago I got on my OPi Zero Plus2 H5 only up to 816Mhz with armbian. In the past I got on this device up to 1.1GHz (1080000 cpufreq) with older armbian builds. @5kft Told me thats because frequencys greater than 816Mhz require 1.2v and the OPi Zero Plus2 H5 isnt/couldnt switch(ing) and would only run at 1.1v. So it seems the cpu-table is now more conservative than before. Yesterday I did see the same behaviour and my "older" non-LTS NanoPi Neo2 (H5 also). Because in September I edited the cpu-table less conservative for the OPi Zero Plus2 H5 I did test this also on the non-LTS NanoPi Neo2 and it worked like on the OPi Zero Plus2 H5
  22. Hi, I'm looking for a tiny board with eth and wireless. My first choice is Orange Pi Zero but I'm worried about thermal issue. Any cheap alternative?
  23. Hi there, I have a RockPi 4b running Arabian with Ubuntu bionic. I mainly use the board to contact it online over ssh/vnc/rdp to work in spyder and texmaker. Quite often the connection is slow however. Therefore I am thinking of changing the system such that i can just bring it on the road and connect it using a local network with the usbc cable outlet of the iPad and a USB port on the rockpi. The reason i would like to connect over a cable is speed and not having to use the WiFi so that both devices can still easily connect to a WiFi network for internet access. I have found many solutions where iPads are connected to raspberry pi’s. These solutions all have various forms, could anyone here please suggest me what the ‘ best’ solution would be in terms of ease of configuration and stability? What i’ ve found so far: - avahi - bonjour - connection related to nmap Are all these solutions even possible on a Arabian system ? And if the procedure is different, can anyone please help me het started ? Furthermore, if anyone of you is willing to help me think out the steps to configure the system that would be awesome (like really awesome). I’m only a Linux hobbyist so I’m still unable to find out the finesse between these programs. Thank you very much in advance. Johan
  24. Which one is better from below two options >> (1) Western Digital WD Blue 250 GB M.2 2280 SATA Internal Solid State Drive (WDS250G2B0B) OR (2) Samsung 860 EVO Series 250GB M.2 SATA Internal Solid State Drive (MZ-N6E250BW) Please suggest as per your experiences...
  25. This was a bit of a buzz back in late Dec 2018, and things got kind of quiet after that... Rumour was that the SoC was the SocioNext SC2A11, which is a Japanese chipset (and from experience, Japanese chip vendors are very particular about who they work with)...