Connecting SigmaStudio with TCP/IP
Thread Summary
The user is facing difficulties testing a design with a microcontroller and ADAU1761 due to heavy I2C bus usage. The engineer provided TCP/IP communication details for writing data to the ADAU1761, including the control byte, message length, I2C chip address, and data address. The user requested clarification on the 0x0A and 0x1B records, which are still under investigation by the software team.AI Generated Content
Hello,
I’m working on a design containing a micro controller (with a Ethernet connection) and a ADAU1761.
Testing is a bit difficult for me, I think because my I2C bus is used a lot. Maybe the USBi interface don’t like that…
But I saw in the new 3.7 version that there is an option to chose for a TCPIP connection. I found that the connection is made to localhost port 8086. I logged the information that’s send from sigma studio.
The format for sending data is almost clear for me. How reads work and other options is’nt clear. Is it some where documented? Or is there some other option available that enable me to send the data using my micro controller (and reading data back, normal configuration is implemented in my program and works fine).
0x1B 0x00 0x40 0x06 0x00 0x01 0x01 0x01 0x00 0x00 0x01 (unknown first record)
0x09 0x00 0x09 0x01 0x00 0x01 0x40 0xEB 0x7F
0x09 start
0x00 0x09 record size
0x01 ?
0x00 0x01 number of bytes to write
0x40 0xEB address
0x7F byte to write
… data …
0x0A 0x00 0x08 0x01 0x00 0x06 0x40 0x02 (last unknown record, wait for a ready signal?)
Lukas
Audio Signal Processors
processors and dsp
SigmaDSP Audio Processors
adau1761
Processors and Microcontrollers
Hello,
I was able to get the documentation about TCP/IP from the software team.
Here is the map for ADAU1761 Read:
/************************
* Package Response MAP
* byte[0] -> control (0xb)
* byte[1] -> msg length hi
* byte[2] -> msg length lo
* byte[3] -> status (0 for Success, x for failure)
* byte[4 -> n] -> data received
* ************************/
The WriteData is:
byte[0] -> ((byte)0x09); //control
byte[1] -> Total Message length Hi
byte[2] -> Total Message length Lo
byte[3] -> I2C chip address
byte[4] -> data length hi
byte[5] -> data length lo
byte[6] -> address hi
byte[7] -> address lo
I hope this helps.
Hello BettG
Thank you, its very helpful for me. Is it also possible to tell me what the 0x0A and 0x1B records mean/contain?
I expect 0x0A is a read on witch I must respond with a response 0xB?
Hi LsH,
I asked the software team about this, but no response yet. I will let you know what I find out.
This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.
Thank you,
EZ Admin
Please log in to reply.