Bluetooth UUID as AA:AA:AA:AA:AA:AA on Rpi 4

Troubleshooting
1

Hi, just had a clean install, where im trying to use the pi as a bluetooth PAN.
However, the uuid of hci0 is being shown as AA:AA:AA:AA:AA:AA - an obvious error.

~# hciconfig 
hci0:	Type: Primary  Bus: UART
	BD Address: AA:AA:AA:AA:AA:AA  ACL MTU: 1021:8  SCO MTU: 64:1
	UP RUNNING 
	RX bytes:1478 acl:0 sco:0 events:88 errors:0
	TX bytes:2534 acl:0 sco:0 commands:88 errors:0

This means that when setting bluetooth up, it is not discoverable. I have not tested pairing as the client, but I assume this would fail also.

In my troubleshooting, the error seems to stem from the hciattatch service, regarding

Sep 03 00:33:37 ToshiProto btuart[280]: Cannot open directory '/etc/firmware': No such file or directory
Sep 03 00:33:37 ToshiProto btuart[280]: Patch not found, continue anyway
Sep 03 00:33:37 ToshiProto btuart[280]: bcm43xx_init

when trying to modprobe this module and restart the respective services, the initialization times out through the service, and the command

hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -

also times out.

Im at a bit of a loss, as all I can find regarding the issue are old threads about a borked bluez upgrade.

I would really appreciate some help here, as ive just spent a good day 'o this and im at a loss on what else to try - im not all that familiar with the hci system.

Any ideas?

(also, doubt its useful but DietPi version is v7.5.2, bluetoothd -v gives 5.55)

2

Just wanting to give this a quick bump, im really at a loss here.

3

Gonna give one more bump!

4

I cannot imagine that this problem is caused by DietPi, as the official packages are used in this case. Have you tried another SD card with debian to verify that it works indeed?