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

AM6442: Processors forum

?? ?
Prodigy 120 points

Part Number: AM6442
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hello,

  • environment:CCS Version: 12.7.1.00001 

            SDK Version: mcu_plus_sdk_am64x_10_00_00_20

            compiler Version: TI Clang v3.2.2.LTS

  • experimental condition：

            1. Add an UART instance with LLD shown as follows:

           2. there are errors in ti_drivers_config.c which is derived from system configuration shown as follows:

so could you help me find the reason?

thank you!

  • 0
    TI__Guru 54443 points

    Hi,

    I have done some experiments on my setup with different combinations.

    I see that this is a potential bug for UART. Not exactly for UARTR but the way code is generated from SysConfig for UART LLD + User Managed Interrupt combination.

    Please allow me sometime to file this bug for the next release.

    What I have seen is the following:

    When using LLD:

    When in Interrupt mode:

    It asks for setting of callback mode and then asks for the name of read and write callback functions.

    Which would be by default provided as NULL.

    Now when you set back to user managed interrupt, it is taking the read and write callback function names(which would be generated if the Interrupt mode was selected)

    A way to go around this would be to simply:

    1. Select LLD and Interrupt mode in SysConfig under UART.
    2. Give Callback mode and write the function name for read and write callback as lets say: dummy_read and dummy_write
    3. Choose the User Managed Interrupt from dropdown option now instead of the Interrupt option.
    4. Once done, in your main.c code, write 
      void dummy_read(){} and void dummy_write()

    Once, these steps are followed you should be able to proceed for now and build your application successfully.

    Let me check this internally if this was expected or not. If not then I will raise a bug for this to be fixed in the subsequent SDK releases.

    Thanks you.

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    Prodigy 120 points

    Hello Vaibhav,

    the method you provided solve my issue, thank you again. 

    However, I have another question. If I want to update the new version SDK in future after you fix this bug, shoud I also update the version of compiler and CCS at the same time? Does this will influence my current code function?

    thank you!

  • +1 in reply to ?? ?
    TI__Guru 54443 points
    ?? ? said:
    shoud I also update the version of compiler and CCS at the same time?

    No need to update the compiler version or the CCS version, but it is a good practise to update the compiler if the new release of the SDK says so.

    Additionally, can you please click on the "This resolve my issue" button if the above answer was helpful.

    Glad my explanation was helpful.

    Regards,

    Vaibhav