Jump to content

Forums

  1. Armbian

    1. Armbian project administration

      Start here if your intention is to help open source community around Armbian.
      Volunteering       opportunities, forum moderation, infrastructure issues and security (confident communication)

      • No posts here yet

  2. Community

    1. Announcements

      Important news and changes at the Armbian project

      644
      posts

    2. SBC News

      Atom feed, Pull requests awaiting review and other tech news

      4.4k
      posts

    3. Framework and userspace feature requests

      Feature requests and enhancement ideas. Stick around and bond with the community!
      Note: A request without funding behind is most likely not considered.

      947
      posts

    4. Off-topic

      Mingle and discuss whatever you want!

      10.3k
      posts

  3. Using Armbian

    1. Beginners

      No idea where to start or state your question? Here is the right place for you!

      20.4k
      posts

    2. Software, Applications, Userspace

      Issues or questions that are hardware-independent regarding various 3rd party / userspace software and applications

      1.8k
      posts

    3. Advanced users - Development

      Kernel, patches, hints, image building

      16.3k
      posts

  4. Standard support

    1. Amlogic meson

      2.6k
      posts

    2. Allwinner sunxi

      3.2k
      posts

    3. Rockchip

      11.2k
      posts

    4. Other families

      3.7k
      posts

  5. Community maintained / Staging

    1. TV boxes

      27.7k
      posts

    2. Amlogic meson

      Community maintained Amlogic boards

      2.6k
      posts

    3. Allwinner sunxi

      Community maintained Allwinner SoC based boards

      41.1k
      posts

    4. Marvell mvebu

      Community maintained Marvell SoC based boards

      2.4k
      posts

    5. Rockchip

      Community maintained Rockchip boards

      14.4k
      posts

    6. Other families

      Unsupported boards

      2.6k
      posts

  • Volunteering positions

    • More information about "Code reviewer"

      Code reviewer

      Position: Framework maintainer
      Number of places: Unlimited
      Applicants: 9

  • Chat | Social Media

    #armbian at
    irc.libera.chat or irc.oftc.net
    Matrix or Discord
    Mastodon | 𝕏

  • Popular Now

  • Activity Stream

    1. 5

      [Project] OpenAuto RK322x (Alpha) : Android Auto Running on Rockchip SOCs

      Update: The reason i haven't released the cursor patch is because im working on the GUI. I managed to now use EGLFS with FFMPEG, so it feels right that we modernized the crankshaft-ng GUI to feel more modern and usable.
      Harleyyyu in Rockchip CPU Boxes
    2. 24

      espressobin completely set aside?

      Hi guys, I have a Espressobin V7_2-1 Model: Marvell Armada 3720 Community Board ESPRESSOBin (eMMC) CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [MHz] DRAM: 1 GiB Would you be so kind as to make the flash-image-DDR4-1g_1cs_5-1000_800.bin?
      Anto in Marvell mvebu
    3. 800

      How to install armbian in h618?

      Bluetooth now working, no compiling required via hciattach. I don't know how much of this is necessary because I generally don't know what I'm doing. But here goes. Apparently hciattach is a legacy app that requires the firmware to be in /etc/firmware so I made a folder and setup a symlink before running the hciattach. <NOT REQUIRED> sudo mkdir -p /etc/firmware <NOT REQUIRED> sudo ln -sf /lib/firmware/aic8800_sdio/*.* /etc/firmware sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep <NOT REQUIRED> sudo hciconfig hci0 up Bluetooth should be available now. You can test it with sudo hcitool -i hci0 scan This will display any devices in the area the bluetooth adapter has detected. I had installed armbian-firmware package so that might also be required but I doubt it. I will flash a new image and start from scratch just to make sure everything I've stated works on a fresh install and then update the thread. Edit: I tested it on a fresh image and the only command required for bluetooth to activate was the hciattach line. I couldn't figure out how to do strikethrough in the code block so I just listed added the "NOT REQUIRED" info. I didn't want to remove them in case it helps someone else. The firmware files I mentioned in a previous post need to copied over and the device powered down before running the hciattach command. The hciattach commands do not persist through a reboot so I need to figure out how to get this to run on startup, hopefully the easy part. Thanks for all the help. Hard to beat that feeling when you spend hours troubleshooting something and it fires up for the first time!
      BoringName in Allwinner CPU Boxes
    4. 19

      BPI M1+ SATA Support

      Some context: https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working The hardest part and expensive for time is keeping functions working while kernel changes, goes up. Image you are referring too is probably a demo image with some ancient kernel that will never be changed. This is usual way to sell hardware. It is made to work, but you will stay at this very old SW stack without any real option to change or fix anything. All functions on 300+ boards, which on top of extreme diversity, have also different revisions, quality issue ... is already not possible to keep up by entire open source community. Armbian is small part focused into SBCs and we do what we can. Work we are doing is never complete, we (nobody) can't solve bugs and especially not near to (expected) real-time. We (or community open source in total) can address a problem within weeks or months fastest as resources are tiny compared to problems that are constantly found in open source code that somebody else made. We have no option to expand the team / project as users don't care about well being of SW developers. We can only try to keep SW stack operational on a best effort principle. Once this job becomes too expensive (<1% of costs share is on users side), we have to step back and declare support as "community". We will continue to build and ship images as they might still work for some use cases and as downstream projects will provide those Armbian images anyway.
      Igor in Advanced users - Development
    5. 5

      btrfs replace fails with rockchip64 edge kernel

      A month ago when doing test boots and power measurements, see I discovered that when using the RPL 27W 'Pi5' PSU, the NanoPi-R6C with the indicated bootloader(s) and kernel(s) sticks to 5V. But when using a 45W USB-C PD PSU from a HP laptop or 60W USB-C PD PSU white-label, switch is made I saw on a USB-C PD power measurement device that was also in the chain. More detailed USB-C PD protocol analysis seems to be needed in order to figure out what happens. One could guess 3A is requested at highest possible voltage as with the 45W PSU, I saw 15V. 9V or 12V would also be OK, but the PD handler cannot be 100% sure I think, depends also what is inserted in USB type-A ports on device etc.
      eselarm in Beginners

  • Member Statistics

    • Total Members
      34658
    • Most Online
      3990
    Marcos Araujo
    Newest Member
    Marcos Araujo
    Joined
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept