-
Upcoming Events
-
-
Volunteering positions
-
Code reviewer
Position: Framework maintainerNumber of places: UnlimitedApplicants: 8
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
8
Make SDcard image with sole purpose of eMMC receiving a fresh bootable Armbian image
I had no idea there is a script for THAT Thanks Armbian team To the original poster: all beginners should stick to microSD. Please gain experience, make the tool you want, and share it here. Also look at this wonderful tool that bedna made: (it might be useful for you) -
14
Orange Pi Zero 3 ili9486 TFT LCD
Did you have any success with the ili9486? I would like to use a bigger 480x320 pixel SPI LCD panel -
8
Make SDcard image with sole purpose of eMMC receiving a fresh bootable Armbian image
I understood perfectly well, but this functionality is necessary for mass deployment. Previously, this was used by lazy and smart system administrators when the task was to expand the number of new jobs. But there seems to be something different here. On which hardware devices does the author want to massively deploy operating systems? -
5
No gpio on BPI M4-zero
When you cloned our repo, you got 10 years of specific work on common work and that was contributed by 500+ people. Most of people are resolving their specific problems, yes, but we all try to do it the way that is reusable, that person behind has less work. We also got a lot of things prepared. Doing things universal should always be considered. Also because you might get help from someone. Which has absolutely same problems, but is having hardware from another vendor. In our world, SoC defines how things work, not the one that put SoC on PCB and name / sell it. This means that most of the drivers are the same, especially this area is shared - low level communication protocols such as GPIO, I2C, SPI. This is always shared among boards with the same SoC. This goes further. It is shared among same families and we also already have some common generic top level API / libraries that can be used. https://docs.kernel.org/driver-api/gpio/consumer.html (but here my understanding ends, I am not updated with the state of this) Yes, it has no point poking into. WiringPi library is a dead project for many years and its no point dealing with this. What vendors do here is, trying to be "as Rpi as possible", so they are doing their quick and dirty assemblies of that, always with partial functionality and absolute absence of maintenance. Their goal is to sell, regardless what is the quality of software. Is that your goal? I doubt. I am not an expert in this field, so those are general tips, but there are people on and around this forum that knows this stuff well, as they developed those libraries. I am just giving you some ideas / tips. Decision what you will do with your time is yours. Another one that came into my mind, while replying: https://github.com/eclipse/mraa1 -
8
Make SDcard image with sole purpose of eMMC receiving a fresh bootable Armbian image
@going Probably @wwortel means to develop a minimal boot image which would download and dd image to eMMC. I agree that would be nice to have, but develop that requires time / resources we don't have. If you look into the script that installs OS to eMMC (and other media) its pretty complex and hard to maintain https://github.com/armbian/build/blob/main/packages/bsp/common/usr/bin/armbian-install Not to mention that people doesn't pile up to help us around that. There is / always was just a few people that sacrifices their precious family time to provide you current experience. Where we can always find something to fix and improve.
-
-
Member Statistics