gpio-issue solved so far…gpio was blocked by activated i2c1…so if the special-function is enabled in dts, the direct gpio-access is blocked
root@bpi-r64:~# GPIO_NO=$((409+56))
root@bpi-r64:~# echo $GPIO_NO
465
root@bpi-r64:~# echo $GPIO_NO > /sys/class/gpio/export
root@bpi-r64:~# echo out > /sys/class/gpio/gpio${GPIO_NO}/direction
root@bpi-r64:~# echo 1 > /sys/class/gpio/gpio${GPIO_NO}/value
root@bpi-r64:~# echo 0 > /sys/class/gpio/gpio${GPIO_NO}/value
my led goes on and off
root@bpi-r64:~# apt-get install bluez
...
root@bpi-r64:~# uname -a
Linux bpi-r64 4.19.0-r64-main #70 SMP PREEMPT Sat Feb 9 09:53:04 CET 2019 aarch64 GNU/Linux
root@bpi-r64:~# dmesg | grep hci0
root@bpi-r64:~#
root@bpi-r64:~# bluetoothctl
[NEW] Controller 00:00:46:76:22:01 bpi-r64 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:00:46:76:22:01 Discovering: yes
[bluetooth]# [ 134.372291] Bluetooth: hci0: last event is not cmd complete (0x0f)
...
[CHG] Device B4:9D:0B:5F:2A:B9 Name: Aquaris X5 Plus
...
[CHG] Device B4:9D:0B:5F:2A:B9 ServicesResolved: yes
[CHG] Device B4:9D:0B:5F:2A:B9 Paired: yes
Pairing successful
[CHG] Device B4:9D:0B:5F:2A:B9 ServicesResolved: no
[CHG] Device B4:9D:0B:5F:2A:B9 Connected: no
[bluetooth]# [ 207.332516] Bluetooth: hci0: last event is not cmd complete (0x0f)
[bluetooth]# exit
[DEL] Controller 00:00:46:76:22:01 bpi-r64 [default]
root@bpi-r64:~#
except of the event-info/warning all is good now
Bluetooth: hci0: last event is not cmd complete (0x0f)
the change seems to create problems detecting mmc-rootfs
sometimes i get this message and boot-prcess hangs
Waiting for root device /dev/mmcblk0p2...
@linkerosa have you an idea regarding preloader and emmc?