• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 33 subscribers
  • Views 599 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PCM9211_EVM-U AUTO source selector

KANJI SHIBATANI
Mastermind 6205 points

Other Parts Discussed in Thread: PCM9211, PCM9211EVM-U

Hello,

I hope  this e-mail  finds you well.

My client  intends to use PCM9211  using auto source selector for their audio product

-  PLL srource/  RXIN2  SPDIF( Optical)  48KHz 256fs

-  ADC       fs= 96KHz 128fs slave mode                      

This operation looks fine in the PCM9211 EVM-U ( also their product),   however, .. when  client  plugged in/out the  Optical source (cable) 

so frequently  ( 1 times/sec  x 100~200 times),  output from Main Output Port  was losed ( stuck to GND)...

And also,  PCM9211EVM-U  Lock LED does NOT  distinguish ( i.e. indicates Locked ).

Problem is there are no way to detect the error from PCM9211 to  MCU.

This situation can be solved by

* Hardware reset ( 0x40h; system reset can't solve)

Or

* 0x26h changed  from  41h to  01h ( AERROR Not slected ),,  and

* 0x25h  changed from 23h ( EFSCHG,=1  EPARITY=1) to 01h

Would you please let me know the cause, and  register setting for AUTO_detection?

Clients are in hurry ( Before Mass Production )  and hope to your reply within 3 days

Best Regards

PS

Client's setting is below in the PCM9211EVM-U


w 80 23 05
# 05h

w 80 24 10
w 80 25 23
w 80 26 41
w 80 28 05
w 80 2A 1F
w 80 30 02
w 80 31 15
w 80 32 22
w 80 33 11
w 80 34 02
w 80 35 02
w 80 6D F0
w 80 6E 00
w 80 6F 80
w 80 78 3E
w 80 6B 00

If you had any queston, please let me know.

Sorry to bother you, but with my best regards

 

 

 

 

  

 

  • 0
    TI__Guru**** 189401 points

    Hi, Shibatani-san,

    Sorry for the delay in getting back to you. I have asked my colleague to look into this for you.

    -d2

  • 0 in reply to Don Dapkus
    Mastermind 6205 points

    Hello Don-san,

    Thank you for your reply.

    Client  hope your answer soon, because they are  just before MP stage .

    Would you please let us know your adivse?

    Thank you and with my best regards

     

  • 0 in reply to Don Dapkus
    Prodigy 40 points

    Dear Don-san

    I'm Hidemi Niimura (the said person) work for D&M Holdings Inc.

    I haven't received any information from you as of today.
    Shibatani-san already said last time, I needs to have it promptly.
    It's pretty urgent. Could you tell me when I can get it?
    Your urgent attention would be appreciated.

    H.Niimura
    Engineer
    Fukushima, Japan

  • 0 in reply to NIIMURA HIDEMI
    TI__Genius 16270 points

    Nimura-san, Shibatani-san,

    Regarding AUTO detection, it seems it is already enabled in this script and by default. 

    I am unable to re-create this issue with the PCM9211 EVM in my lab.  However I looked through the i2c settings, and it seems a parity error or Fs_change error is what is being detected permanently during this lock issue?  When Register 25/26 are being changed, they both still detect for PLL_LOCK, they just no longer look for the parity / Fs error and it solves the problem. 

    One way to verify this is the case, is to see if the MPO can be used as an interrupt for this condition.  We could do this by setting Register 0x78 = 6x to detect for parity errors?  If this serves a more accurate interrupt it could be used to alert the MCU, otherwise we may need to focus on Fs_change errors.

  • 0 in reply to Patrick Galvin
    Prodigy 40 points

    Dear Patrick

    Thank you for your reply.

    First of all, I would like to show you the video recorded when the issue verified.
    However, the file size is more than 60MB; too big, so I cannot attach it in this forum.
    Do you have any good idea to show it to you?

    In addition, i2c setting always detects parity / Fs_change error in this product. Do you think it is an irregular usage?
    Should we change the i2c setting which stop alerting parity/Fs_change error when PLL Lock error detected?

    Shibatani-san didn't write about other Fs_change though, there were no problems when 0x25h changed from 23h to 21h or 20h.
    We consider Fs_change is not related to this issue.

    We are really looking forward to your reply of your recommendation value for 0x25h and 0x26h when only Auto Source Selector executes path switch function.

    H.Niimura

  • 0 in reply to NIIMURA HIDEMI
    Prodigy 40 points

    Dear

    I’m sorry to be pressing, but … Any update on this?

    It’s been more than a week since I requested it.

    Your immediate response is urgently needed.

    H.Niimura

  • 0 in reply to NIIMURA HIDEMI
    TI__Genius 16270 points

    Nimura-san,

    In some applications using INT0/1, the other error sources are indeed masked.  If doing this does not cause a performance issue, it could be analyzed further.  However if you can send me the video at p.galvin@ti.com, along with a schematic, this may help further as well.