• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 1032 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.

TAS2563: code example for MCU

Lenio Cacula
Genius 17010 points

Part Number: TAS2563

I have seen links to Android drivers and some github location for Linux drivers as well, but I am interested in code for a general purpose MCU, in either C or C++. Do we have such a thing?

Thank you!

  • 0
    TI__Guru** 114365 points

    Hi Lenio,

    There may be some reference code, let me check with our driver specialists.
    Will get back to you by early next week or earlier of possible,

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Lenio Cacula
    TI__Guru** 114365 points

    Hi Lenio,

    Some feedback is that functions from available driver are C code and headers, you may be able to call functions from a main code in MCU instead of device tree from Android/Linux.

    I'm checking if there are any guidelines on how to implement these but no feedback on that yet, I'll check back again.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • +1 in reply to Ivan Salazar
    TI__Guru** 114365 points

    Hi Lenio,

    Attached are the files provided from SW development team for no OS applications:

    tas2563_baremetal_driver-master@77ee72e0119.zip

    If you need further support in terms of system integration we can sync offline for more details.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    Prodigy 66 points

    Hi Ivan,

    I think "tas2563-baremetal.c" source file is missing.

    Do you have any MCU project example with these baremetal library?

    Kind regards,

    Burak Enez

  • 0 in reply to Burak Enez
    TI__Guru** 114365 points

    Hi Burak,

    Did you mean tas2563-baremetal.h ? Or can you point out where tas2563-baremetal.c is called for?
    I think our team can provide some guidelines for system integration if that's helpful. Let me check if this is something we can share publicly or need to reach out directly.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    Prodigy 66 points

    Hi Ivan,

    I mean the source file. Because there is no function definitions of the prototypes which are in the header file. If there is a "tas2563-baremetal.h" which has only the function prototypes, it means that there should be a "tas2563-baremetal.c" which shoud include the definition of these functions. But there is not such a source file in the attached zip file.

    Kind regards,

    Burak

  • 0 in reply to Burak Enez
    TI__Guru** 114365 points

    Hi Burak,

    I understand, let me double check with driver development team. I should get some feedback early next week.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    TI__Guru** 114365 points

    Burak,

    You may have already developed some additional code for this, however I'm following up on the original request:

    • TAS2563 is basically configured through register settings. Registers can be accessed either by I2C or SPI interface depending on hardware setup.
    • General purpose MCU should have own I2C or SPI command/lib
    • tas2563-i2c.c code is meant to be used for header format interpretation, as described in tas2563-regmap-bypass.h
      • This will write configuration sequence as described in tas2563_config_registers function
    • Custom I2C or SPI write code should be added to PltI2cTransfer function in tas2563-i2c.c
    • tas2563-regmap-bypass.h should be adjusted depending on device configuration, it follows the same format as header file obtained from End System Integration, it has default settings bypassing internal processing as is.

    Hopefully this helps for better understanding on how to use the provided codes.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    Prodigy 66 points

    Ivan,

    Thank you for the answer. I think this library that you provided is very lite if you compare it with TI's TAS2563 linux driver. I believe that there should be a bigger library provided by TI for ARM MCUs. There is not even a VolumeControl funtion in this one. Also, PPC3 generates config data with pages which not even explained in the datasheet. Is there any plan to develop a more through library in your side? If there is, when do you plan to release it?

    Kind regards,

    Burak

  • 0 in reply to Burak Enez
    TI__Guru** 114365 points

    Hi Burak,

    I don't know of any active development as of now. I'll communicate this request with the team but I couldn't comment if it can be addressed or a timeline for it.

    Best regards,
    -Ivan Salazar
    Applications Engineer