allways, auto increment CAN MSGBUFFER

Go To Last Post
2 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

when is the auto increment of the FIFO CAN data buffer executed, if it is activated?

I have seen several code examples where each of the 6 CANPAGE is called in a loop and each of the 8 MSGBUFFER is deleted in a inner second loop, but here the pointer of the MSGBuffer is increased by inc command. If auto increment is activated you should be able to do without inc, and possibly even simply execute the delete command 8 times in a row. Is this pointer for the message buffer increased with every access from my program or is this only the case with incoming CAN messages.

 

So would this also be possible?

clr temp
"select CANPAGE0"
sts CANMSG, temp
sts CANMSG, temp
sts CANMSG, temp
sts CANMSG, temp
sts CANMSG, temp
sts CANMSG, temp
sts CANMSG, temp
sts CANMSG, temp
"select CANPAGE1"
sts CANMSG, temp
....

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is there perhaps a possibility to access the memory areas of the CANMSG directly, which are definitely mapped somewhere? There is nothing about it in the data sheet. Probably because you want the way to turn off the MOBs and select the code page.

 

SRAM ATMega16M1/32M1/64M1