PCM5242: PPCM5242EVM - Unknown Device

Hi Jay,

Thank you for your query. My colleague Paul will take this up during US timezone.

Regards,
Uttam Sahu
Applications Engineer, Precision DACs

Hello Uttam, 

Thanks for the heads up. Paul, you are the man! I look forward to your response. 

If someone can send me the "Register Dump" from the purepath console of a basic working flow that would get me by. I'm generally past the need for the purepath console... I now need to initiaialize it with my MCU, and that's why I was going back in. I want a Register Dump of a working configuration so I can start programming it. Even if this is bricked, with that dump I could probably get by without buying another EVM. 

Or... Maybe it's not bricked? I look forward to hearing from you. 

Thanks!

Jay

Hi Jay,

What are the steps you need in your configuration? Are you configuring the PLL or switching to hybrid flow or something?

As far a reviving the EVM is concerned, I would first ensure the jumper configuration is good. It may be possible to re-flash the MCU, but I need to check on this device.

Thanks!
Paul

Hi Paul,

The jumper configuration is right. It's the same it was when it was working great for 3 days. It sounded great by the way.

Then I started messing around with the drivers and now I can't get it configured other than Unknown Device.

For the flow, honestly the out of box configurations seemed to work fine. I don't know for sure that I changed much if anything. I'm pretty sure it has to be set to 32 bits, and then just simply turned on (volumes up i guess?). Then I would send some I2S and it would work fine.

If you have a way to flash this device here I would love to try it. I could be wrong, maybe it's not bricked but I can't get it to recognaize anything anymore.

I can connect my own controller to it and read all the I2C default configurations. But it won't accept my I2S signal flow. So I was going back to see what I need to change off the default config so I can try that. But that's when I noticed I couldn't connect via I2C anymore via the purepath console.

The jumpers are the same as are listed in the GUI of the Purpath Console. I tried everything to get past the Unknown Device issue but windows wont recognize it for anything. That's why I started assuming I blew up the USB controller somehow. But of course there could be something I'm missing. It's just strange because it's 2 jumpers we are talking about. the SDA and SCL jumpters. Those are the only ones I had removed.

Maybe is there a way to more forceably install the driver? Right click in the device manager and "update driver" to a specific driver? Do you know where the driver is stored? Or is it a plug and play device. If so, then it's unknown and I don't know...

Thanks again for the help!