• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 227 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.

TMDSCNCD263P: IO MUX handling in MCAN4 for AM263PX-CC Board

Pradeep R
Expert 1100 points
Part Number: TMDSCNCD263P
Other Parts Discussed in Thread: TCA6424

Tool/software:

Hello Team,

we are working on MCAL version MCAL_AM263Px_09.02.00 for AM263Px

we are facing difficulty in establishing communication over MCAN4 on the EVB board

we referred the example provided as part of SDK mcu_plus_sdk_am263px_09_02_00_56 

Eg : :mcu_plus_sdk_am263px_09_02_00_56\examples\drivers\mcan\mcan_external_read_write

Here the IO MUX handler is handled separately and this is not part of MCAL and also when we try to refer the IO MUX handling files, there is dependency on Semaphores and other TI environment.

As we already have OS integrated and we do not need semaphore and other dependencies, Can you please provide us the IO MUX handling for MCAN4 without any additional dependency

The mcan_external_read_write example is working on CCS and communication is Up in CCS, but our application will be executed on lauterbach trace32, so we need exact  IO MUX handling for MCAN4 so that we can integrate in our application.

Thanking You,

Regards,

Pradeep R

  • 0
    TI__Guru*** 135355 points

    Hello Pradeep,

    So I make sure I get the right expert involved here, the issue you are facing is specifically concerning how to handle IO MUX with MCAL?

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Ralph Jacobi
    Expert 1100 points

    Hello Ralph Jcobi,

    Thankyou for the feedback.

    Yes we are integrating MCAL, so we need to use MCAL modules

    As part of MCAL, Cdd_I2c is present but for IO MUX as per example they use additional I2c driver which is part of SDK but not MCAL.

    So , can you please support us here.

    Regards,

    Pradeep R

  • 0 in reply to Pradeep R
    TI__Intellectual 870 points

    Hello Pradeep,

    IO MUX or PINMUX in MCAL is handled by port module.
    So in order to use MCAN4, PINMUX for the same need to be done as part of port module configuration.

    Refer mcal/examples_config/Port_Demo_Cfg , present as part of our recommended config for our example.

    Thanks,

    Mudit Bhansali

  • 0 in reply to Mudit Bhansali
    Expert 1100 points

    Hello Mudit Bhansali,

    Our Port Configuration is same as per demo shared "MCAL_AM263Px_09.02.00\mcal\examples_config\Port_Demo_Cfg\soc\am263px\r5f0_0\src\Port_PBcfg_CAN.c"

    But we need to know the how to handle FSI_MUX_SEL GPIO to pull it down using MCAL modules

    as per SDK mcu_plus_sdk_am263px_09_02_00_56\examples\drivers\mcan, there is an ioexp_tca6424 file being added which pull down the FSI mux to low, but this ioexp_tca6424 file includes I2C functions which are not part of MCAL

    Can You please explain us how to handle this scenario.

    Regards,

    Pradeep R

  • 0 in reply to Pradeep R
    TI__Intellectual 870 points

    Hi Pradeep,

    In case of E1 boards -> mux is pull down and which means MCAN is the default select.
    In case of E2 boards -> FSI is the default select.

    In MCAL, right now we don't have functionality for controlling the IO MUX.
    But now keeping in mind the need we will analyze and add this in future release.

    Thanks,

    Mudit Bhansali

  • 0 in reply to Mudit Bhansali
    Expert 1100 points

    Hello Mudit Bhansali,

    Yes, we are using E2 board, so FSI is default

    Thank you for the feedback.

    we will try with integrating the additional software's for IO mux handling as part of SDK.

    Regards,

    Pradeep R