• State TI Thinks Resolved
  • Locked Locked
  • Replies 25 replies
  • Answers 5 answers
  • Subscribers 98 subscribers
  • Views 747 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.

AM62A7: Sysconfig Usage

? ??
Prodigy 20 points
Part Number: AM62A7
Other Parts Discussed in Thread: SYSCONFIG

Hello teachers
When using the TI AM62Ax R5 SDK to debug routines, it was found that the same Sysconfig in the routine cannot meet the needs of debugging multiple drivers. As shown in the figure below, neither sysconfig can meet the needs of debugging MCAN and DMA simultaneously.
1. May I ask if it is possible to add TI drivers based on this sysconfig. (If possible, please provide a method)
If 1 is not feasible, can we provide a course of action for this issue.

  • 0
    TI__Guru 50378 points

    Hello,

    Thanks for reaching out to Texas Instruments E2E support forum. 

    Can you please tell us which version of MCU+SDK are you using?

    Please refer to the AM62A MCU+SDK version specific release note to see which features are supported and which are not supported.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    1. I am using mcu_plus_sdk-am62ax_09_1-00_19 and Sysconfig 1.18.1. My question is how to create a Sysconfig project that can simultaneously meet my debugging needs for UART, SPI, DMA, CAN, PWM, ECAP, and IIC.
    2.Does the AM62Ax R5 kernel support the watchdog driver.

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    1. I am using mcu_plus_sdk-am62ax_09_1-00_19 and Sysconfig 1.18.1. My question is how to create a Sysconfig project that can simultaneously meet my debugging needs for UART, SPI, DMA, CAN, PWM, ECAP, and IIC.

    Please open the Sysconfig tool with below parameters to see the above peripherals.

    Please refer below screenshots.

    ? ?? said:
    2.Does the AM62Ax R5 kernel support the watchdog driver.

    No, it is not supported for R5F as it is in MAIN domain. Only MCU domain peripherals are supported in MCU R5.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    Do you mean that I can use the A53 program to debug the R5F core and successfully access R5F resources?

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    Do you mean that I can use the A53 program to debug the R5F core and successfully access R5F resources?

    No it is not possible to use A53 program to debug R5F core.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    1.In the operation steps you demonstrated (as shown in the figure below), the context selected is a53ss0_1, not mcur5fss0_2
    2.Can Sysconfig with context a53ss0_0 be used in R5F programs.
    3. Let me reiterate my request. I would like a suitable Sysconfig project that can meet my needs for debugging UART, SPI, DMA, CAN, PWM, ECAP, and IIC for R5F cores

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    1.In the operation steps you demonstrated (as shown in the figure below), the context selected is a53ss0_1, not mcur5fss0_2

    Yes, the above configuration is suggested to answer the above asked query regarding Sysconfig Project where all UART,SPI,DMA,CAN,PWM,ECAP,I2c can be debugged simultaneously.

    ? ?? said:
    2.Can Sysconfig with context a53ss0_0 be used in R5F programs.

    No, this is not possible.

    ? ?? said:
    3. Let me reiterate my request. I would like a suitable Sysconfig project that can meet my needs for debugging UART, SPI, DMA, CAN, PWM, ECAP, and IIC for R5F cores

    Unfortunately, the above requirements can not be fulfilled.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    For example, this r5fss0:0 routine contains most of the drivers I want to debug, but there is no MCAN driver. Can I add an MCAN driver in some way?

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    Can I add an MCAN driver in some way?

    Currently, MCAN peripheral is only supported through MCU R5F and A53 core. Please refer MCAN_loopback_example.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    As shown in the figure below, is there a way to add MCAN to the TI Drivers list in the reserved driver list to meet my development needs.

    Regards,

    Tushar

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    As shown in the figure below, is there a way to add MCAN to the TI Drivers list in the reserved driver list to meet my development needs

    The Reserved Peripherals tab is used to reserve any particular hardware resource that your own custom code will handle, and it tells the sysconfig tool not to use that peripheral. This tab should not be used for any peripherals that you want to be configured by the tool.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    Let me summarize the above conversation. If Sysconfig is used to configure the driver, it cannot meet the requirements of R5F core debugging UART, SPI, DMA, CAN, PWM, ECAP driver.Can we understand it this way？

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for the above note.

    The Peripherals which are supported by particular core in SDK, can only be configured using Sysconfig tool.

    Peripherals which are not supported for a specific core can not be configured using Sysconfig tool.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    One thing I don't understand is why the driver content supported by the Sysconfig file for each routine in R5F is different. For example, the UART routine does not support MCAN drivers, but the MCAN routine supports MCAN, which is also a routine in R5F.

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    ? ?? said:
    One thing I don't understand is why the driver content supported by the Sysconfig file for each routine in R5F is different. For example, the UART routine does not support MCAN drivers, but the MCAN routine supports MCAN, which is also a routine in R5F.

    Sorry, I didn't understand the above comment fully. Can you please elaborate a little bit?

    Can you please clarify what routine means here?

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    1.What I mean is, why does each instance of an R5F program support different numbers of drivers.
    2.Why can't the Sysconfig tool create a Sysconfig project that includes all the drivers supported by R5F.
    3. Can upgrading SDK and Sysconfig solve the above issues.

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    What I mean is, why does each instance of an R5F program support different numbers of drivers.

    I didn't understand the above statement fully, but as per my understanding are you asking something like this.

    Why MCASP has 3 instance and UDMA has only 2 instances for DM-R5?

    To check the above details, please refer to section 1.2 Module Allocation and Instances within Device Domains of AM62A TRM. 

    ? ?? said:
    Why can't the Sysconfig tool create a Sysconfig project that includes all the drivers supported by R5F.

    Sysconfig tool gives you the flexibility to add or remove the peripheral instance according to the use case. It will include the drivers for peripherals which is configured by user to meet the application requirement instead of including all drivers.

    ? ?? said:
    Can upgrading SDK and Sysconfig solve the above issues.

    No, upgrading the SDK and Sysconfig tool will not allow you to add all the drivers in R5F core until it is supported by the SDK. Only those peripherals which are supported in SDK for specific core can be added to Sysconfig project.

    Please refer release notes for more details. 

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    1. Let me ask in a different way, what is the difference between mcu-r5fss0-0 and r5fss0-0?
    2.I found that only the TI drivers list of the mcu-r5fss0-0 example program has MCAN.

    Regards,

    Tushar

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    1. Let me ask in a different way, what is the difference between mcu-r5fss0-0 and r5fss0-0?

    DM R5 is in the wakeup domain which is used to run the Bootloader and the device manager responsible for the power and resource management. It is not recommended to run other driver along with device manager on DM R5F core.

    While MCU R5 is in the MCU domain which can be used for general purpose and for running safety applications. In the SDK v09.02 I can see except ECAP all other driver support is there. You can use the MCU R5 core to use the MCAN driver.

    ? ?? said:
    2.I found that only the TI drivers list of the mcu-r5fss0-0 example program has MCAN.

    It is supported from A53 core also. 

    Hope the above information helps.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your response.

    Which Sysconfig and CCS versions are recommended for SDK v09.02.

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your reply.

    ? ?? said:
    Which Sysconfig and CCS versions are recommended for SDK v09.02.

    To find all the required tools for SDK, please refer Setup SDK and tools. 

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your reply.

    I upgraded to SDK v09.02. But when entering assertions during DMA initialization, can you help guide me on whether there are any issues with the configuration of DMA and UART?

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your reply.

    We don't recommend to build the example.syscfg file from scratch. There are existing examples for UDMA which you can use as a reference.

    I can see that you have configured the UART to operate in DMA mode which is currently not supported.

    Please refer https://software-dl.ti.com/mcu-plus-sdk/esd/AM62AX/latest/exports/docs/api_guide_am62ax/DRIVERS_UART_PAGE.html 

    Please refer to the existing UART & UDMA examples provided in the SDK.

    If you have any query related to UART and UDMA, please feel free to open new threads. 

    It will help us assign the thread to right owner.

    Hope the above information helps.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 20 points

    Hello Tushar,

    Thanks for your reply.

    When debugging with mcu-r5fss0-0, can resources outside of MCU Domain be accessed without checking the Use MCU Domain Peripherals option.

    Regards,

    Ding

  • 0 in reply to ? ??
    TI__Guru 50378 points

    Hello Ding,

    Thanks for your response.

    ? ?? said:
    When debugging with mcu-r5fss0-0, can resources outside of MCU Domain be accessed without checking the Use MCU Domain Peripherals option.

    Yes, but you can only access peripherals outside of MCU domain which are supported/accessible by the MCU core by unchecking the use MCU domain peripheral option.

    To check the list of peripherals supported by each core please refer mcu-sdk-release-notes. 

    Regards,

    Tushar