Search the Community

Showing results for tags 'research'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues / peer to peer technical support
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

  1. As we know, the PCIe on H6 is buggy, which doesn't offer linear address, and Linux cannot support such kind of configuration. However, the Cortex-A53 cores used by H6 supports virtualization, which can be used to change the order of the address space. Recently, I tried to make use of virtualization to provide linear mapping of PCIe, and I succeed in making an Intel 6205 wireless card working. The hypervisor code is at https://github.com/Icenowy/aw-el2-barebone . It's intended to start before U-Boot, and located at 0x40010000. A U-Boot fork that is patched to load the hypervisor is at https://github.com/Icenowy/u-boot/tree/h6-load-hyp , and a kernel that utilizes the wrapped PCIe (and patched to reserve memory for the hypervisor) is at https://github.com/Icenowy/linux/tree/h6-pcie-wrapped . In order to let the hypervisor start before U-Boot, BL31 needs to be built with `PRELOADED_BL33_BASE=0x40010000` in make parameter -- this will change the EL2 entrypoint to the hypervisor. Mainline ATF from ARM works. Contributions to the hypervisor is welcomed. (In addition, abusing virtualization in such way will prevent us from using KVM. But I think more people will want PCIe instead of KVM, right?)
  2. @Igor Kernel enabled Bootsplash works great on the recent 20.08 on Orange Pi 4. However there is a delay of around 20 - 30 seconds before this Bootsplash comes up. Is is possible to enable bootsplash on u-boot also on this image? I built a custom image 20.08-trunk with option "Kernel enabled bootsplash' disabled however could not see u-boot bootspalsh on this image. -Rajesh
  3. Hi, A small discussion started here, but I would like to lift it to here. The question and tests should be. Are there alternatives to Etcher? A must was - standard writing verification. IIRC this was back in the days an option you had to set a 'tick' on Win32 DiskImager.. and so not an option. Before we change anything - proper testing and writing down the steps to achieve a great result is a must. Multiplatform, would be nice, but we can as well recommend 2 or 3 SDcard writing programs. Can you please help to write a table of available programs (you can do a table in the forum, but consider quantity of lines & rows first). And whether or not the software is an equivalent replacement for armbian? Please help us to collect here your knowledge and expericence Of course your recommendation should support the minimum mentioned above - otherwise it is not a recommendation but Spam Thank you in advance for your participation on this challenge
  4. Recently, a new SBC, the Rock Pi S by Radxa, was launched. Here's it's wiki page: https://wiki.radxa.com/RockpiS 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!
  5. These days i did install on some devices debian buster (via armbian-build-system generated). On the Orange Pi One this did work also fine with the cpu-temperature (showing via armbianmonitor -m) On a Orange Pi PC2 and a NanoPi K1 Plus this doesnt work. First I did think this is a problem of the dev-image with debian buster where /sys/devices/virtual/thermal/thermal_zone0/temp doesnt show an output via cat or more - but its filesize does show a 4096 bytes size (also on a working device - and also rights 444 = rrr for the file): -r--r--r-- 1 root root 4096 May 20 10:47 temp BUT NOW after a apt update & apt upgrade I also got this "problem" on a NanoPi Neo2 LTS with a stable debian stretch image: Welcome to ARMBIAN 5.85 stable Debian GNU/Linux 9 (stretch) 5.1.0-sunxi64 package bsp-kernel[5.86] u-boot[5.85] dtb[5.86] firmware[5.83] config[5.86] with armbianmonitor -m the stretch and buster devices does show the following error: Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU 11:14:59: 1008MHz 0.22 7% 4% 2% 0% 0% 0%/usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected and the devices with this error got these - for me - new error messages about thermal in the dmesg: [ 6.727971] OF: /thermal-zones/cpu-thermal: arguments longer than property [ 6.728007] OF: /thermal-zones/cpu-thermal: arguments longer than property armbianmonitor -u for the NanoPi Neo2 LTS: http://ix.io/1JNA root@npi-neo2-24(192.168.6.24):~# armbianmonitor -u System diagnosis information will now be uploaded to /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected http://ix.io/1JNA Please post the URL in the forum where you've been asked for.
  6. Hi all, sbc-bench is now on Github: https://github.com/ThomasKaiser/sbc-bench I'll link from the README there to this thread for further discussion about the tool and proper benchmark methodology.
  7. Finally I got my lcd (some of them) to work with armbian on mainline kernel (5.4) using device tree overlay. It should be working on 4.19 kernel too. I test mine on orange pi zero. The one I am able to get working is ili9341 and st7735 based lcd. I'll add more detail later but for now I'd like to get this out. edit 1 : Adding ssd1306 and nokia 5110 overlay to the repo device tree overlay
  8. After working with sysfs and libgpiod as cross platform solutions I was wondering if there was a faster way using /dev/mem or mmio? I know this gets more bare metal and SBC specific, but for some things you may want absolute speed. https://opensource.com/life/16/4/bulldog-gpio-library for instance claims 1 MHz GPIO writes in Java. However it only supports 3 SBCs as you can see from https://github.com/SilverThings/bulldog. Is there a more generic way to do this and not lose performance? Using my generated JNA wrappers for libgpiod I get about 2K writes per second. In Python I think it's about 70K using libgpiod Python bindings. I realize you may not always need 1 MHz GPIO writes, but it would be neat to offer this in a more generic way.
  9. Hello, I'm try to setup my OPiZero as mediaplyer, and I need to use it sometimes as WiFi Client - Managed mode and sometimes as WiFi AP - Master mode. Scenario 1 Work in "dual mode", I mean, when my wifi network within reach, then OPiZ start as "client", and connect to my preferred wifi network when wifi network not in range, it start as AP+DHCP (hostapd and dnsmasq) Scenario 2 Switched mode, Make any push button on gpio, and then make scripts "to do the job" .. disconnect from wifi, stop wpa_supplicant, run hostapd an dnsmasq. Has anybody something like "scenrio1" or "scenario2" .. ?? (or my ideas are totally bad ... )
  10. For the last few years I have been working on some hardware projects based on ARM SBCs. Every board I work with seems to have different kernel/overlay/GPIO/etc issues. So my question is - Which SBC, or chipset, has most complete and stable Armbian support? In other words if you had to pick a board to go into battle to run Armbian, without knowing any specific requirements, which SBC would it be?
  11. 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.
  12. I would like to know the content of u-boot-s905x-s912 and u-boot-s905x2-s922 at the boot dir. of armbian release . Is there a tool to de-compile these script to plain text ? Sorry if this question had been asked or answered . I didnot find any clues from searching at this forum. Thanks !
  13. The ARM kernel itself has already been compiled. How to compile a ARM kernel module on an VM amd64?
  14. Does anybody have a solution how to charge battery with more conservative voltage range? I'm using battery backup for my CubieTruck boards to survive power outages for several years. And as one of the batteries recently blew up (and also killed the backup HDD next to it) I try to find a way to charge the battery in a range that preserves health of it. When searching for a long-term-save voltage range of LiPo batteries you get something like: use only half of capacity, much below 4V, never deep charge, ... Default setting for the AXP209 charge controller is to charge to 4,2V, and emergency shutdown is at 2,9V. These ranges are much too broad and may damage the battery over the years. Deep discharge protection is quite easy, just use a script to regularly check current voltage and issue a shutdown when too low (no clue, why this is not already handled by the OS): if [ $(cat /sys/class/power_supply/axp20x-battery/status) = Discharging ]; then if [ $(cat /sys/class/power_supply/axp20x-battery/voltage_now) -lt 3200000 ]; then # prevent undervoltage shutdown -h fi fi But target voltage for the charge controller is not that easy to change, as AXP209 only supports 4,1V / 4,15V / 4,2V / 4,36V: echo 4100000 > /sys/class/power_supply/axp20x-battery/voltage_max_design I tried to reduce the charge current with rising voltage to stop charging at some point: echo 300000 > /sys/class/power_supply/axp20x-battery/constant_charge_current_max But the minimum supported value is 300mA, which is still charging and increasing the voltage. Also the charge current can not be increased again after setting a lower value. Does anybody have an idea how to stop charging at some voltage and to resume if it has dropped again below a second threshold?
  15. Hi - Earlier this week ( begin April 2020 ) I found out H5 boards become scarce. I was unable to find the H5 chip at allwinner tech H series section, suppose this will be replaced ? Anyone more info perhaps?
  16. Would there be a way to add a configuration option to armbian-config to disable built-in button being used for shutdown? Currently I have to remove the r_gpio_keys section in the DTB and compile. Seems like something armbian-config could do?
  17. Hi everybody, I have a problem with this version: Armbian_20.05.2_Rockpro64_buster_legacy_4.4.213.img I don't see my disk that is plugged on the PCIe To SATA Marvell 88SE9230 in the system. I've create the file /etc/udev/rules.d/99-marvell.rules with the following line on it: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x1b4b", ATTR{device}=="0x9230", RUN+="/bin/bash -c 'echo %k > /sys/bus/pci/drivers/ahci/bind'" If I do the same thing with this version: Armbian_20.05.4_Rockpro64_focal_current_5.4.46.img, I see my disk after creating the file. But, there's two problem with this version: first the fan always running and, more important, second I can't install OpenMediaVault on it. My question is, do I have to do something on the kernel? If so, could someone tell me what I have to activate to see my disk ? I don't have a lot of knowledge about kernels but I'm ready to jump it if someone could tell me where to check. Thank you all in advance.
  18. Is there an issues page relating to the M4V2 and Armbian Focal. I'm testing it and I have a few strange things happening with NFS and network but I was wondering if there as a known issues or a general topic regarding this board and this Ambian build because searching for nanopi-M4V2 Focal... is not a good idea. Thanks
  19. Hi there, I'm currently struggling to get the Cedrus VPU up and running. I have downloaded the specific version from bootlin and got the kernel up and running, however the V3s isn't supported by the Sunxi SRAM driver. This driver is important to get the VPU going. I tried altering the devicetree of the V3s to match a SoC that is somehow similiar, but it clearly failed for obvious reasons. I get this error message: [ 1.035259] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 1.040990] cedrus 1c0e000.video-codec: Failed to probe hardware [ 2.478247] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 2.484047] cedrus 1c0e000.video-codec: Failed to probe hardware [ 2.505765] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 2.511591] cedrus 1c0e000.video-codec: Failed to probe hardware [ 8.595278] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 8.601112] cedrus 1c0e000.video-codec: Failed to probe hardware I tried to understand whats going on in the linux/drivers/soc/sunxi/sunxi_sram.c file to adapt this driver to the V3s, but in the end I don't know how to do that. I hope somebody can help me with that or can give me a hint.
  20. Hello i hope you all have a nice day At first i need to thank you for all the work you done. I'm runnig my ROCKPro64 no for a while now Today i wanted to try wifi and bt but it looks we dont have any drivers for the module AMPAK AP6256 Combo Module and made specifically for the ROCKPro64 Debian 10 headless 20.08.0-trunk Can someone help me to reach the goal to use my wifi ?
  21. I have got 2x USB 3.0 RTL8156 ethernet dongles using one on my Rockpi4 the other windows client If the rockpi4 is the server speeds are awful [rock@rockpi4 ~]$ iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.1.12, port 52620 [ 5] local 192.168.1.9 port 5201 connected to 192.168.1.12 port 52621 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 56.7 MBytes 475 Mbits/sec [ 5] 1.00-2.00 sec 43.7 MBytes 367 Mbits/sec [ 5] 2.00-3.00 sec 46.3 MBytes 388 Mbits/sec [ 5] 3.00-4.00 sec 39.3 MBytes 330 Mbits/sec [ 5] 4.00-5.00 sec 45.2 MBytes 379 Mbits/sec [ 5] 5.00-6.00 sec 38.3 MBytes 321 Mbits/sec [ 5] 6.00-7.00 sec 41.4 MBytes 347 Mbits/sec [ 5] 7.00-8.00 sec 38.0 MBytes 319 Mbits/sec [ 5] 8.00-9.00 sec 42.0 MBytes 353 Mbits/sec [ 5] 9.00-10.00 sec 46.4 MBytes 389 Mbits/sec [ 5] 10.00-10.05 sec 2.29 MBytes 404 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.05 sec 440 MBytes 367 Mbits/sec receiver ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- RockPi4 as client [rock@rockpi4 ~]$ iperf3 -c 192.168.1.12 Connecting to host 192.168.1.12, port 5201 [ 5] local 192.168.1.9 port 38240 connected to 192.168.1.12 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 186 MBytes 1.55 Gbits/sec 0 220 KBytes [ 5] 1.00-2.00 sec 190 MBytes 1.60 Gbits/sec 10 212 KBytes [ 5] 2.00-3.00 sec 215 MBytes 1.80 Gbits/sec 0 212 KBytes [ 5] 3.00-4.01 sec 208 MBytes 1.74 Gbits/sec 10 245 KBytes [ 5] 4.01-5.00 sec 180 MBytes 1.52 Gbits/sec 30 212 KBytes [ 5] 5.00-6.00 sec 197 MBytes 1.65 Gbits/sec 10 214 KBytes [ 5] 6.00-7.01 sec 161 MBytes 1.34 Gbits/sec 0 214 KBytes [ 5] 7.01-8.00 sec 137 MBytes 1.15 Gbits/sec 30 214 KBytes [ 5] 8.00-9.01 sec 138 MBytes 1.15 Gbits/sec 20 217 KBytes [ 5] 9.01-10.00 sec 159 MBytes 1.34 Gbits/sec 0 217 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.73 GBytes 1.48 Gbits/sec 110 sender [ 5] 0.00-10.00 sec 1.73 GBytes 1.48 Gbits/sec receiver iperf Done. I prob need to sort some better cabling as my dodgy collection of battered and old ethernet cables made me rummage around until I got 2 half decent ones but I am not sure why client/server should make such a big difference and set speed? If the rockpi4 is the server and the client uses -R then [rock@rockpi4 ~]$ iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.1.12, port 52663 [ 5] local 192.168.1.9 port 5201 connected to 192.168.1.12 port 52664 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 181 MBytes 1.52 Gbits/sec 10 151 KBytes [ 5] 1.00-2.00 sec 187 MBytes 1.57 Gbits/sec 20 231 KBytes [ 5] 2.00-3.01 sec 199 MBytes 1.66 Gbits/sec 31 210 KBytes [ 5] 3.01-4.00 sec 204 MBytes 1.71 Gbits/sec 10 155 KBytes [ 5] 4.00-5.01 sec 184 MBytes 1.54 Gbits/sec 124 212 KBytes [ 5] 5.01-6.01 sec 205 MBytes 1.72 Gbits/sec 0 212 KBytes [ 5] 6.01-7.00 sec 187 MBytes 1.58 Gbits/sec 20 214 KBytes [ 5] 7.00-8.01 sec 207 MBytes 1.73 Gbits/sec 10 238 KBytes [ 5] 8.01-9.01 sec 198 MBytes 1.67 Gbits/sec 11 212 KBytes [ 5] 9.01-10.00 sec 182 MBytes 1.53 Gbits/sec 30 230 KBytes [ 5] 10.00-10.04 sec 8.15 MBytes 1.85 Gbits/sec 0 230 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.04 sec 1.90 GBytes 1.62 Gbits/sec 266 sender ----------------------------------------------------------- Server listening on 5201 Confused as it can but why not as the server? Anyone know more about iperf and networking than obviously me I prob need to get some better cabling as had a mare with some cables that just where not liked even though just 2.5g Also any tweaks or tips on network and packet settings to get the most and lower overhead?
  22. Fun stuff - and something that's kept me offline/busy for the last few weeks... # uname -a Linux blaster 3.4.0 #1 PREEMPT Wed May 13 14:43:07 PDT 2020 armv7l GNU/Linux # cat /proc/cpuinfo Processor : ARMv7 Processor rev 2 (v7l) BogoMIPS : 586.13 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls CPU implementer : 0x51 CPU architecture: 7 CPU variant : 0x1 CPU part : 0x00f CPU revision : 2 Hint - it's old enough not to have a device-tree... actually, in CPU years, it's old enough to vote/drink, and in dog-years, it's probably dead. I'll sent $20USD and a possible job offer if you can ID the specific chip... No @Igor, you don't get to play here
  23. <smaeul> scanning bus dwc3@5200000 for devices... 2 USB Device(s) found <smaeul> wooo, got USB3 boot working on H6 :D patchset at https://github.com/smaeul/u-boot/commits/h6-dwc3 Just catched this on #linux-sunxi IRC channel. I do not have a H6 board to test this but maybe someone else wanna give it a shot.
  24. Looking to find out why the Orange Pi OS Build isn't finding this file. Tried on two separate Linux 18.04 OS and neither has this file. When running Build_OrangePi.sh, right after entering the initial password, it drops out and claims the file lib32z1-dev not locate able. The only thing I can think is I need to install the SDK to build the OrangePi OS for this? Trying to do this from the Orange Pi Git Hub. https://github.com/orangepi-xunlong/OrangePi_Build Thanks for any help.
  25. Ever since patchfolders were created for different branches and different board families it has become more and more a nightmare to maintain these folders and keep them clean. Instead of taking the approach to clear one or more of these folders by myself, last but not least due to lack of necessary skills, I was thinking maybe I can provide some tools that make such tasks a little easier for somebody else. Last but not least was (and still is) this a perfect opportunity to pratice with my quite new Python skills. https://github.com/EvilOlaf/refactorpatches What this script basically does is break down all patches in a certain folder and check which files are targeted by each individual diff (if you choose to split them up) and sort the output by the target file. This way it should be an easy thing to merge patches that affect the same file and therefore it is no longer necessary to take care about the order to apply them. Requirements from apt: patchutils, python3 Requirements from Pypi: none but just make sure the prettytable.py is in the same folder as main refactor.py. I have tested this with random patch folders for kernel patches and for what it is expected to do at the current state it seems to just work as it should. There is still a ton of room for improvements. Let me know what do you think or if it is useful at all. Even if it is not I had fun coding and using Python