ProtoDAC TDA1387 X8 project

[varunach]

Couple things:

1. Linux manages all network connections way before moOde even starts. All moOde does during its startup sequence is check for an IP address assignment.

2. WiFi suddenly dying or becoming unreliable can be a symptom of interference. The infamous HifiBerry issue from back in the day where one of its clocks generated RFI that interfered in the 2.4G WiFi band is an example.

To troubleshoot you need to start from a clean slate.
Use your full board stack.

1. Start with a fresh moOde 8.3.8 image
2. Connect using Ethernet
3. Set "Output device" to "I2S audio device"
4. Set "Named I2S device" to "ProtoDAC TDA1387 X8"
5. Reboot
6. Verify that everything works

Troubleshoot WiFi

1. Leave Ethernet connected
2. Open Network Config and define your SSID and password (use SSID for 5GHz band first)
3. Reboot

Post the contents of the startup log and output from the commands below

1. Startup log
The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from the any of the Config screens. The startup log will be at the end of System info output.

2. WiFi info

Code:

ifconfig

iwconfig

Hi @Tim Curtis trying to understand your guidance here better. So you are asking me to recreate the 'failure' mode with ethernet cable connected, correct? In other words, do this test from the location (my office room) where Wifi is dying but with ethernet cable connected so that you can see what is happening in start up log for the Wifi config? I just need to find a 20 feet ethernet cable ? 

FWIW yesterday I tried to start from clean slate multiple times. I typically set the Wifi SSID and password while imaging the SD card using RPi imager tool. And yes I've been entering the 5GHz band info. I was able to see the 5GHz connection in the router when it connected successfully from my living room.

Finally, is the start up log stored in the SD card boot partition somewhere (hidden)? I can plug in the SD card and try to get the startup log if that is feasible.

Yes, try to recreate the failure with Ethernet plugged in so you can get log and command output that can be analyzed.

If it fails in a location closer to your Router then use that location. If it only fails in your office room then it would reinforce a wifi interference or some other external issue.

@Tim Curtis I think I figured out what is going on. It looks like the Wifi signal is getting increasingly weak as I move away from the wifi router room. And based on what I read in multiple forums RPi4's wifi implementation seems to be inherently weak. And the IanCanada stack is making the signal attenuation worse. I just chatted with Gabster and he confirmed the same experience and suggested I stick to ethernet. 

It appears that plugging in a USB wifi adapter with antenna could be an alternative. Should any Wifi adapter that works with RaspiOS/Debian work with the latest Moode build? I'm considering the following and it is based on the RT5370 which likely works out of the box.

https://www.amazon.com/Adapter-LOTEKOO-R...0BHW6T96R/

Here is a more advanced adapter but not sure if this will work out of the box plug n play. Might need driver installation. Is it relatively easy to install drivers for this if needed? Please advice. 

https://www.amazon.com/BrosTrend-600Mbps...01GC8XH0S/