Post Go back to editing

ADAU1701 and SigmaTcp - Header mismatch

Hey All,

I was trying to configure an ADAU1701 connected to a raspberry pi (over an i2c bus, running Raspbian) using SigmaTcp. Unfortunately, I was unable to do that in the first attempt. I analyzed the TCPIP packages sent by SigmaStudio using wireshark and I noticed that the header was different from the one that SigmaTcp was waiting. Sigma tcp waits for a 8 bytes header, with length in the bytes 4 and 5, and addr in the bytes 6 and 7. SigmaStudio sends a 10 bytes header with length in the bytes 6 and 7, and addr in the bytes 8 and 9. After some changes in function handle_connection on sigma-tcp.c, I was able to control the chip over a TCP/IP connection. 

Is there a different version of sigma tcp to be used with ADAU1701? I searched in this forum and couldn't find anyone with the same problem, so I decided to post this. 

Thanks!

Lucas@

Parents
  • I did study the C code for the 145x/146x family as i will use it for raspberry PI

    many bugs and overly complicated/obfuscated, must be very unstable. (IMHO)

    the oposite of KISS

    I will rewrite it , and add  SPI support,

    anyway,  to return to the original topic.

    it cannot be very hard to reverse engineer the 1701 format, can it ?

    i assume it will resemble at least the 145x format

    if you just run the code you can see the incoming packet and analyse it, or run wire-shark on it.

Reply
  • I did study the C code for the 145x/146x family as i will use it for raspberry PI

    many bugs and overly complicated/obfuscated, must be very unstable. (IMHO)

    the oposite of KISS

    I will rewrite it , and add  SPI support,

    anyway,  to return to the original topic.

    it cannot be very hard to reverse engineer the 1701 format, can it ?

    i assume it will resemble at least the 145x format

    if you just run the code you can see the incoming packet and analyse it, or run wire-shark on it.

Children
No Data