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

LAUNCHXL-F28P65X: MCAN implementation on Launchxl F28P65x CPU1_FLASH and CPU1_LAUNCHXL_FLASH

Yash Bhati
Prodigy 110 points
Part Number: LAUNCHXL-F28P65X
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hello TI Team,

There is an issue while implementing MCAN(CAN-FD) transmit functionality on launchxl p65x that while building my code with 'CPU1_FLASH' I'm not able to transmit the data. Even though the data is being updated on the Message RAM.

But when building the same code with 'CPU1_LAUNCHXL_FLASH' transmit functionality works fine. 

Want some clarity here that how changing this will effect the transmit functionality.

And what are the significance of other build configurations like- CPU1_LAUNCHXL_RAM and CPU1_RAM?

Regards

Yash

  • 0
    TI__Mastermind 34785 points

    Hi Yash,

    Is this on an existing C2000Ware example code?  If so, can you tell me which one it is?

    Regards,,

    Joseph

  • 0 in reply to Joseph Casuga
    Prodigy 10 points

    Hi Joseph, I work alongside Yash.

    Yes, All the existing C2000Ware example codes show the same behavior. We explicitly tried our initial testing with "mcan_ex9_transmit" example code; built with 'CPU1_FLASH' and with this, we couldn't see any data on the CAN-FD Bus. It's only when we build with 'CPU1_LAUNCHXL_FLASH' we see the data loaded onto the bus. I could see some Conditional Compilation happing between LAUNCHXL_F28P65X and ControlCARD in the device.h library.
    I guess, it has to do something with the allocation of correct GPIOs. Please shed some light on this.

    I would like to know, what exactly is different in the build process when we change from 'CPU1_LAUNCHXL_FLASH' to 'CPU1_FLASH'?
    And I don't understand the terminology being used here "CPU1_LAUNCHXL_FLASH". What does LaunchXL-Flash mean here? How is it different than a CPU-Flash?

    Waiting for your response! Thanks, and regards!
    Kapil

  • 0 in reply to Kapil Lanjewar
    TI__Mastermind 34785 points

    Hi Ysa,

    CPU1_FLASH and CPU1)LAUNCHXL_FLASH have different GPIO assignments.  If you are using the launchpad, make sure to use target CPU1_LAUNCHXL_FLASH to ensure the correct GPIO assignments are used for MCAN and other peripherals.

    Regards,

    Joseph