BreadLee

@Igor Thank you for your reply. I was inattentive yesterday, in fact, this manual was used by me already, but I forget about that. Thank you! Kind regards

Hello! I'm building Armbian Images from scratch. So, I want to add my own repository to the repos list and install my packages during Armbian building process. Is it possible to do? Best wishes, Breadlee

May you tell more about your idea?

Igor, I tried to do that, but currently it shows me an error with SD card also. I will try to move it on to eMMC, but it will not work, in my opinion. Update: Same with eMMC

So, it was my mistake I just not configured files properly.... Sorry for that question... Kind regards

Igor, thank you for your reply. I will check it right now.

Hi, I built a fresh Armbian Image from scratch (using Armbian build system). After that I used Etcher to burn .img file to SD card. Everything works great, but U-Boot shows, that there is no environment. I used saveenv and fixed a problem. Then I installed Armbian into internal memory (eMMC), same message about environment, I tried fix it same way, using saveenv, but I get only an error message and infinite loop. Screenshot attached. How I can fix that? UPD: My board - Orange Pi Zero Plus 2 Kind regards

Hello to everyone! I am trying to configure dual boot using u-boot. But I've got some misunderstandings, maybe someone will help me with that problem. When I'm booting from SD card everything works fine: rootdev=/dev/mmcblk0p1 (armbianEnv.txt) or rootdev=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX in both cases. When I'm booting form eMMC something goes wrong: I can not set rootdev=/dev/mmcblk1p1 cause in this case I've only error message: But if I'm setting as rootdev=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX everything works fine. Maybe it is bad way to use /dev/..., but I need it. So, I tried a lot of ways to fix that and found that, such situation only with legacy kernel, mainline works without any issues. Where I'm doing wrong?

@chwe Thank you for you reply! Yes, currently I want to create second partition with its own kernel and other files, but I don't know how to do that? For me it looks so mysterious , cause I'm noobie in U-Boot and Linux Kernel. I'm trying to dive in this suff using google, but it doesn't work such way. To this moment, I compiled U-Boot and Linux kernel (uImage) and DTS file... I tried to mix this files on SD card, but without any great results Maybe you will advise me something?

@martinayotte Thank you very much for your help! If I will find a right way to create a such system, everything will posted here as an asnwer. Best wishes

Sure, I understand that. Currently it will be great for me, to make such system with a human intervention. I don't know how to store two systems and one u-boot and select only that system, which one I want to boot...

My idea looks like this: I want to create system, which will can be restored by itself. I've got two separate partitions: first one which works everytime, in other words main partition. Another one will be used in emergency cases only (restore partition). For example: something goes wrong, it is not possible to boot from the main partition. I want to boot from restore partition, then I want rewrite main partition from restore partition. Then reboot and work in normal mode, until new emergecy case will occur.

I already build Armbian by myself and it works great. But I don't know how to change partition scheme during building. There any official documents available on this topic?

You are absolutely right.... But I don't know how to start and where I can find information about that. May you advise me something?

I'm trying to create device with two partitions, which situated on eMMC. First one will be main for system and user, but in cases, when main boot will be broken I want boot from second one and then rewrite broken partiton. So currently I don't know how to do that. That is why I started with U-Boot and it's functionality. Maybe I'm chosen to go wrong way.

Dear Community, I am actively using an Orange Pi Zero Plus 2 board and I want to build U-Boot mainline by myself. I donwloaded mainline version from Denx's git, but when I'm doing configuration for Orange Pi Zero Plus 2. it uses H5 chip, but my board works with H3. During building Armbian Images, build system downloads latest U-Boot version and build it for H3 chip. I'm new to u-boot and maybe someome will help to find propper configs. Kind regards

Dear Сommunity, I've got an Orange Pi Zero Plus2, it has a WiFi only, no an Ethernet interface. But I want to use a TFTPBoot for my project. That's why I've got two questions: How I can configure/compile U-Boot with WiFi support? And how I can configure it for usage with TFTPboot? Kind regards, Bread Lee

Thank you for your reply! Actually @Igor was right. Yesterday I installed all packages that he advised, but it seemed that nothing changed. Today after board powering everything works great.... I think, that yesterday I didn't reboot board. Also this script ( from Armbian git) helped me a lot. Thank you @arox and @Igor Best wishes

Ohhh, I see! Thank you! I will continue my work... Kind regards

Dear Igor, Thank you for your reply. I installed everything, but same problem no bluetooth controllers available in the system... May you guess what's wrong with my system?

Dear Armbian community, I'm trying to make a minimal size Armbian image ( Ubuntu 16.04 with default kernel). Build system works great, but when I'm building the system without GUI (Image wit console interface "server") a bluetooth system doesn't work. I tried to build same system with same configs, but set "Image with desktop environment". In this case bluetooth system works great. I tried to solve this problem by myself, but..... It seems like I can not fix it. So, why I'm thinking that bluetooth system doesn't work. When I'm using bluetoothctl list it is void output. hciconfig -a void output I tried to start systemctl start bluetooth and after that systemctl status bluetooth, it shows that a bluetooth service works fine and everything ok. I hope you will help me! Kind regards