All Activity

I received the box. How can I open it? I didn't find the screws.

Made a release build & images are uploading and syncing. This will take at least a day ... we continue to test. Repository update can wait a bit.

Thank you. I have sent you email.

Hello! I try to connect to OrangePiPC by serial console. I tried using UART1 (add overlay & switch console to ttyS1), UART3 (ttyS3) and ttyS0 (debug port). But always I can see output (with kernel or ) but on my host computer (ubuntu 20.04) I see login prompt and can't enter anything. I tried change speed but not login. Even when I stop serial-tty@ serivice and start minicom without luck. Can you help me?

Tried with BalenaEtcher and it works well

Can you tell me what FDT you're using? If you aren't passing the right tree, it may be disabling the emmc. Check by: "cat /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000"

I'm guessing you don't have a "scriptaddr" variable after the env update. Pali helped me track down a bug in u-boot, for which I've submitted a patch. Then, we'll need to build a new u-boot for ebins, to really resolve the issue. In the meantime, add env set scriptaddr 0x6d00000

Thank you. I built it last evening. It appears stable, iscsid now starts (fixed the key symptom) and does allow Longhorn to work. I also included the Ceph kernel modules due to future testing plans. I'd like to run with it for a few days to see if there are any problems and, barring any problems, will submit the PR in a week or so.

This is exactly the reason why the linux has no bugzilla-like issue tracker, because people would abuse of that since this is not a bug of the kernel. Please, stop posting nonsense.

You can try and follow the "Restore" paragraph on the first page. It shows how to manually upload an image to the internal flash without using the multitool but just the basic maskrom mode. But from the photos I see that your stick has a SPI flash memory. It has never been tested and I don't think any image could even boot there because both u-boot and kernel must be aware of that hardware, and in current images they aren't.

That's unfortunate to hear. I also bought a BPi M2 Zero based on the premise that the PIN's are compatible with Raspberry Pi and hence my Hifiberry Digi would be supported. Did you eventually get it to work by re-wiring the PINs somehow? Did you get your HAT working on another board?

Thanks! Unfortunatelly it is not working for me. But with the tag "tinkerboard-2" now I can found more information in the forum and stay up to date.

No descriptionView the full article

If you need help then please let me know. And ideally CC to my (kernel) address.

Check if something important is missing from the docs - if you have added pull requests to the Github without a Jira ticket, then its missing from the list. Please add now!

Hi, balbes150, have a nice day! I'll follow your advice, thanks. By now, I'm investigating where & when messed configurations. When sure of something, I'll let you know. Thank you a lot by your commitment! Cheers, Francisco

Hi @jock and @fabiobassa, it's great that you guys support the TV boxes that Armbian won't, amazing! I have a HDMI stick with a RK3229 SOC, and this pathetic stick/board is a clone of a product with the brand "Any-cast", which at the same time is a clone of the Google Chromecast. I thought I had bricked it, but I wonder if there's anything to do with it? I didn't expect to run Armbian on it, but if I can ssh into it and run something like lighttpd, it will be already great I think the two soldered spot near the USB port is the UART serial, but I'm not sure I also managed to do rkdeveloptool db rk322x_loader_vxxx.bin , seems that the image is flashed successfully, but it still show "Maskrom" mode after I do rkdeveloptool ld But I'm afraid to say that I'm not too clear about what I am doing 😅 (Oh there is an external WiFi chip that is soldered to a USB cable, you can look at the last three photos)

Try this but not sure if it will work: git clone git@github.com:armbian/build.git cd build in file "packages/extras-buildpkgs/xf86-video-armsoc/debian/patches/0001-Add-sun4i_drmmode-driver.patch" change "sun4i-drm" to "sun4i_drm" ./compile.sh docker - "Show a kernel configuration menu before compilation" - button at the bottom "Show CSC/WIP/EOS/TVB" - "I understand and agree" - "cubietruck" - "current" - "jammy" - "Image with desktop environment" - "xfce" - choose what you need - ОК

No, because printenv sort variables by name. But in default_environment[] they are not sorted. For example distro_bootcmd= is after the scriptaddr= and preboot= is before arch=

Test version of the Armbian+EDK2 system (UEFI\grub) is available. The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard To use this option. Download the EDK2 image. https://github.com/jaredmcneill/quartz64_uefi/releases Unpack and burn to SD card. Download the Armbian image (kernel 6.1.0-rc7), For Station M2 https://disk.yandex.ru/d/C4Ql9v0BvhKPjQ For Station P2 https://disk.yandex.ru/d/5XuGz9WgF7FGCg unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options). Connect the SD card and USB drive. Turn on the power. If the system does not start immediately, go to settings and select the device to start. On the EDK2 boot screen, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel. If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch. If desired, you can place the entire system on an SD card, but additional steps will be required at startup. At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console. That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000. https://github.com/jaredmcneill/quartz64_uefi

The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard

I can recommend the USB Image Tool: Info-Page: https://www.alexpage.de/usb-image-tool/ Download at: https://www.alexpage.de/usb-image-tool/download/

@marsmars I found a fork of armbian build which it was complated eaidk 610 board: https://gitee.com/e190/armbian , i'm testing it now.

Rikomagic RKM V7 is an HDMI TV stick running Android 11 on a Rockchip RK3568 quad-core Cortex-A55 processor with 2GB RAM, 16GB flash, Gigabit Ethernet and WiFi 5/6 connectivity, as well as HDMI female port, and two USB ports. While the device could be used as a general-purpose Android mini PC, it is also suitable as a digital signage player with features such as RTC for time on/off control, screen rotation support, and a watchdog timer to ensure continuous operation even if a software crash occurs. Rikomagic RKM V7 specifications: SoC – Rockchip RK3568 quad-core Cortex-A55 processor @ up to 2.0 GHz with Arm Mali-G52 2EE GPU with support for OpenGL ES 1.1/2.0/3.2, OpenCL 2.0, Vulkan 1.1, 0.8 TOPS NPU for AI acceleration, 4Kp60 H.265/H.264/VP9 video decoding, and 1080p100 H.265/H.264 video encoding System Memory – 2 GB or 4 GB LPDDR4 Storage – 16 GB or 32 GB eMMC flash, [...] The post Rikomagic RKM V7 – A Rockchip RK3568-powered Android 11 HDMI TV stick appeared first on CNX Software - Embedded Systems News. View the full article

Does anybody have piclone available? I have tried many repos but it won't compile. I was able to install rpi-imager but I need piclone. Thanks!