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.

TMDSCNCD280049C: CAN peripheral issue between F280049M vs. F280049C controlcard.

Part Number: TMDSCNCD280049C
Other Parts Discussed in Thread: TMDSADAP180TO100, C2000WARE

I've had working code (done with mathworks 2020b embedded coder) for the F280049M which spewed out CAN messages at 500kbaud.  When i move this code over to the 280049C (with selecting 280049C under device in embedded coder), my CAN bus gets a form error then CAN messages go out on the CAN Bus.  I have few CAN messages (40-100 messages) at the start of power up then the continuous CAN messages go out and nothing is seen on the bus after on the 280049C.  

I have verified the GPIO connection as i am using TMDSADAP180to100 with the TMDSCNCD280049C connected going onto a USB-EMU R3 docking station with a CAN transceiver. I was using the same 180to100 and UBS-EMU docking station with the 280049M and that was working fine for CAN traffic.

so far, i have verified the GPIO for CANTx/Rx, ensured i am using CAN A, and ensured the correct linker file.  Is there anything different about the 280049C board that is different from the 280049M that would affect CAN output?  

I could not find any schematics for the F280049M as since that was experimental it doesnt seem like that is available anymore.

Appreciate any leads anyone can provide.

Thanks,

Abe