Hi all,

Recently my Bela CTAG Beast has stopped functioning properly. It boots and runs the IDE, but when I try to compile & run a project which I know definitely works, I get the following error message:

Unrecognized Bela hardware: is a cape connected?
Error: unable to initialise audio

Admittedly I updated the Kernel recently and had a slight boot problem which I solved but during the process to solve that issue, I had removed the CTAG Beast from the beaglebone board. Then re-attached it. It seems the headers have good contact and I've checked that there are no defects. But it seems since then I now have this error which I only realised today as I was trying to run some code. But didn't realise as I was able to connect through terminal etc.

I also went through the following procedure that is shown below to narrow down the issue at the time.

I used the following command: grep uboot_overlay /mnt/boot/uEnv.txt
I get the following output:

uenvcmd=echo loading ${fdtfile}; load mmc ${mmcid}:2 ${fdtaddr} boot/dtbs/${uname_r}/${fdtfile}; if env exists uboot_overlay_addr0; then setenv overlay ${uboot_overlay_addr0}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr1; then setenv overlay ${uboot_overlay_addr1}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr2; then setenv overlay ${uboot_overlay_addr2}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr3; then setenv overlay ${uboot_overlay_addr3}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr4; then setenv overlay ${uboot_overlay_addr4}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr5; then setenv overlay ${uboot_overlay_addr5}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr6; then setenv overlay ${uboot_overlay_addr6}; run bela_loadoverlay; fi; if env exists uboot_overlay_addr7; then setenv overlay ${uboot_overlay_addr7}; run bela_loadoverlay; fi; load mmc ${mmcid}:2 ${loadaddr} /boot/vmlinuz-${uname_r}; setenv bootargs console=${console} root=/dev/mmcblk${mmcid}p2 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet; bootz ${loadaddr} - ${fdtaddr};
uboot_overlay_addr2=/lib/firmware/BB-BELA-00A1.dtbo
uboot_overlay_addr3=/lib/firmware/BB-BELA-CTAG-SPI-00A0.dtbo

I then used the command:
grep -i "8dc\|828\|8d4\|82c\|8d8" /sys/kernel/debug/pinctrl/44e10800.pinmux/pins

Which results in the following:

pin 10 (PIN10) 44e10828 00000037 pinctrl-single 
pin 11 (PIN11) 44e1082c 00000017 pinctrl-single 
pin 53 (PIN53) 44e108d4 00000017 pinctrl-single 
pin 54 (PIN54) 44e108d8 00000017 pinctrl-single 
pin 55 (PIN55) 44e108dc 00000037 pinctrl-single

When I call ls /dev/spidev32766.0 I get the following:

ls: cannot access '/dev/spidev32766.0': No such file or directory

Lastly I call board_detect and the following comes up:

NoHardware

I have tried again to take the boards and put them back together with no luck. I've only had it since early March and it seems strange that after removing it the one time before that it would stop working. Any thoughts on how to proceed?