I forgot to mention: Is VNC disable or enable on your zynthian? VNC, specially for ZynAddSubFX engine is really CPU-hungry.
Hi @jofemodo
I was running now the command in the terminal and could not see any stalling of the CPU nor did I observe any temp increase. Then I decided to run Zynthian with that one track, also opened the VCN monitor and kept refreshing the home screen to observe the temperature.
I captured one of these dropout moments and did a screen recording.
I will disable VNC now and run another test series.
I remember, that I had VNC disabled previously, but will do this again now and share the result.
Here is the screen capture of the moment when the system freezes.
zynthian terminal monitoring
I had the terminal window running with your provided command before that and did not see any dropoutsā¦ all was just running smoothly.
This becoming even more interesting!!! It doesnāt looks CPU related.
Could you check if the UI is responsive during the āaudio dropoutā? If yes, i would bet all to āsound deviceā. Are you still using the NI-Audio for the tests?
Regards,
VNC is disabled now and another dropout just happened.
Yes, I am using the NI MK2 again.
I will try at the next dropout if the UI still responds.
I just had an ideaā¦ I have a small Yamaha mixing desk and it has a USB, so it can run as an audio device, and it has its own power, so I will also test this after the UI test.
I think I remember how to add the audio interface by checking the name in alsamixer in the terminal and add this to the custom audio hw:DEVICE
Feedback is coming soon.
Donāt complicate things. Use the internal RBPi audio. Itās not the best quality, but it should work without problems in a bare-bones RBPi. It would serve as a diagnostic test.
just had a dropout and YES, the UI is still responsive and I can navigate the menu.
Okay
I just thought this is one of the last options. I only used the MK2 as an external since I have the Pi and the internal also does the dropout.
So, what are we doing next? 
And disconnect everything from the RBPi. Leave it as alone as possible, including ethernet.
doneā¦ still, the dropout happens.
Please, send a photo of your latest bare-bones setup.
ā¦Pi & touchscreen nothing else left to have connected.
The power connection is a simply USB A to USB C cable plugged into a 3-ampere power supply. The strongest I have with 5V output.
I even reused the coolers from the Pi on the screen board. It didnāt get hot, but I thought it canāt harm.
I donāt even close the lead of my box anymore for all the tests. Added air holes underneath the Pi for better air circulation and the box is getting more holes in the back, but this error has nothing to do anymore with cooling. The CPU temperature is fine now with the passive cooler. No matter if in the box or not.
I tried also the Yamaha USB mixer (MG10XU)ā¦
Same storyā¦ after a while a dropout happens.
CPU is at 41Ā°C and the case feels not hot to the touch, so sensor seems to work.
Is there anything left to try now?
I see you are driving the touch device using the I2C interface. I donāt see a problem on this, but itās something āspecialā and you should have explained before.
BTW, what display are you using?
Thanks!
OK! I see itās a RBPi display, first version. Could it be related? Why is not driving the touch thru the flat cable as they normally do? And then, why the INT pin is not connected?
Regards,
is there a terminal command to give us the exact name of that display?
It is a 7inch touch screen and I did nothing with l2C, but I see that these MCP stuff keeps popping up now. I have no idea about that. The only thing I do is selecting a display.
this list of MCP stuff I donāt understand. I think I have never had that previously. It showed up after the new Zynthian update.
Here are my settings:
These are all standard settings.
I have no idea about the meaning of the l2C MCP stuff.
Kit is set to Customā¦ nothing else there to show.
Hardware Options are empty too.
The I2C report is clearly not normal. It should be empty but itās full of shit! Could you disconnect the 2 I2C wires from the display?
I just pulled out the wires red, orange, yellow and black - not the flat band cable.
l2C list is now empty.
1 Like
But my friend! This is the first thing you should have reported!! And this is probably the source of all the problems you have. Letās see. Why did you connect the i2C pins of your display? And more important ā¦ why didnāt you explain to us such an important thing? OK! In fact, itās our fault because the first thing we should have asked for is a screenshot from your webconf dashboard and we didnāt !! 
1 Like
Could you check that:
- touch is working fine
- the dropouts have vanished
Thanks!