Other Parts Discussed in Thread: PCM1808, PCM5102A, CC-DEBUGGER,
Not sure why the original thread was locked so quickly...I just got back to this project in the last week. Here is the last response from TI:
Hi Andrew,
Have you programmed your board with a customized production test image?
For your project, go to "Flash Programming" . In the "Select Device Configuration" section change "Image Type" to "Production Test". This file must be programmed on your DUT.
You also need to make a custom ppwptc file, this is well documented in the Commander documentation.
Regards,
Fredrik
Originally I did not use the Production Test setting as this is completely unclear in the instructions for PPW Commander. However, loading the images as production test does not change anything in the original issues I was seeing. I have pretty much given up using this software for QC testing. I am sure that there are still some hidden configurations related to the DK that are preventing the supplied tests from working with customer hardware. One area that makes this clear is that the audio loop through tests mention a hex file that applies to the DK hardware only. But there are no instructions whatsoever on how to modify this file to work with different hardware. I know when trying to run the test that nothing appears on the I2S lines to my device, so it's obviously not working. Fredrik, you were going to ask your PPW software expert to get in touch with me but that has not happened. Is there any way you can try him/her again?
Thanks,
AW