Thanks for the reply
The issue is that I only have one TMS570.
Yes. Tivaware only provides methods to read/write to registers, send messages, init the controller, etc. No buffering or any of the features of RTEMS CAN API. By “correct” I meant tivaware knows the register-map/datasheet of the tm4c123, and it can be used to write simple (single-process) CAN applications.
- If I understand correctly, you’re saying even with tivaware as a reference, writing an rtems DCAN driver for the TM4C123 will require as much work as writing one for the TMS570?
Not sure, but it looks like its BSD. The source is freely available on the tivaware website.
Both hardware: TM4C+TMS570? or BBB+TMS570? I was planning to have tm4c and tms570 CAN transceivers connect via jumper wire, and have both MCUs individually connect to my laptop via uart-to-usb for debugging.
Need to confirm. I have the evaluation board with header pins: LAUNCHXL2-570LC43 Development kit | TI.com. Maybe breadboard+jumper wires are enough?
Is there a preference for BBB D-CAN driver for this gsoc project? I picked the TMS570 after going reading @ppisa message in the BBB thread
Will check, thanks.