Content originally posted in LPCWare by DaveNadler on Wed May 18 08:28:22 MST 2011
[FONT=Arial]Sorry if I've somehow missed this in the documentation, but...
The CAN API functions do not specify the required scope of
arguments (ie, must these objects be static, or can they be
ephemeral stack variables). To minimize RAM use, I'd like
to avoid unnecessary static objects. And I think/hope
that mostly the data is just copied to the CAN controller...
For example:
init_can: is the configuration just copied, or is the address
saved and the data might be used later ?
config_rxmsgobj: can the structure pointed at by the parameter
be destroyed after the call ?
config_txmsgobj: [/FONT][FONT=Arial] can the structure pointed at by the parameter
be destroyed after the call ?
Similarly, the CANopen API implies the RAM CAN_CANOPEN_CFG
table must persist, but does not say so. Also it does not clearly
explain when/how this structure may be updated during operation.
Thanks in advance for your help,
Best Regards, Dave
[/FONT]
