• State TI Thinks Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 1111 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TLV320DAC3101: TLV320DAC3101 Beap generator

Ryuuichi machida
Guru 12085 points
Part Number: TLV320DAC3101

Hello,

I would like you to confirm whether following description is correct or not.

* 1: Beep generator is enabled (self-clearing based on beep duration).

According to confirmation w/ CodecControl and DAC3101 EVM, when I write "1" to Add 0x47[7], I confirmed beep sound by using HP but this bitfield is NOT cleared.

So, I would like you to confirm how user can observe self-clearing in this bitfield.

Could you please confirm ?

Best regards,

  • 0
    TI__Guru** 104455 points
    Hi Machida-san,

    The bit will remain '1' during the beep sound. Did you read this bit after the beep sound ended?
    I can confirm that the statement is correct.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • 0 in reply to Ivan Salazar
    Guru 12085 points

    Hello Ivan-san,

    Thank you for your reply.

    >Did you read this bit after the beep sound ended?

    Yes, I performed "Refresh" from "Register Inspector" on CodecControl.

    Could you please confirm whether statement is correct or not ?

    I only set following registers after power on by using CodecControl.

    1. Set 0x19 to Add 0x3C

    2. Set 0x80 to Add 0x47

    I confirmed beep sound from HP out.

    Best regards, 

  • 0 in reply to Ryuuichi machida
    TI__Guru** 104455 points
    Machida-san,

    I've been testing this specific case. I'm seeing a weird behavior of the control software described as follows: When I send the command "w 30 47 80" it seems that somehow this command is stuck and when I hit "Refresh" button it sends once again the previous command and there is a beep at the output, thus the bit is still '1'.
    I've found two ways that this does not happen:
    - Use the Beep control from the GUI (the small square with this name in the main panel).
    - Read back register 0x47 after the beep sound stops, by the command line "r 30 47 01"

    However the device operation seems to be OK, it seems this is more related to the control software.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • 0 in reply to Ivan Salazar
    Guru 12085 points
    Hello Ivan-san,

    I also confirmed when I try to perform following two ways, 0x47[7] is self-cleared.

    - Use the Beep control from the GUI (the small square with this name in the main panel).
    - Read back register 0x47 after the beep sound stops, by the command line "r 30 47 01"

    >it seems this is more related to the control software.
    Is it possible to request to investigate above ?
    My customer observe similar issue on customer's software condition, so if you locate root cause, it will become help.

    BR,
  • 0 in reply to Ryuuichi machida
    Guru 12085 points
    Hello Ivan-san,

    Is there any update for below ?

    >it seems this is more related to the control software.
    Is it possible to request to investigate above ?
    My customer observe similar issue on customer's software condition, so if you locate root cause, it will become help.

    Best Regards,
  • 0 in reply to Ryuuichi machida
    TI__Guru** 104455 points
    Hi Machida-san,

    I can look into this; it might take some time to get to the root cause, though.
    I'll reserve some time to debug this and update at the end of the week (hopefully earlier if possible).

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • 0 in reply to Ivan Salazar
    Guru 12085 points

    Hello Ivan-san,

    Thank you for your confirmation.

    If you have any update, could you please let me know ?

    Best Regards,

  • 0 in reply to Ryuuichi machida
    Guru 12085 points

    Hello Ivan-san,

    Could you please tell me your status ?

    Because, I need to inform current status to customer tomorrow.

    BR,

  • 0 in reply to Ryuuichi machida
    TI__Guru** 104455 points
    Hi Machida-san,

    Unfortunately I have not been able to identify the root cause so far. I'm still testing on this.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • 0 in reply to Ivan Salazar
    TI__Guru** 104455 points
    After some tests, I have identified that the writings to the beep registers are only happening on a specific GUI. If using a different control interface this is not happening, so there is no issue with the device itself.
    This is most likely a bug in the GUI code.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • 0 in reply to Ivan Salazar
    Guru 12085 points

    Hello Ivan-san,

    Thank you for your confirmation.

    I understood that there is no issue w/ the device itself.

    >My customer observe similar issue on customer's software condition, so if you locate root cause, it will become help.
    However, as I described above, customer have similar issue on their system.
    They are referring to following driver information.
    www.ti.com/.../tlv320aic31xxsw-linux
    e2e.ti.com/.../601636

    It seems that you said that this issue is NOT related to device driver, related to Application layer.
    Is my understanding correct ?

    If no, and this is related to device driver, could you please point out source code which have problem ?

    Best Regards,

  • 0 in reply to Ryuuichi machida
    TI__Guru** 104455 points
    Machida-san,

    Yes, the issue might be related to the application as using different GUI gives different results.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • 0 in reply to Ivan Salazar
    Guru 12085 points

    Hello Ivan-san,

    Thank you for your reply.

    I informed that this issue is related to code of App layer not device driver to customer.

    If they have additional question, I will post it to this thread.

    Please keep open to confirm their feedback.

    Best Regards,