Jump to content

Updated images for FriendlyARM T4/M4/Neo4


Recommended Posts

- enabled Bluetooth

- align with latest upstream sources

- tested on M4 and T4 http://ix.io/1MYD

- updated repository

- clocked back to normal CPU speed 1.5/1.8Ghz to minimise thermal throttling

- added wireless drivers for 88x2bu

- updated wireless drivers for Realtek 8811, 8812, 8814 and 8821

- updated wireless drivers for rtl8188eus & rtl8188eu & rtl8188etv

- added latest Wireguard driver 



Link to comment
Share on other sites

Help us fund some #badass gear for our continuous integration build framework

Bluetooth sounds good, but really why cant we use armbian instantly as a microcontroller or the process seems much less spoken about than doing it on a teensy 3.2/3.6, for example I can have instant access to Bluetooth hc-05 wired to teensy 3.2 on power on but armbian takes boot time to access that.

Link to comment
Share on other sites

Built latest dev branch on Vagrant. No bluetooth :(


The hci_uart module is running, but it is not talking to any hci module.


The dmesg output seems to be missing lines along:

[    6.957330] Bluetooth: hci0: BCM: chip id 101
[    6.957644] Bluetooth: hci0: BCM: features 0x2f
[    6.961779] Bluetooth: hci0: BCM4354A2
[    6.961788] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[    7.965063] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0266

Maybe not that exact chip since the DTS in latest kernel talks about a bcm43438.


Did I miss something in my build command line? Am I missing some firmware?




Link to comment
Share on other sites

that is the cortex-a really is that like a specific cpu or all cortex's? the teensy is using the cortex-m4, but lets call it the noob tube because sounds like m4-carbine


aim high with the cortex-m4 carbine found in teensy 3.6


Link to comment
Share on other sites

2 hours ago, jerryg said:

Did I miss something


When we speak about updating images and its not specifically noted, it means for the (stable) legacy kernel builds. Support for development builds will exists when you will cover R&D and time lost on support in 100%. This means never.

If some feature doesn't work (we are aware for most obvious ones) in development kernels its expected. Develop that feature or submit a fix is the way to: https://www.armbian.com/get-involved We can only sponsor a fraction.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Create New...