• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 215 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.

TDA4VM: Drives CAN to send out messages

Cherry Zhou
Mastermind 22235 points
Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

Using the ti-processor-SDK-RTOS-j721e-EVM-08_04_00_06 original code.

The customer wants to add a DIO driver to the code of MCU2-0 to drive the LED8 and LED9 user lights on the EVM board to drive the can to send messages out. But they don't know how to add these drivers to the project to build.

Is it required to copy the contents of MCUSW or just need to call MCAL directly?

Also, is it important that MCAL code be configured with the EB tool? Is there a drive for a non-EB tool available?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 32377 points

    Hello Cherry,

    Cherry Zhou said:
    The customer wants to add a DIO driver to the code of MCU2-0

    Yes, to be clear, in the SDK natively supports mcu1_0 and mcu2_1, so you want some guidance on adding a build option for mcu2_1, is this correct?

    Cherry Zhou said:
    Is it required to copy the contents of MCUSW or just need to call MCAL directly?

    I believe this depends on their application build structure. It can either call the MCUSW build structure independently, calling the make commands as needed.

    OR

    You can copy the contents of the MCUSW and incorporate it into your project.

    It depends on what you want to do with the MCAL.

    Cherry Zhou said:
    Also, is it important that MCAL code be configured with the EB tool? Is there a drive for a non-EB tool available?

    Yes, it is important that the MCAL code be configured with the EB tool. The reason is that the EB tool has "checks" or verification that the configuration you are modifying is valid, and it checks the ranges of the values you modify. There currently is not a non-EB tool available. If you do modify the generated configuration files manually, you need to make sure you are using valid values.

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    TI__Mastermind 22235 points

    Hello Erick,

    Thanks for your help.

    Erick Narvaez said:
    so you want some guidance on adding a build option for mcu2_1, is this correct?

    Yes. For example, the customer want to use LED8 LED9 two user lights, how to use them in the vision_app mcu2_1, mcu2_0? Also, they do not know if the MCAL in the default SDK has these two pins configured. 

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 32377 points

    Cherry,

    Cherry Zhou said:
    Also, they do not know if the MCAL in the default SDK has these two pins configured. 

    I do not think the MCAL in the default SDK has these pins configured. Can you point me to a reference of the vision_app that you mentioned? I don't see this in the MCUSW Documentation.

    Regards,

    Erick