ProtoDAC TDA1387 X8 project

[varunach]

What do the status LEDs indicate on the Raspberry Pi? Is there normal power and SD card activity?

@hifinet yes there is. It is just unresponsive and I simply can't access 'moode.local' end point from the wifi network. If i unplug the 3.3V terminals from FifoPi Q7 and reboot it seems to work just fine. 

My full stack is as follows: PurePi >> RPi4 >> FifoPi Q7 gets its 3.3V from PurePi >> ProtoDac on top of Q7 with GPIO extender and pins 2/4 removed and gets its 5V from PurePi

For additional info, other than my previous message around troubleshooting, here are a few more things I tried.

1) I removed the Q7 altogether from this chain above and connected the ProtoDac to RPi4 (which sits on top of PurePi) directly with isolated GPIO extender, still maintaining 5V supply to ProtoDac from the PurePi. Everything works as expected and can get audio out. This tells me RPi4 and ProtoDAV is able to share the 5V PurePi supply without any issues. 
2) I also have a monitorPi which is helping a bit with troubleshooting. Connecting a MonitorPi to RPi4 GPIO (with nothing else connected) shows that it is getting audio signal via GPIO (see image with 48Khz playing). When I add the FifoPi Q7 to the GPIO stack with 3.3V still not connected, the MonitorPi doesn't show any clock or audio signal (see attached image that shows NOSIG and everything is 0). When I connect the 3.3V terminals to Q7 the clock seems to be initialized properly but still no signal via GPIO (see attached image where the 45 and 49 Khz clock signals are displayed with NOSIG). This is also when Moode becomes unresponsive and I lose access. 

Something tells me this might be related to a driver and/or clock signal related issue? Looks like @OnkelPH had the same issue so I'm curious how he got over this hurdle.

[varunach]

@hifinet FWIW i also tried to increase the 'delay' setting on FifoPi Q7 to 0.8 or 1 sec (from the default 0.2 sec), that didnt help either.

[hifinet]

If the ACT light is flashing after power on, then Moode is likely starting properly. When Moode is running, get the WiFi IP from m--->Network. Use this IP in the browser, because it won't change for that RPi (assigned by the router based on the MAC).

Moode needs to function and send I2S signal (play a file) in order for MonitorPi to show anything other than "nosig".

I think the delay setting uses more FIFO buffer memory in the Q7. I know very little to nothing about Q7.

[Ludomaniac]

@varunach Does the Empty LED on the Q7 light up?

I had a similiar issue, and in my case there was a fuse on the PuriPi's J2 3.3V connector that was blow. A small fuse located next to J2 connector. Are you able to measure if your 3.3V rail is okay with a voltage meter or so or do a check on that fuse that it isn't blown?

From the manual to the PuriPi:

"A fuse F2 is installed to this output to protect from over current or short circuit. The Littlefuse P/N of this fuse is 0451005.MRL"

[varunach]

@hifinet @Tim Curtis ok this is bizzare, but when I connected my entire stack via ethernet cable to RPi4, it works flawlessly. Looks like Moode's Wifi goes unresponsive for some reason when connected to Q7. @Tim Curtis let me know if you need any logs or anything.

[varunach]

@Tim Curtis I've done multiple tests and it seems to be a network related problem. For whatever reason, on Wifi, Moode is not able to acquire the IP both in DHCP and Static IP configuration. I'm guessing thats what is happening. The moment i connect to Ethernet it works great. I'm really perplexed tbh. Any suggestions? I never had this problem until I connected the FifoPi Q7. Originally I had a simple RPi4 with just the ProtoDac connected and it was working great. Could this be power related where RPi4 getting power from PurePi ultra capacitors is somehow causing Wifi issues?

So close to getting this to work ?

[hifinet]

What happens when you let the browser with the wifi IP address open on the page for a while = Few minutes? Does it eventually connect?

What is the state of the red power LED on the RPi?

[varunach]

What happens when you let the browser with the wifi IP address open on the page for a while = Few minutes?

Times out with 'Site can't be reached' message. I tried on both mobile and PC browser, letting the browser run for a while.

[hifinet]

What happens when you let the browser with the wifi IP address open on the page for a while = Few minutes?

Times out with 'Site can't be reached' message. I tried on both mobile and PC browser, letting the browser run for a while.

Refresh a few times. My Zero W can need a few refreshes, or if you let it sit there, it should connect.

[varunach]

What happens when you let the browser with the wifi IP address open on the page for a while = Few minutes?

Times out with 'Site can't be reached' message. I tried on both mobile and PC browser, letting the browser run for a while.

Refresh a few times. My Zero W can need a few refreshes, or if you let it sit there, it should connect.

I've let is be for more than 30 mins ? no luck. i personally think there is some sort of network configuration that is getting wonky. Perhaps @Tim Curtis can chime in on where to look for the root cause.