balbes150

@NicoDI checked the image of Buster is a Legacy from this link. https://users.armbian.com/balbes150/firefly_station_p1/Armbian/ I wrote it to the SD card and started it on P1 (with the NVMe module connected), everything starts and works. Yes, when running for 1 second, I see a "grid" on the screen (this is the u-boot splash screen) and the startup continues on without any problems. Which TV do you use ? Is it possible that unsupported data from the TV is received during the mode survey ? Try to force the permission in the extlinux.conf file (in the APPENDS argument).

I tested the latest versions from this link, booting from USB media works and all items work with DTB by default (except NVMe). By default, DTB does not support NVMe, if you need NVMe, you need to replace DTB with a second link. https://yadi.sk/d/TnDjwCsvG9-nuA?w=1 DTB for NVMe https://yadi.sk/d/UgUTCAw8mxijYw?w=1

Sent the PR for Legacy to the desktop branch. I checked the work of WiFi, analog sound and remote control on P1 and M1, everything works. Additionally, I removed useless elements from the kernel configuration that are only needed for smartphones and tablets.

I looked, I don't have such permission in the list of available ones. I checked on the 4K TV, there is also no such resolution.

I've already found a solution ... By the way, today almost all the hardware works for M1\P1 with Legacy core, I have to solve the issue with NVMe for P1, but I hope to spend more time porting the received settings to the main core - this is a higher priority for me.

I managed to get WiFi to work on P1 with the current kernel and configuration for rockchip64-legacy.

I am checking out new patches and now I can use the common kernel and configuration from rockchip64 to P1. I need time to check on the M1. I hope to get full support for M1\P1 with existing configurations ( may have to make small additions to them for modules, but this is not critical for other models).

You don't need to change anything. I found a solution-changed the patches so that can now use a common core for p1.

For P1, a different kernel is used (station-p1) and even when I put the kernel on freeze, it is still replaced with the one in the network reps (but in the network reps it is not correct). This breaks the whole system. IMHO the script should not depend on the kernel, from trying to install only the version registered in it.

When testing the latest legacy kernel on P1, I found that when installing the media script, it replaces the kernel. Have you linked the script to a specific kernel ?

@NicoD I uploaded new Legacy images 20210204 to the site with support for WiFi NVMe and analog audio for the P1.

We are waiting for a response from @Igor and @piter75 and other maintainers who are associated with Legacy on rk3399 (rockchip64).

the patches are ready. But I do not know if they need to be sent now (in the run-up to commit 21.02) ? https://github.com/150balbes/build/commit/20fc9ba46cf3a04dac81b0f159eb5f8bcc0addb4

Yes, I'm working on adding patches.

WiFi works if you use this image and replace the DTB in it with a new one. https://yadi.sk/d/gwkAREv3dVbd8A?w=1

@NicoD try this image, it's with a new kernel and DTB. https://yadi.sk/d/1vS1NGwoYnQWVQ?w=1

What version of the image are you using ?

In working condition, the top will be a radiator for the processor, and the NVMe module will be at the bottom, and there is enough plastic plate for protection, it can be installed with a blunt and a gap on the additional racks with which the hat will be attached. By the way, you can install a corner plate on these racks, on which to place the WiFi antenna mount.

The DTS patch is sufficient to enable NVMe. For the rest of the elements-I'm just now preparing patches for the current Legacy kernel (rockchip64), which is used to build the version for P1 in the official GIT.

@NicoD Can you try with the current version of Buster-legacy this DTB ? With it, you should have NVMe. There will also be a device for analog sound, but without patches in the core itself, the sound does not work (in the new image with patches, the sound and remote control work). https://yadi.sk/d/VnNZwpT0Sfbf8Q

I meant the release of a new model P1 (if the manufacturer releases one), in which the M2 connector will be built into the main board (for example, as it is done on the Firefly rk3399 or on the NanoPC T4). As for the photos, this is @NicoD, we have a specialist, I hope he can make them. The good news is, I'm currently testing a new "old " kernel (legacy) that runs NVMe, analog audio, and remote control on the P1. I hope to upload a new Buster-legacy image with this core to the site soon. By the way, do I need to build more versions of Focal \ Bullseye, etc. with this kernel ? https://yadi.sk/i/jICyz61XLYsoGw

The ideal solution would be to place the NVMe connector on the main board itself. The main board itself is large and has enough space to accommodate the M2 connector.

If @JMCC adds a script for the main kernel, then any version can be used. Personally, I like the latest Hirsute. I am testing the latest versions (Hirsute and Sid) and see a significant improvement regarding Focal and Bullsey. As far as I know (when building LE with the main core), the main core now has all the components for HW. I am quite satisfied with the main core, even without HW, it is enough for full-screen video in 1080p mode (this is the main mode I use, 4k is too small for the desktop). I regularly update all the latest images on the site http://bbs.t-firefly.com/forum.php?mod=redirect&goto=findpost&ptid=2781&pid=13344&fromuid=636914 I don't have N2+. I try not to release versions for hardware that I don't have (this creates a lot of problems for me, users ask questions and describe problems, but I can't test and fix them, so I avoid creating such variants).

The old LEGACY kernel does not see NVMe. Need to understand the configuration and DTS. But there's no time for that yet.

I checked it again now. NVMe works with all ArmbianTV and Armbian images with the main core. I didn't check the legacy kernel. Here is a screenshot. Please note, the hat is very sensitive to the contact fit, if you put it on too tightly, NVMe does not work. You need to slightly raise the hat over the main board, so that there is no contact with other elements. https://yadi.sk/i/cWmayDV-hH0D5Q Disk /dev/mtdblock0: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk2: 29.12 GiB, 31268536320 bytes, 61071360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x72dd71e9 Device Boot Start End Sectors Size Id Type /dev/mmcblk2p1 30720 1038335 1007616 492M c W95 FAT32 (LBA) /dev/mmcblk2p2 1040384 61071359 60030976 28.6G 83 Linux Disk /dev/nvme0n1: 232.91 GiB, 250059350016 bytes, 488397168 sectors Disk model: Samsung SSD 970 EVO 250GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x95cda040 Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 488396799 488394752 232.9G 83 Linux Disk /dev/sda: 14.73 GiB, 15795748864 bytes, 30851072 sectors Disk model: Transcend 16GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xd59e383c Device Boot Start End Sectors Size Id Type /dev/sda1 32768 1081343 1048576 512M e W95 FAT16 (LBA) /dev/sda2 1081344 30542559 29461216 14G 83 Linux armbianmonitor https://yadi.sk/d/iw5-pIbZWEucmQ