I have a TI RM46x HDK and have it setup to communicate successfully on CAN1 using the TI Demo tool.

I also have the FreeRTOS 9.0 demo built and running under CCS 5.4 on the RM46x HDK. We are using the Simma SDK for CAN and J1939. I do not think I have correctly setup the CAN rx/tx ISR.

So, for the 9.0 demo for CCS RM48, what should I do to assign the can[r/t]xisr functions?

If I understand your question, you seem to be asking about how to assign and name ISRs using Code Composer, which doesn't appear to be a FreeRTOS related question. Let me know if my understanding is wrong and your question is about FreeRTOS.

It is a question on how to assign an ISR to a specific CAN function (one for rx and one for tx). It is not specifically a FreeRTOS question, but is a question where I hope to use the version 9.0 demo for RM48 as a starting point.

I already have changes that allow a J1939 message (Address Claim) to be transmitted, but I am not seeing any reply or CAN/J1939 frames. I suspect my ISR setup, since those appear to not be assigned.

I am confident in my communication wiring and resistor setup, since intended traffic is visible on USB CAN tools and those tools capture the 1939 Address Claim message from the RM46x HDK board.

Any advice would be appreciated. Any guidance on whether I should be looking at specific interrupts or specific channels might also be helpful.

It might be a FreeRTOS question if considered along these lines: For any FreeRTOS demo created for the TI Hercules RM4 series, has anyone added CANBUS support? If so, how did you do it?

To answer this question I would have to first get out the hardware manual to remind myself how interrupts work on that part. Then have a look at some projects for that part that use the same compiler as you to see how they name interrupts, define the vector table, and any library functions that are used to install/enable/configure interrupts. I'm afraid non of that is related to FreeRTOS or uses the FreeRTOS documentation.

Here is an update to the question I asked. I was successful in using HalCoGen to create buildable code to support CAN/DCAN. I was expecting to hear about code snippets, but HalCoGen appears to have replaced the "code snippet" approach.