• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 644 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.

AM2634: MCAL MCAN test example demo CanApp.c failed to send data properly

Cherry Zhou
Mastermind 22235 points
Part Number: AM2634

Hi team,

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

MCAL version: MCAL_AM263x_00.09.00_03

CCS version: 12.0.0.00009 

H/W: AM263x control card evaluation module (EVM)

1) Import MCAL source code, compile passed. Debugging CanApp.c sending data failed using MCAN1. EB reconfiguration of the port module generates code, and it was found that can_mcanStart needs to be modified to add the following statement to send data properly:

MCAN_lpbkModeEnable(baseAddr, (UINT32_t)MCAN_LPBK_mode_external, (UINT32_t)true);

Because this code is the MCAL low level code, modifications are not required.

Is there any other possible reason for this? OR is there a bug in the MCAL example initialization function?

2) Could you help provide MCAL CCS based test projects?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Genius 15435 points

    Hi

    I am looking into this query, will get back to you by Tuesday EOD.

    Thanks

  • 0 in reply to Kowshik Gudimetla
    TI__Genius 15435 points

    Hi Cherry,

    Can you please confirm if customer was trying to get the "CAN Loopback mode" to work?? if yes, there's a macro in the CanApp.c file named "APP_LOOPBACK_MODE", make it to STD_ON and the CanApp.c works as expected in the loopback mode (User doesn't need to add or modify the existing example or source code to get this working)

    Hope this helps.

  • 0 in reply to Kowshik Gudimetla
    TI__Mastermind 22235 points

    Hi Kowshik,

    Thanks for your support.

    Kowshik Gudimetla said:
    Can you please confirm if customer was trying to get the "CAN Loopback mode" to work??

    No, please let me clarify:

    1) Using the CanApp.c example code, the customer wants to send out CAN data on the AM263x controlCARD test.

    2) In non-loopback mode, the oscilloscope seems to have just grabbed a segment of the waveform and stopped.

    3) And they attempts to modify MCAL code (non-normal operation) Add Mcan_lpbkModeEnable(baseAddr, (UINT32_t)Mcan_LPBK_mode_external,(UINT32_t)true; compile and download to control card, CAN continuously sends out data.

    Q1: Why is the CanApp.c example code not sending out can data continuously without any modification in the non-loopback mode?

    Q2: Could you help provide a complete CCS project for this MCAL example code for AM263? 

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Genius 15435 points

    Hi Cherry Zhou,

    I'm checking internally on why the source code modification is needed. Ideally it is not required and we have see the messages during the testing phase too. 

    My understanding here is, by default the CAN transceiver on our AM263x-CC EVM are activated and the example's port configuration is done in such a way that it uses this transceiver CAN instance to perform loopback kind of operations. However, customer can disable the loopback in the example and must change the PORT configuration to choose a MCAN instance that is connected to some jumper pins to get the CAN working in external mode. (I'll be updating more on which instance is this and what header pins are these after internal discussion)

    Allow me some time to check internally and come back with confirmation. I should have some info by Friday EOD.

    Thanks

  • 0 in reply to Kowshik Gudimetla
    TI__Genius 15435 points

    Hi

    Apologies for delay in my reply, we had many holidays and vacation going on lately. I was able to properly test the CAN App in external transmission mode and able to verify the transmission on a PCAN module without making any changes to the source code. Please find the steps below to get it working

    1. You need to add the port configurations to the Port_PBcfg.c file as the MCAN related pinmux configurations are by default not done. Please add the below changes to the Port_PBCfg.c file under the path mcal/examples/Config (These are for configuring MCAN Tx and Rx lines)

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    {
    .Port_PinId = 99,
    .Port_PullInhibitEnable = PORT_PIN_PULL_INHIBIT_DEFAULT,
    .Port_OutputOverride_Ctrl = 2,
    .Port_InputOverride_Ctrl = 2,
    .Port_DirectionChangeable = FALSE,
    .Port_PinModeChangeable = FALSE,
    .Port_PinLevelValue = PORT_PIN_LEVEL_HIGH,
    .Port_PinDirection = PORT_PIN_DEFAULT,
    .Port_PinInitialMode = PORT_PIN_MODE_MCAN1,
    .Port_PullTypeSelect = PORT_PIN_PULLTYPE_DEFAULT,
    .Port_SlewControl = PORT_PIN_SLEWCONTROL_DEFAULT,
    .Port_NumPortModes = 1,
    .Port_PinMode =
    { [0] =
    {
    .mode = PORT_PIN_MODE_MCAN1,
    .muxmode = 0,
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
     

    2. Change the following macros in the Can_Cfg.h file and Can_app.c files

    3. Comment the following lines in the Can_app.c file (Line 601) (This is the actual bug that was causing you not to transmit and we are considering it into fixing in the next release, here's the JIRA ID for refernce [SITARA_MCU_MCAL-3612] Compilation error for CAN module when Loopback is disabled - Texas Instruments JIRA)

    4. After this, do a clean build and run the Can_app.c binary to see the data, I have tested it with PCAN module and I was able to see the transmitted data as shown below

    Hope this helps and solves the issue.

    Thanks,
    G Kowshik