remlei

I assume thats the proper format because armbian-config is the one put that there so I never questioned about it. so far all of the NAND models seems to have USB OTG working but not all my eMCP boards, it always throw that error I posted earlier. also for some reason, in NAND models with jumpstart installed on NAND, overlay option on /boot/armbianEnv.txt for some reason do not work and have to resort editing the dtb file manually, all of it from led config to wifi stuff, also enabling the peripheral mode as well. I guess those overlay stuff only works when that u-boot bootscreen on emcp boards I had only have those overlay stuff working but not on the NAND models with jumpstart. After all those dtb shenanigans, I went ahead and install https://github.com/srepac/kvmd-armbian skipping all the way to step 3, a hour and 2 reboots later, yep its all working now. with 256GB USB flash drive mount on /var/lib/kvmd/msd and running that msd fix sh script to get that USB storage stuff working. sheesh, this box sure is really hell of a work. if I dont have extra time, id probably not doing this and just buy a cheap orange pi instead.

Yes I verified that its there. But im suspecting something though. I have a NAND rk322x and using jumpstart to boot armbian using sd card, can that possibly causing this issue? edit: nah scratch that, I snag my on emmc model and tried it there but this time uboot did throw some useful stuff it relates that it cannot load the dtbo file? I cd to the directory and it was there. edit2: managed to partially get the OTG port working, just have to edit the dtb file on my own instead of relying on armbian-config now the otg functionality kinda works? I ended with this error and basically clueless at this point [ 76.310374] dwc2 30040000.usb: new device is high-speed [ 76.310458] dwc2 30040000.usb: dwc2_hsotg_enqueue_setup: failed queue (-11) pi-kvm is partially working, the usb capture and everything works except for the USB OTG so no remote keyboard/mouse functionality.

Anyone managed to get the OTG port do USB peripheral stuff (gadgets)? I installed the latest armbian for rk322x on github armbian community. Looking at the kernel config, it looks like all the OTG stuff are set to Y by default now, execute armbian-config and set the dtb to rk322x-usb-otg-peripheral and reboot the system but alas, it still doesnt work with dmesg output pertaining that "Can't find any UCD" when executing "modprobe g_mass_storage file=/test.img luns=1 stall=0 ro=0 cdrom=0 removable=1". A little bit googling someone managed to get it working, I tried to follow what he did (but in more recent build of armbian instead of the legacy one), alas didnt managed to get it working. Using the provided rk322x-4.4 dtb file result of bricking my armbian install. My main goal here is to get that kvmd (pi-kvm port for armbian) working with rk322x.

I wish this was the case but as soon as armbian is installed on emmc, any image in the community repo from github do not boot the SD card first, for it to boot to sd card, I need to short that maskrom to ground. but for some reason, the old images does actually what you said, it boots to sd card first before anything.

this is expected specially for eMMC models unfortunately. its still possible to boot multitool after the emmc install but you need to find out how to put the board to maskrom mode. If you have SD card inserted to the board and and you perform maskrom, it should boot to SD card.

well you also need to know how to put the board in maskrom mode, with eMCP boards, this can be very challenging to do. I learned this in a hard way. Board bricked due to for some odd reason, it kernel panicked during emmc install process. and that managed to brick the bootloader as well. luckily I easily found that out by shorting a capacitor near the eMCP module, that basically put the board in maskrom mode. rockchip based tv boxes usually have these maskrom test pad placed somewhere in the board but amlogic tv boards is just bad. for people who wants to run armbian on tvbox board, just use the SD card/USB, the emmc install is just too risky.

while you can do a supervised install of Home Assistant on this box, I recommend getting a 2GB RAM variants specially if your going to run esphome to compile the firmware, 1GB RAM will literally crash the box during firmware compilation, all of that because of the very limited 1GB RAM. Else, if you can run HA without esphome, it works fine. Make sure to use a high endurance SD card as your storage for all the database logs, configurations. etc... just spare the eMMC for system use. Heck there are times that its actually much better to run armbian on SD card with home assistant because eMMC on these cheap boxes are really slow, specially the eMCP variants.

what I only did to get my installation to get supported is mess with that apparmor to properly work, I kinda remember changing stuff over /boot directoy. still if you dont mind the unsupported install notification so you dont have to hunt how to get your instal lsupported since after installation, home assistant supervise install works just fine and already survived several monthly updates of HA.

I successfully installed supervised install of HA using the images here https://users.armbian.com/jock/rk322x/armbian/stable/ what I did usually after armbian is installed is perform apt update and upgrade. after that I follow the most generic instruction how to install supervised install of HA, the only thing you need to watch out is install the right architecture for the os_agent. after that its just a matter of how to fix that unsupported install to supported. also a fair warning, do not install esphome on this box, the ram alone will make this box slow to crawl or worst crash the entire thing.

while rockchip have a USB-OTG support (both as host and client) on android in armbian however this is not implemented. so you will not be getting that usb-gadget features that pi-kvm uses for USB mass storage and USB Mouse/keyboard emulation.

when you run the multitool, did it prompt you a message mentioning that box your using is using NAND chip, if it does then you need to use legacy images which can be found here. You can only run later latest images via SD card or via USB with NAND bootloader upgrade. and even if you try flashing non-legacy image on NAND system, it will just error out during early boot process mentioning it cant mount something. to be honest if you have a NAND model, you might as well just use the SD card slot to run armbian.

@abhinavpra I used Orange Pi PC Plus image but you should try Orange Pi PC image first and see if it can boot, if it does you can try the Plus image and do a nand-sata-install in terminal to install armbian to emmc, though there are likely chance that it may not be able to detect the internal storage since newer mxq box with allwinner h3 contains emcp.

sorry about that. I used the image Armbian_22.11.0-trunk_Rk322x-box_jammy_current_5.15.72.img once the image flash, it works fine until you perform a apt upgrade. procedure to reproduce it is to perform apt upgrade and reboot. it doesnt really matter what dtb file I use but my board is based of V72 (MXQPRO_V72 2021-01-29) so even if I picked the V72 on rk322x-config the issue persist. funny thing about this is that the issue persist even after reflashing everything. I even go as far as reflashing Armbian_22.05.0-trunk_Rk322x-box_bullseye_current_5.15.25_minimal.img the issue still persist. Not until I reflash the tvbox-backup.gz I have before and suddenly after android booted up, that ethernet port suddenly works. this is no fluke, I didnt even touch the LAN cable nor replugging it, I just left it plug in all the time. I wish I had some meaningful dmesg output I can share other than having rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down rk_gmac-dwmac 30200000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off rk_gmac-dwmac 30200000.ethernet eth0: Link is Down over and over again. after reflashing my android backup, I just reflash Armbian_22.05.0-trunk_Rk322x-box_bullseye_current_5.15.25_minimal.img again and the ethernet port remains working even after update. let it run for 8 hours for no issue the next day, you know what ill try reflashing that Armbian_22.11.0-trunk_Rk322x-box_jammy_current_5.15.72.img image again. ok it works, perform update again, it broke. ----- so that's it, Im not really a linux developer guy to be honest so I cant really dig much further on the issue what causing it.

be warned guys that the nightly image have ethernet issues, you basically loose your wired network connection and flood the dmesg with rk_gmac-dwmac up 100mbit and shortly follow with rk_gmac-dwmac link down reflashing it with older image doesnt fix it, even with the 5.15.25 images, the only solution to fix this is reflash the android image and reflash stable armbian_22.02 image. they probably effed up something on the u-boot when i flashed the latest nightly.

you can just burn the armbian image to SD card, and let it boot. checking the RAM using free command, youll be looking at the mem part here (ignore the swap) and check the value of the total, this value is in megabyte, not mebibyte so that 1gig RAM is more likely to appear as <1GB unlike in x86 Computers. checking the emmec/nand storage can be done using fdisk -l command and look for the /dev/rknand or/dev/mmcblx