You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to get ledscape to work on the Beaglebone green wireless.
(It's a BB with 2 seeed connectors plus wifi/Bluetooth - minus the Ethernet and HDMI)
I used the lts kernel and debian jessie (since the BBG-W isn't supported on earlier builds)
update_kernel.sh --bone-rt-kernel --lts-4_4
I also used
bash patch_dts.sh /boot/dtbs/$(uname -r)/am335x-bonegreen-wireless.dtb
to generate a suitable dtb
This nearly works - but I get the following error message :
pru_gpio:173: /sys/class/gpio/gpio26/value: Unable to open? No such file or directory
As far as I can tell this is because the BBG-W steals 2 gpios to enable/disable the Bluetooth and wifi chips - the schematic seems to indicate they are: GPIO0_26 (WIFI) and GPIO1_28 (BT)
I don't need 48 lines - is there an easy way to reduce the GPIO needs and exclude these 2
from LEDScape's use? (Say disabling a PRU?)
The text was updated successfully, but these errors were encountered:
I've been trying to get ledscape to work on the Beaglebone green wireless.
(It's a BB with 2 seeed connectors plus wifi/Bluetooth - minus the Ethernet and HDMI)
I used the lts kernel and debian jessie (since the BBG-W isn't supported on earlier builds)
update_kernel.sh --bone-rt-kernel --lts-4_4
I also used
bash patch_dts.sh /boot/dtbs/$(uname -r)/am335x-bonegreen-wireless.dtb
to generate a suitable dtb
This nearly works - but I get the following error message :
pru_gpio:173: /sys/class/gpio/gpio26/value: Unable to open? No such file or directory
As far as I can tell this is because the BBG-W steals 2 gpios to enable/disable the Bluetooth and wifi chips - the schematic seems to indicate they are: GPIO0_26 (WIFI) and GPIO1_28 (BT)
I don't need 48 lines - is there an easy way to reduce the GPIO needs and exclude these 2
from LEDScape's use? (Say disabling a PRU?)
The text was updated successfully, but these errors were encountered: