MattWestB

@fedex My test script is showing the same and i can installing portainer and / or docker agent and its working OK.
What is HA complaining then you is trying installing it ?
Also the CPU is 32 bits so need using installing the "armv7l" version by selecting "raspberrypi2" or its failing.
 
@jock I think we shall not hijacking the thread with no Armbian things and you must saying if we shall stop spamming it with HA problems.

Hi everyone,
 
Can anyone help me? I'm not so technical guy so please bear with me.
 
I decided to use bullseye image because I have a hard time using jammy in remote session. It really really slow.
 
I just want a system running adguard home. So I think I need aguard home installation and a browser to configure it.
 
My problem is that I cannot launch the browser (chromium) in SSH for the obvious reason.
 
What do I need to install to be able run and configure adguard home. I really appreciate if anyone guide me for the command that I need to use.
 
Thank you so much.
 
EDIT: Silly me, I figure it out. I just need to install aguard home and configure it in my local computer (laptop) 😅

@cmuki
Assuming the boot you provided is from the original image, I think there is no extra questions to ask: if the ddrbin says that you have 2048 megabytes, that is so.
The ddrbin, which is the first piece of code that is executed at all and initializes the board DDR memory, is the most reliable source from this point of view.
 
Going on with the bootstrap phase, u-boot says the same:
U-Boot 2017.09-gaa00306-201224-dirty #foxluo (Jan 19 2021 - 14:31:53 +0800) PreSerial: 2, raw, 0xff130000 DRAM: 2 GiB  
And obviously even the linux android kernel also detects 2 gigabytes of total RAM:
[ 0.000000] Memory: 1955884K/2064384K available (14910K kernel code, 2056K rwdata, 8884K rodata, 3968K init, 2806K bss, 75732K reserved, 32768K cma-reserved)  
That's it, fake hardware specs; the manufacturer altered the Android image somehow to show fake specs and maybe something is wrong with the DDR chips too (are they have been reprinted? are they just fake chips or not really connected to the board? who knows...)

@MattWestB @fedex Hello, I enabled BPF filters and various other related options.
I built an experimental kernel you can install with dpkg taking packages from here
 
I didn't enable other cgroups options except for the one related to BPF, let me know if docker works for you or still there is the need for something else.

@fedex not really too much time lately, but I will try to enable config options and compile it today if possible!

Checked  Armbian_22.02.0-trunk_Rk3188_bullseye_current_5.10.96.img
changing dtb that ususally gives me partial function on Minix Neo X7 (Ugoos, CS968)
without luck (no boot, no led), same thing happened with latest LibreElec RK3188 images,
no boot, no led , sometimes kernel panic.
 
With this image and included default .dtb (rk3188-ugoos-ut2.dtb) boot from SD works ok:
 
Armbian_21.11.0-trunk_Rk3188_hirsute_current_5.10.63.img.xz
 
Also internal USB-LAN (RTL8152) works ok,
No Wifi , No BT  (GPIO3_23 conflict with ethernet)
will debug more about this and come back later.

Ubuntu 22.04 LTS rk3318-box is up and running nicely with working Docker and HA supervised looks working OK.
Up time is only some hours after install but the prereleases was also working stable so hopefully it shall doing the same.
 
Great thank devs for making it happening !!!

Ubuntu 22.04 LTS rk3318-box is up and running nicely with working Docker and HA supervised looks working OK.
Up time is only some hours after install but the prereleases was also working stable so hopefully it shall doing the same.
 
Great thank devs for making it happening !!!

Erase flash from multitool isn't work.
After reboot android still boots. 
 
I was able to boot armbian from a flash drive, but first I need to boot MXQ with the sd card (multitool) and the flash drive (armbian) inserted together. After a second, I remove sd card (multitool) and armbian boots from pendrive.
 
/edit
Succesfull install armbian on emmc using dd command.
Big Thx for you boys
 

What do you mean by adding support ? To what ?
To libreelec recognizing the wifi chip, but then should ask in libreelec forum, or add support to armbian to run kodi, then you missed a lot of previous posts.. ?

 

@chinhhut

Try these steps:
1) push the little switch inside the hole while inserting a male-male cable into the otg
2) on another linux machine you should have now a new device (lsusb will help you) and you can run rkdeveloptool
3) rkdeveloptool ld should List Device
4) rkdeveloptool rd 3 should Reset Device into mode 3  ( maskrom )
5) rkdeveloptool db MiniLoaderAll.bin ( of course from your path) should upload a temporary loader to recognize the internal emmc
6) if all is successfull until now you can rkdeveloptool wl 0X0 yourimage.img . This should flash the internal emmc .

DISCLAIMER: very " dangerous" approach , be ready to have the opportunity to short the emmc clock pin to ground to go back into mask rom
 
MiniLoaderAll.zip

@jock had to wait for 24 hrs to reply to your post. I will try the other images when I have the time and play around with it.
 
Here are the pics:
 
https://drive.google.com/file/d/1JGB3Ihnp1kKlnuh6fkCftuHMoj0aInjD/view?usp=drivesdk
 
https://drive.google.com/file/d/1JImmtinhNfkJxE8qCE_0q9afLQHg3sRL/view?usp=drivesdk

Thanks jock for this post. I was able to unbrick my device. I now have successfully installed Armbian on my device and loves its performance by following this post.
 
My device is called Ninkbox N1 Max RK3318. I was trying to look for a firmware suitable for my device but I am unable to find the exact one. I tried asking support from their main website but to no avail. So I tried installing different firmware on my device with almost the same chips until I ended up bricking the device. Unfortunately I already bricked the device before landing into this post so I was not able to backup my original firmware. For some unfortunate twist of fate I also have those BGA chips with no exposed pins. Upon further examination there are two round copper at the back of the board where the BGA chip sits. After burning the image on an SD card I tried shorting the round coppers with a piece of staple wire and it gave me the Multiboot window.
 
I am writing this for those other people who may have the same device as mine and is looking to setup Armbian or probably trying to unbrick their device.
 
This is my EMMC Chip
https://drive.google.com/file/d/1J5E8OGBUOV_sdQ0VF0glIt4t6yhRKxrr/view?usp=sharing
 
The picture of my device
https://drive.google.com/file/d/1J2Ha8nUhA5hhXne_vqHdyzLBOlxCWcMV/view?usp=sharing
 
The round copper at the back of the board to short
https://drive.google.com/file/d/1J-X_9Y4jKr8u87lEosGkBmtpwjdxGsFb/view?usp=sharing
 
My device desktop after successful install
https://drive.google.com/file/d/1J5hkfP7A4U5r6xO7P9Zgv8ArpjUmZJ0g/view?usp=sharing
 

The Z80-MBC2 is a 4-chip Z80-computer which can run CP/M and has a 5V TTL-serial-port.
The Z80-MBC2 is powered and accessable via a USB-TTL-serial-adapter (configured to 5V - not 3.3V) type CP2102 seen as /dev/ttyUSB0
 
The easy way would be to connect the USB-adapter to a Pi-style computer wth armbian, login via SSH and start minicom for the port.

But that way doenst look as good - to me - as the following way  
 
First we need to install ser2net and telnet (telnet doesnt seem to be installed as standard) in armbian via
apt install ser2net telnet
 
Then we have to edit /etc/ser2net.conf (delete all lines after the comments and insert these):
 
BANNER:banner:\r\nser2net port \p device \d [\s] (Debian GNU/Linux)\r\n\r\n BANNER:z80mbc2:\r\nZ80-MBC2 via Telnet on Port [\p]\r\nDevice connected to [\d]\r\nConnection Speed [\s]\r\n # 2000:telnet:600:/dev/ttyS0:9600 8DATABITS NONE 1STOPBIT banner # 2001:telnet:600:/dev/ttyS1:9600 8DATABITS NONE 1STOPBIT banner # 3000:telnet:600:/dev/ttyS0:19200 8DATABITS NONE 1STOPBIT banner # 3001:telnet:600:/dev/ttyS1:19200 8DATABITS NONE 1STOPBIT banner 127.0.0.1,2023:telnet:0:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT z80mbc2  
Now create a login "shell"/pogram for the new local user z80mbc2 as /usr/local/bin/z80mbc2 :
 
#!/bin/sh /usr/bin/telnet 127.0.0.1 2023 exit Do a chmod 755  /usr/local/bin/z80mbc2
 
Now we can create the new local user z80mbc2 as seen on
http://www.lug-wr.de/wiki/index.php/Howto:Network:SerialConsoleServer
 
adduser --shell /usr/local/bin/z80mbc2.sh -q z80mbc2  
If you havent done - connect your TTL-USB-Dongle to your SBC - and it should show up as /dev/ttyUSB0 :
[354660.047087] usb 7-1: Product: CP2102 USB to UART Bridge Controller [354660.047099] usb 7-1: Manufacturer: Silicon Labs [354660.047109] usb 7-1: SerialNumber: 0001 [354660.112318] usbcore: registered new interface driver usbserial_generic [354660.112414] usbserial: USB Serial support registered for generic [354660.131499] usbcore: registered new interface driver cp210x [354660.131617] usbserial: USB Serial support registered for cp210x [354660.131902] cp210x 7-1:1.0: cp210x converter detected [354660.141405] usb 7-1: cp210x converter now attached to ttyUSB0

Now its time to reboot your SBC (I used my NanoPi K1 Plus) via
reboot 
to automatically let start ser2net-service while booting
 
Now when you connect to your SBC via SSH and use the z80mbc2 User to login, you should generate a automatic and local (127.0.0.1) telnet-login to Port 2023 where /dev/ttyUSB0 a.k.a the Z80-MBC2 device is configured.
 
PS: other (german) interesting Page about ser2net:
http://www.nwlab.net/tutorials/ser2net/konsolenserver-linux.html
 

 

Z80-MBC2_SSH_Ser2Net.zip

From the log:
MMC0 = SD-Card
MMC1 = is the WiFi card but i think its not finding the firmware for it.
MMC2 = eMMC but its being probed with very strange clock speed.
MMC3 = not used or its the eMMC.
 
With RK-3228 boxes its not working good at the first boot then the system is loading NAND and eMMC support.
If first config no eMMC and only NAND and rebooting and the config only eMMC support and booting and updating the system its being detected in full speed and working OK.
 
For the WiFi have you loading the full firmware pack ?
The problematic files is in the git https://github.com/armbian/firmware/blob/master/brcm/brcmfmac4330-sdio.rockchip,rk3318-box.txt.

Hi everyone!
 
at first I would like to thank jock for his great work.
 
It's probably kind of dumb questions, but I'll ask it anyway  Should we use apt-get upgrade for those images? Because, when I did, the armbian seems to be crashing during next boot. It seems that rk3318-box.dst is not in a /boot/dts/rockchip directory after the upgrade, and uboot tries to boot from the mmc0 instead of mmc1. My box is H96 max 4GB/64GB which I bought really cheap due to fact it's bricked and always starts in a maskrom mode. Below is the log from uart : 
ID:0xFFF In DDR3 333MHz Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB ddrconfig:3 OUT U-Boot SPL 2021.07-armbian (Jan 25 2022 - 12:54:45 +0000) Trying to boot from MMC1 NOTICE: BL31: v2.5(release):c1588782-dirty NOTICE: BL31: Built : 12:54:38, Jan 25 2022 NOTICE: BL31:Rockchip release version: v1.2 U-Boot 2021.07-armbian (Jan 25 2022 - 12:54:45 +0000) Model: Rockchip RK3318 BOX DRAM: 4 GiB MMC: mmc@ff500000: 1, mmc@ff520000: 0, dwmmc@ff5f0000: 3 Loading Environment from MMC... MMC: block number 0x400000 exceeds max(0x4) *** Warning - !read failed, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Rockchip RK3318 BOX Net: eth1: ethernet@ff550000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 211 bytes read in 4 ms (50.8 KiB/s) 11502551 bytes read in 505 ms (21.7 MiB/s) 30345728 bytes read in 1321 ms (21.9 MiB/s) Failed to load '/boot/dtb/rockchip/rk3318-box.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 2698 bytes read in 10 ms (262.7 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 08000000 Moving Image from 0x2080000 to 0x2200000, end=3f90000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 11502487 Bytes = 11 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@ff500000.blk... Scanning disk mmc@ff520000.blk... fs_devread read outside partition 1024 Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Card did not respond to voltage select! : -110 Scanning disk dwmmc@ff5f0000.blk... Disk dwmmc@ff5f0000.blk not ready Found 3 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Card did not respond to voltage select! : -110 starting USB... Bus usb@ff5c0000: USB EHCI 1.00 Bus usb@ff5d0000: USB OHCI 1.0 Bus usb@ff580000: USB DWC2 scanning bus usb@ff5c0000 for devices... 1 USB Device(s) found scanning bus usb@ff5d0000 for devices... 1 USB Device(s) found scanning bus usb@ff580000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found  
The other question I have is : canthe eMMC be used as additional storage while booting from SD card? I've checked and there's no additional mmcblk device in /dev. Is the eMMC configuration is missing in devicetree, or its something related to my board (faulty emmc?).   
 

LAN working on Minix NEO X7.
For now I gave up on trying to find the IO-pin that controls the LAN power on the Minix NEO X7 board.
By making a hardware modification, involving removing a voltage controller (because unfortunately 1 pin broke during the modification) and placing a wire to get the LAN power supply from another voltage controller, I got LAN up and running. I will leave it running for a couple of days to see if nothing breaks.
 
I can state that the drivers for the Realtek 8152B USB ethernet adapter are working.

New version ArmbianTV of images for RK3288 and RK3188.
 
 
rk3288 \ rk3188
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
rk3188
https://disk.yandex.ru/d/7wqSh5Z5bv9q1g?w=1
 
rk3288
https://disk.yandex.ru/d/fRZwre9HDgAKHw?w=1
 
 
 
 
This link contains images with Libreelec for rk3288 and  rk3188, testing these images can help with the development of media functions for rk3288 and rk3188.
 
https://disk.yandex.ru/d/8vNYuuxynz1L0w?w=1

ver 20220205 kernel 5.10.96 for rk3188
 
Please note, now I am publishing new versions for rk3188 only on yandex disk (in order not to occupy Armbian resources with non-profile and unsupported versions that are released "as is" without any guarantees of work and support)

Minix Neo X7 LAN via RTL8152: It seems that the RTL8152 is not powered on after booting. I cannot measure any supply voltages to the chip. When booting from Android NAND the supply voltages are there.
 
I expect that there will be a GPIO that switches the voltage regulator and I'm going to look into this. But it will be a search for the needle in the haystack.

Multitool update!
 
Hello! I'm pleased to announce that multitool finally got network and SSH access, and now can be used on headless systems!
 
The latest release will retrieve an IP from the network DHCP server automatically, so you can consult your local network router to discover what IP the box got.
SSH access can be obtained logging in as root user; no password is requested.
Example with IP 192.168.1.18:
paolo@predatorg:~$ ssh root@192.168.1.18 Welcome to Multitool SSH session! root@multitool:~#  
 
Link-local access:
 
Multitool will also, by default, listen to link-local 169.254.120.120/16 address. This is useful if you have no DHCP server or have troubles retrieving the IP address.
Note that to access such private IP you need to set a network interface of your PC on the same subnet, or also use a virtual interface.
 
Here there is an example using ip assigning address 169.254.89.32/16 to virtual interface eth0:1 (address can be changed at your pleasure, interface must be the same interface you use to access the box, ie: wlan0, enp0s25, or whatever):
ip addr add 169.254.89.32/16 brd + dev eth0 label eth0:1  
or if you prefer old but good ifconfig:
ifconfig eth0:1 169.254.89.32/16  
then the multitool is accessible to 169.254.120.120:
paolo@predatorg:~$ ssh root@169.254.120.120 Welcome to Multitool SSH session! root@multitool:~#  
Of course link-local access won't work if you have multiple devices running multitool on the same network, since all of them will conflict because they have the same IP; in such case use the IP provided by DHCP.

Thanks @jock for comments.
The problem is that user like my with boxes that the HDMI is not working and then cant getting mulltitool working at all also from serial console so being complete blind and if copy your first part of mulltitool and copy one armbian to on partitation after the boot part is possible installing armbian without problem in EMMC with SSH.
Is it OK posing part of your mulltitool with added system partition on git-hub if some user is requesting it ?
 
I have only found focal with desktop and installing it i only have little more than 2G free flash and HA is needing that or more so i need mounting the SD-card in docker storage directory then i have 64G for containers and still can installing things and doing updates.
 
The LEDs is right configuration and changing is not helping (the LED is power off mode) so i must trying your trigger if google can giving my the right guldens.
 
@fabiobassa you are more then welcome PM my or you can open issue in one of my git-hubs repros like https://github.com/MattWestb/R29-MXQ-LP3-V2.3-00908.
Im not one expert on HA but have much knowledge with ZHA part and the Zigbee system and device.
If i can help with some problem or sharing some good or bad experience is very OK for my and you looks have much knowledge in other interesting technical things.
 
PS the soldering is not so good that it can being but working and it can being better done but with the age its more Shaking Stevens have doing it ;-))
 
Mvh  Mattias

Could you just use the nand/flash you have onboard?
 
Well, it does what it is supposed to do... If you shutdown your PC, it shuts down; your PC has the button to turn it on, the tvbox has no button, so you have to unplug and replug the power cord.
 
You need to chose the right board, the LED should turn on when then kernel loads.
You can control the leds using /sys/class/leds/working/trigger and /sys/class/leds/auxiliary/trigger filesystem object. Google is your best friend here
 
No typo. Armbian image has all the things in the right places to boot as explained in the instructions.
Supposing you have eMMC/eMCP, to boot from SD card you need one of these:
to clean the internal flash memory, or install Armbian on internal flash memory If you have NAND, you need one of these:
to clean the internal flash memory (not suggested for NANDs), or install Armbian via multittol step-nand on internal NAND, or install Jump Start via Multitool on internal NAND

@MattWestB
compliments for your installation, looks fine

Are you ok on home assistant ? would ask something,  maybe i can send you a private message ?

 

I was rebooting the box after nearly 8 days of up time with HA supervised and that is not bad for the "first try" running it on the new hardware.
I was not liking the external SD-Card that is 4/5 outside of the box and im using micro SD-card so i was baying one cheep USB card reader and desolating the SD socket and soldering up side down on the back side of the external in the box so i can mounting the SD-card or one adapter for micro SD-card inside the box and having the docker container storage on it and its working OK. (only 2 pads was tricky getting OK in the middle and dont looks so nice but is working OK)
 
I was doing one mistake that i can fixing but im sure some knowing how to do that.
By using commands shutdown the box is being shutdown and cant being powered on then its not having any power button so must re powering by taking  the power cord away and back but after that the power LED is always off also if i changing the LED config with RK-config.
Is it possible sending one command type "LED on" so its start working or some other work around ?
If booting on external SD-card or USB with one new installed armbian its working  OK until using shutdown.
 
@jock in the first post in "Quick installation instructions to boot from SD Card:" you is writing "Erase flash" and then Build or download your preferred Armbian image and writing it to one SD-card and booting armbian.
But its not working then its not bootloader in the internal flash so the chip is trying to finding one on the SD-card = OK but all armbian images is only system in and no bootloder so the chip cant booting if not adding one bootloader and  u-boot on the SD-card before the system partition. Have i misunderstanding some thing or is it one typo ?
If having one image with "normal" bootloader and u-boot and one minimal system partition (one meg or so) then it shall being extending the partition and copy one system partition the card having it booting OK also for no Linux skill window user with minitols that can extending Linux partitions and also copy them between dicks from windows.
 
Thanks for great support and work with our boxes and hope next Ubuntu LTS is coming soon (beta is booting OK but is not  working OK for one week ago) and working great on them in near future !!