balbes150

Do you read the instructions carefully ? rtk_hciattach autorun has already been added to these images, but you must turn on the bluetooth manager yourself (for those who need it) and restart the system so that BT will automatically start.

The link you provided is intended for other purposes. See the general directory for M1 , subdirectory 20220311-legacy. https://disk.yandex.ru/d/vzFjfl4AwaQ5VQ

The described steps are intended for the device, as it leaves the factory, multi-boot is not activated in the factory firmware, you activated it yourself. You have already changed the state of your device (activating multi-boot changes the contents of eMMC and SPI, and changes the entire logic of starting systems from external media, not allowing you to start systems with a new format). In fact, the primary "activation\inclusion of multi-boot" is the transfer of the "old" (which does not know how to launch new systems from external media) version of u-boot to SPI. Until multiloading is fixed to work with new launch formats, multiloading needs to be disabled. I have already written to the Firefly developers what needs to be fixed in the multiload so that it works with all systems (with new and old formats). The correction is simple (just a few lines), but so far there is no answer from them.

legacy = kernel 4.4 edge = kernel 5.16 support BT for m1 only legacy (4.4)

ArmbianTV=Armbian(oficial)+additional improvements, specifically for these models (i.e., in fact, it is a slightly improved or newer version than the official image) I have already answered above what is the difference. If you only need the official version, you only need to use the official download page. Have you carefully studied the information on the official download page ? There is an order of steps that need to be done once with the official firmware version of StationsOS (update u-boot as the device leaves the factory) to run Armbian. At the moment, the standard StationOS firmware cannot work with the latest versions of Armbian with support for installation in eMMC. If you have already changed something in the standard firmware (the contents of the u-boot in eMMC or in SPI), there is no guarantee that everything will start and work correctly.

What is the question ?

add

Version 20220311-legacy for Station M1, which adds support for BT. To turn on BT, after the initial system startup and logging in to XFCE, turn on BT in the bluetooth manager and restart the system. After that, you can connect BT devices.

Did I understand correctly that when using a script with a fixed parameter FIRSTSECTOR=32768, the installation in eMMC works correctly (the system works normally from eMMC) ?

no, it won't help, these are completely different kernels with a different driver organization.

for P2 https://disk.yandex.ru/d/neKXsYolKXgLzg Can you show the contents of nand-sata-install from these images ? I have a suspicion that there is incorrect information for creating partitions. Try replacing nand-sata-install with the version from the working image.

copy /lib/firmware/rtl_bt/rtl8723ds_config.bin to /lib/firmware/rtlbt/rtl8723d_config /lib/firmware/rtl_bt/rtl8723ds_fw.bin to /lib/firmware/rtlbt/rtl8723d_fw Enable Bluetooth Manager run rtk_hciattach -n -s 115200 /dev/ttyS2 rtk_h5

A test version in which I added some elements for BT. BT doesn't work on my instance, maybe others will have a different result. Also included in the image is a utility for managing BT rtk_hciattach -n -s 115200 /dev/ttyS2 rtk_h5 https://disk.yandex.ru/d/yY2wu1u4p7j4CQ

Try installing in eMMC using these images. Please note that you should not do any manual operations with eMMC, use only the regular installation procedure from armbian-config (choose the ext4 file system). https://disk.yandex.ru/d/WLXChayq0xf91A

If you have erased the eMMC, you do not need to run the u-boot update. Judging by the log, you installed a very old version of Armbian, where did you get it from?

You need to remove the multi-boot from SPI (return the use of u-boot from eMMC) and install the update for u-boot in eMMC (according to the instructions that are on the Armbian image download page).

The current version of Firefly multi-boot (which is installed in SPI) uses an outdated startup scheme that cannot work with new versions of Armbian. I am communicating with the Firefly developers to fix this issue. Additional settings are needed to get a working image. In the near future I plan to add CSC settings for quartz64. This hardware is not supported and will not work. Have you updated u-boot according to the instructions for Armbian?

Which model do you want to build an image for ?

https://en.t-firefly.com/product/industry/itx3588j

I will try to add changes, but only in two weeks when I get back to work.

alas, I will not be able to check this, my M1 does not give a working BT in any variants of systems and DTB.

I checked the StationOS version, BT also doesn't work for me. Strange. maybe my version (1GB RAM and 8GB eMMC) is faulty. Try copying firmware files from StationOS to Armbian. A new version of the P1 pro has been released. A power button has been added, which makes the P1 pro a ready-made solution as a mini PC. https://www.stationpc.com/product/stationp1pro

Added version 20220220-5.16 for Station M2 with NVMe and Wifi support

It's strange, I downloaded the latest official version of Ubuntu for testing, but I don't have BT on it either. Does anyone have BT on any system for M1?

I haven't checked BT for a long time. Now the check will be in a couple of weeks.