balbes150

New version of images for rk3188 \ rk3288. New kernel 5.10.25.

I'm just starting to get into the specifics of Allwinner, so my interests in this area are limited to H6 and H5 (in the future, H616). A year ago, I was interested in the possibility of acquiring PinePhone and PinebucPro, but due to the peculiarities of delivery in my area, Pine64 politely explained that this is not possible (I have no complaints about them, this is their business, they decide how to run it).

Write in detail what steps it does. If the device is supported, you don't need to send anything to others. If it is not supported, no sending to others will help, they will not be able to do anything.

I'll try adding them, but I can't guarantee that it will work.

Update to version 20210319. Using kernel 5.10.24. Added support for Firefly-rk3399 in station-p1 images (for proper operation, you need to configure DTB in extlinux.conf). With the correct DTB setup, the HDMI audio LAN WiFi BT works in kernel 5.10. In kernel 4.4 worck remote control and analog sound.

You can try using the latest kernel 5.12 or 5.11. Maybe there will be better support. You don't need any patches for this, just build the kernel on the Jetson Nano itself and copy it with the Initrd rebuild and the installation of modules.

Please contact the authors of these crafts. The topic is closed.

Unfortunately, I can't test the M2 operation. I don't have an adapter to connect the NVMe module to the board. Without an adapter, it is impossible to connect a standard NVMe module (the USB connectors interfere, they are double height), you need to look for a short version of NVMe, but I have not seen such for a long time. But I do know that the latest versions of ArmbianTV run perfectly from the SD card (i'm tested). The kernel versions 4.4 and 5.10 work. The composition has a DTB specifically for firefly-rk3399 (although with DTB for rk3399-pc-plus, everything works the same, except for BT and analog sound). I hope to send a patch for the main core to the official build system soon, this will allow the official Armbian versions on Firefly-rk3399 to work properly.

I have no idea, I haven't checked.

I received Fyrefly samples today, including Firefly-rk3399. The first tests showed. Yes, indeed, the official images for this model from the official download page (I have only checked the main kernel so far) do not work, i.e., as described earlier, u-boot starts, transfers control to the kernel, and that's the end of it. But there is also good news, I checked the image from Firefly-Station P1 and it worked perfectly without any additional settings. I.e. I wrote the image to the SD card, connected the SD card to Firefly-rk3399, turned on the power and the system automatically started. Works LAN HDMI Wifi HDMI sound. BT does not work and instead of shutting down, the system restarts. I briefly checked the system with the 4.4 kernel (for P1), the main components work, including analog sound. I checked the launch of Libreelec - the system starts and works with HW.

I haven't received any such messages. But perhaps someone is systematically trying to find passwords to all known accounts with the necessary rights.

Send PR

That is, did I understand correctly that it makes sense to send a PR ?

@IgorQuestion. does it make sense to send a PR for CSC to Jetson Nano right now, or is it still enough to have test builds in my catalog ?

I checked the native build of the image works on the Jetson Nano itself. But while there is no fan control in the main core, I had to use a USB fan for cooling (all resources are used during the build

New version of Armbian 20210311. Based on the main core 5.10.23. Now anyone can build their own version of Armbian for Jetson Nano without an external PC, the entire process is completely performed on the Jetson Nano itself.

Good news. Thanks to the work of many, there is now a real opportunity to run the Armbian system with the main core on Jetson Nano, and more importantly, it is easy to integrate the image build process into the official GIT Armbian. In the near future, I plan to post ready-made images with the latest kernel 5.10.22 on the download site. To run them, you need to update u-boot to Jetson Nano. This is very easy to do, just run the latest official version of Ubuntu for Jetson Nano from the SD card, it will update itself in SPI (?) u-boot to the latest version (2020.04), after that you can run Armbian from any SD card or USB media. The new u-boot supports automatic system startup from both media or over the network. Also, now you can build an Armbian image for Jetson Nano yourself, easily build the latest kernel with the necessary options, etc. https://users.armbian.com/balbes150/ https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ https://disk.yandex.ru/d/XBRXnig7F1M4rw?w=1

I plan to open a new topic in the Board Bring Up section dedicated to Armbian support on Jetson Nano. Now there is a lot of interesting information.

Good news. You can now use the main core to run on Jetson Nano. I have already added the necessary data to the build system and you can build an image for Jetson Nano using the official sources of the main core. U-Boot 2020.04-g6b630d64fd (Feb 19 2021 - 08:37:46 -0800) SoC: tegra210 Model: NVIDIA Jetson Nano Developer Kit Board: NVIDIA P3450-0000 DRAM: 4 GiB MMC: sdhci@700b0000: 1, sdhci@700b0600: 0 Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 338 bytes read in 22 ms (14.6 KiB/s) 1: Armbian Retrieving file: /boot/uInitrd 11330177 bytes read in 512 ms (21.1 MiB/s) Retrieving file: /boot/Image 31306240 bytes read in 1364 ms (21.9 MiB/s) append: root=UUID=de820d8a-ca8e-4b1a-8e96-ce586b2422f3 console=ttyS0,115200 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian Retrieving file: /boot/dtb/nvidia/tegra210-p3450-0000.dtb 42868 bytes read in 33 ms (1.2 MiB/s) ## Loading init Ramdisk from Legacy Image at 83200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 11330113 Bytes = 10.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 Using Device Tree in place at 0000000083000000, end 000000008300d773 copying carveout for /host1x@50000000/dc@54200000... copying carveout for /host1x@50000000/dc@54240000... Can't set DT prop /bpmp/carveout-start: FDT_ERR_BADOFFSET Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd071] [ 0.000000] Linux version 5.10.22-jetson-nano (root@vbox) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-re1 [ 0.000000] Machine model: NVIDIA Jetson Nano Developer Kit [ 0.000000] efi: UEFI not found. [ 68.257514] systemd[1]: Starting Create System Users... [ 68.270413] systemd[1]: Mounted Kernel Configuration File System. jetson-nano login: root (automatic login) _ _ _ _ | | ___| |_ ___ ___ _ __ | \ | | __ _ _ __ ___ _ | |/ _ \ __/ __|/ _ \| '_ \ | \| |/ _` | '_ \ / _ \ | |_| | __/ |_\__ \ (_) | | | | | |\ | (_| | | | | (_) | \___/ \___|\__|___/\___/|_| |_| |_| \_|\__,_|_| |_|\___/ Welcome to Armbian 21.05.0-trunk Focal with Linux 5.10.22-jetson-nano No end-user support: built from trunk System load: 74% Up time: 1 min Memory usage: 6% of 3.80G IP: Usage of /: 28% of 15G [ General system configuration (beta): armbian-config ] Last login: Wed Mar 10 08:41:35 UTC 2021 on tty1 New to Armbian? Documentation: https://docs.armbian.com Support: https://forum.armbian.com New root password: ****** Repeat password: ****** Choose default system command shell: 1) bash 2) zsh Shell: BASH Creating a new user account. Press <Ctrl-C> to abort Desktop environment will not be enabled if you abort the new user creation Please provide a username (eg. your forename): user Create password: ****** Repeat password: ****** Please provide your real name: User Dear User, your account user has been created and is sudo enabled. Please use this account for your daily work from now on. Now starting desktop environment...

The version of the image you are using is not official and there are no kernel updates for it via network repositories. You can try to build the latest version of the kernel yourself (directly on the device itself from under the Armbian system) and manually install it.

In order to practice creating and working with a cluster, you can use any "junk". But for real work (when the result is more important than the cost), all the "constructors with one wire" assembled from mismatched components "on the knee", always cost more than a proven solution. It is important to set your priorities correctly. To create software (which will work in the cluster cells), a minimum developer fee is used with one module that is planned to be used in the cluster. The price of such a developer kit (fee + module) is not high and you can have several such development kits for all project participants (developer, tester, debugger, etc.). And a full server (a set of servers that can consist of more than one physical server) is used at the final stage of launch when the entire cluster system is put into operation.

If the cluster is needed for real productive work, and not for "try and practice". Need to look at the correct configuration of the entire complex. Required elements. 1. High-quality metal housing for use in racks. The metal of the housing shields the interference, ensures proper cooling and stability of the parameters. 2. Power supply unit. There is not even anything to discuss here, only a high-quality product and it is very desirable with hot replacement and redundancy. If the cluster is running, it is not allowed to interrupt it due to a power drop. 3. Smart cooling system (passive radiators on the elements and a general active fan system with control sensors). It is a "system", and not a set of mismatched fans with difficult docking and control. Independent hardware management. 4. Easy extensibility and scalability (different modules by performance and configuration from minimum to maximum). And the free build-up (addition) of modules without complex reconfiguration of the entire system. Firefly R1 R2 servers are well suited for these requirements. But this is for those who really understand that they need the maximum cost / result ratio from the cluster system. For those who only want to practice and learn the principles-you can use any model, up to the simplest TV boxes.

If you don't need the case and you are ready to add a radiator yourself, you can look at the clean board that is used in the M1. I gave your information to Firefly representatives. https://www.firefly.store/goods.php?id=99

What mistakes are we talking about ?

I don't do Docker support, and I have no idea what it takes.