• AVR Freaks

Hot!dsPIC33EV256GM106 CAN vs ECAN

Author
FalcioneE
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2019/10/28 06:42:05
  • Location: 0
  • Status: offline
2019/10/28 09:35:14 (permalink)
0

dsPIC33EV256GM106 CAN vs ECAN

Hi all,
 
I am using a dsPIC33EV256GM106 microcontroller, and I can't figure out the difference between CAN and ECAN.
 
Using MCC, I can see that I have a CAN peripheral, but not an ECAN peripheral. However, my MCC generates both ECAN and CAN files.
 
When I compile the code several warnings appear that claim the ECAN functions are deprecated. How can I eliminate those warnings? Should I use any of the ECAN functionality, or stick to the CAN functions/variables?
 
Thanks
#1

4 Replies Related Threads

    du00000001
    Just Some Member
    • Total Posts : 3956
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: dsPIC33EV256GM106 CAN vs ECAN 2019/10/29 15:19:39 (permalink)
    0
    "ECAN" is (was?) the denomination for a CAN controller with more than 16 message buffers.
    I think the "deprecated" warnings/infos are due to a decision not to differentiate between CAN controllers just based on the number of message buffers.

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #2
    FalcioneE
    New Member
    • Total Posts : 10
    • Reward points : 0
    • Joined: 2019/10/28 06:42:05
    • Location: 0
    • Status: offline
    Re: dsPIC33EV256GM106 CAN vs ECAN 2019/10/30 08:33:36 (permalink)
    0
    Thanks for your response!
     
    Like I said before, my MCC generates CAN.h, CAN.c, ECAN.h, and ECAN.c files. It looks like the ECAN files are just some abstraction that calls functions from the CAN files. Any suggestions as to whether it is better to use functions directly from CAN files or via the ECAN files?
    #3
    du00000001
    Just Some Member
    • Total Posts : 3956
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: dsPIC33EV256GM106 CAN vs ECAN 2019/10/30 09:01:35 (permalink)
    0
    I haven't worked with MCC generated code on the EVs yet, so I have to wager an educated guess:
    if feasible, stick to the CAN* files. "deprecated" might result in the ECAN* files no longer generated one day.

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #4
    FalcioneE
    New Member
    • Total Posts : 10
    • Reward points : 0
    • Joined: 2019/10/28 06:42:05
    • Location: 0
    • Status: offline
    Re: dsPIC33EV256GM106 CAN vs ECAN 2019/10/30 09:37:00 (permalink)
    0
    Seems reasonable, thanks!
    #5
    Jump to:
    © 2020 APG vNext Commercial Version 4.5