SigmaStudio crashes when using TCP/IP communication

To troubleshoot, I tried downgrading to SigmaStudio v4.5.

I have also tried creating a new project from scratch.

I have the same problems.

This thread seems to be related.  Has tremendous details:

[BUG REPORT] Sigma Studio TCP-IP read from DSP ( With Temporary Solution ) - Q&A - SigmaDSP Processors & SigmaStudio Dev. Tool - EngineerZone (analog.com)

Answer: I believe the raspberry Pi is disrupting communication with the SigmaDSP chip, and the fault is not necessarily with the SigmaStudio TCP communication.  There might be other problems left to uncover, and the SigmaStudio crashing to desktop could be investigated.

Here are steps to reproduce my findings:

Attach the SPI programmer EVAL-ADUSB2EBZ to the 6pin header on the Hifiberry board called "programming".  Pin 1 is towards the amplifier chips.  Attach the raspberry Pi to the Hifiberry board.  Power up the boards with power at the barrel connector.  Open SigmaStudio (I'm using v4.7) and create a simple project with some kind of read-back function, like a white noise generator connected to a VU meter.  Link compile download.  In SigmaStudio, I would see the VU meter working correctly for about 5-10 seconds and then it will freeze.  The SigmaDSP chip will continue functioning but I am unable to interact with the chip using the SPI programmer, either sending or receiving data.  This is exactly the same behavior I was seeing with the TCP communication method earlier.

Remedy: remove power from the boards, disconnect the Pi from the Hifiberry, and power on the Hifiberry board.  Follow the same steps as above.  I am now able to interact with the SigmaDSP chip reliably, and communication does not fail.

I believe the Pi is doing something that disrupts the SPI communication with the SigmaDSP chip which would explain why I lose communication with both the TCP and the SPI programmer methods (and why both methods seem to fail in the same way).  I do not know what the Pi is doing and have not investigated, but this is the next step I would take.

Note: this behavior occurs with both the Hifiberry OS and the official/vanilla Raspberry Pi OS.