failed to write register 1 on codec...

Yeah that looks ok. Can you add --verbose in the User Command Line Arguments: field in the IDE project setting and then run the project again? That may print some more useful details.

I mean, run the Bela program with --verbose and if it fails, see if you get some extra information

Hi,

I'm having the same issue with a CTAG FACE cape. Using the command

i2cdetect -y -r 2

I get the following result:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --     

I have received the FACE Cape recently, is this a hardware issue (cape damaged)?
(I have a Bela Cape with a BeagleBone Black working with no problems)

The codec for the CTAG cards is not on the I2C bus, so it's normal not to see it with i2cdetect. The CTAG cards need Bela image v0.3.6a or later. You can check the version of your image you are running by reading it above the prompt when you log into the board, or running grep v0 /etc/motd. If you have an older Bela SD card, you would have to update it to the latest release.

Once you have a suitable image, does the problem persist?

If it does, can you run ls /dev/spidev* on the board and post the result?
If you obtain /dev/spidev32766.0 /dev/spidev32766.1, then it means that the SPI devices used to configure the codec are correctly initialized. If you don't see those there, that would be very weird.

If the devices are listed, but the problem persist, then run board_detect on the board and post the result.

Then, run the Bela program that you are trying to start with --verbose (either from the command line, or adding --verbose to the "Command line options" in the IDE tab) and post the result of that.

I'm getting somewhat similar message on Bela Mini:

Error: unable to initialise audio codec
Error: unable to initialise audio
Makefile:613: recipe for target 'runide' failed
make: *** [runide] Error 1

It happens from time to time and power cycling (hard reset) usually helps.

I'm suspecting this might have something to do with two unusual usage scenarios I'm exercising:
1. I'm using the "hidden" analog inputs on PocketBeagle (as discussed in this thread https://forum.bela.io/d/1054-lots-of-inputs-what-are-my-options/22 ) and @giuliomoro mentioned that this method is "not real-time safe at all" - I thought it means that there's a chance of audio drop-outs at most, but maybe the method messes something up in the audio codec as well - could it be so?
2. In this particular Bela Mini I didn't solder the cape directly to the PocketBeagle - I'm using male and female pin stripes soldered to the cape and PocketBeagle, respectively, so in case of any damage it would be easier to disconnect them and replace the broken part. Could it be that the pin-to-pin connection is loose at some critical pins, which causes the issue?

I don't want to get too optimistic too soon, but it looks like I've found the possible cause of the issue - I was trying to read the "hidden" PocketBeagle analog ins, while reading the "regular" analog ins at the same time by using [bang~] and [snapshot~]. When using each set of analog ins separately, it didn't seem to cause much issue, but when I've used them together, this might have been a little too much for Bela, possibly. I've replaced [bang~] with [metro] and the issue dissapeared (for the time being, at least).