ADAU1452 Sigma Studio TCP/IP Safeload write header problem
Hello,
I am working on a project where I use the ADAU1452 on a custom pcb. DSP is working fine controlled by USBi or local MCU (export from sigma studio project).
For my project I need to control the DSP over network. Therefore I implemented the necessary TCP/IP interface. That works well for a sigma studio block write.
I am figuring out some problems with the header when a parameter is send as a safeload operation.
The header for a write operation from Link to Wiki is as expected for the block write.
I would expect to receive the identical header in case of a safeload write, despite the safeload bit (actually the second byte) is high. The strange thing is, that in case of the safeload transfer the register address is not the address of the module which should be updated, but always the address of the safeload data register.
The address of the module apears a few bytes after the data bytes. The safeload has an additional data paket of 22 bytes. That makes no sense and I also didn't find any documentation for that.
See the attached screenshot where a gain is set to a new value and the output from the capture window and the received data over tcp are tracked.
Could you please share the correct structure for a safeload message over the ADAU1452 TCP/IP connection.
Kind regards,
Markus
Audio Signal Processors
adau1452
software
sigma studio 4.7
TCP/IP
SigmaDSP Audio Processors
SigmaDSP
Show More
Hello Markus,
I need a clarification. Are you using the TCP/IP control from the communications devices on the config page? Show us a screenshot of your configuration page.
That TCP/IP object is only for SigmaStudio to function over an internal connection. your MCU should function the same way to communicate to the DSP. Your MCU is the one that will connect to the network and then it will communicate to the DSP as normal. Safeload is the same either way.
So what is your hardware setup and are you trying to use SigmaStudio over the network or just trying to control the DSP over a network?
Dave T
Hi Dave,
yes, I use the TCP/IP block from the communications channels in the tree toll box. As I said, the general communication with the MCU is working (TCP --> I2C).
I now figured out, what the problem was:
The safeload is send as 2 separate transactions. I would have expected the safeload is send as one transaction with the safeload byte high to indicate the safeload.
The part of the data registers for the safeload is sent as one transaction. The safeload address and the num words are sent as one combined second transaction. Each transaction again has a complete write header.
That thing seems to be documented nowhere.
Kind regards,
Markus
Please log in to reply.