ss4sh

Translation:

Dear ADI technical support:
I recently ran into a problem with SS4SH development and was hoping you could give me some answers.
I'm using SC594 and ev-somcrr-ezkit for audio development, and using the CCES framework provided by ADI
(called LibIntegrationExample). The debugging steps and hardware links are the same as the manual provided
by ADI. When debugging the program, the following printout sometimes appears, indicating that TWI read and write failed.
I've checked the hardware link and it works fine. There is only a clock signal but no data signal.
USBI also has a phenomenon that when the circuit board is plugged into USBI and the program is debugged,
it will get stuck in the ADC initialization area. Unplugged the USBI from the board and initialized the ADC,
but the program stopped waiting for SMAP. I suspect that plugging in the USBI might tie up some buses,
causing TWI communication to fail. What's wrong with USBI's JTAG port?
Looking forward to your reply.

尊敬的ADI技术支持：

我最近在SS4SH开发中遇到了一个问题，希望你能给我一些答案。

我使用SC594和ev-somcrr-ezkit进行音频开发，并使用ADI提供的CCES框架（称为LibIntegrationExample）。调试步骤和硬件链接与ADI提供的手册相同。调试程序时，有时会出现以下打印，表示 TWI 读写失败。我已经检查了硬件链接，它运行良好。只有一个时钟信号，但没有数据信号。

USBI也存在一种现象，即当电路板插入USBI并调试程序时，它会卡在ADC初始化区域。从电路板上拔下USBI并初始化ADC，但程序停止等待SMAP。

我怀疑插入 USBI 可能会占用某些总线，导致 TWI 通信失败。USBI的JTAG端口有什么问题？

期待您的回复。

Edit Notes
translated

[edited by: GenevaCooper at 10:07 PM (GMT -5) on 21 Nov 2023]

software

cces2.11.0 sigmastudio4.7

ss4sharc

sc594 ev-somcrr-ezkit

audio