About I2C function calling!

Discussions about USB Audio on XMOS devices
LeonYu
Newbie
Posts: 1
Joined: Wed Oct 08, 2025 2:57 am

About I2C function calling!

Post by LeonYu »

Dear team:
Now I am using XU316-QF60B on my project,instead of XU316-TQ128 on EVM 316-MC-AB . Now I meet the following questions need your help:

1. If I run the modified FW on EVM, it can run well (of course I keep the IO port settings and power control for EVM). But I changed IO ports including I2C port for my hardware, when call function "WriteRegs", xrun will report the following message:

Code: Select all

    xrun: Program received signal ET_ECALL, Application exception.
               0x00080fe0 in i2c_reg_write (device_addr=132 '\204', i2c=<optimized out>, reg=<optimized out>, data=<optimized out>) at 
               C:/Users/Administrator/sw_usb_audio_sw_9_1_0/lib_board_support/lib_board_support/src/boards/xk_audio_ch_316_mc_ab/xk_audio_ch_316_mc_ab.xc:155  
The difference between my board and the EVM, the I2C pull up resistor is 2.2k ohm, the EVM is 4.7k ohm.

2. I select an audio codec which only have one slave address, so I need another 3 groups of I2C master(EVM is using one group of I2C), how can modify the reference code?

Thans for your support!
User avatar
Ross
Verified
XCore Legend
Posts: 1283
Joined: Thu Dec 10, 2009 9:20 pm
Location: Bristol, UK

Post by Ross »

Please let us know what version lib_board_support you're using.

Its likely an assertion raised due to a detected i2c issue.
Technical Director @ XMOS. Opinions expressed are my own