Direct transmission of metadata from TXT Buffer
In the actual implementation, the TX Arbitrator loads the metadata during two clock cycles into internal registers and stores it to the output. At the start of Frame, CAN Core will lock the buffer, and tranBuffer will store metadata.
Since now, the whole TXT Buffer is implemented as single RAM memory. Data part of CAN Frame is already loaded from the TXT Buffer via pointer. Metadata + Identifier are still stored in the internal TX Arbitrator registers, on TX arbitrator outputs and also in tranBuffer.
The aim of this task is to:
- Implement storing of metadata during SOF by access to TXT Buffer via pointer, instead of taking data from tranBuffer.
- Implement loading of Identifier shift registers by access to TXT Buffer via pointer, instead of taking data from the registers.
- If 1 an 2 are implemented, tranBuffer will be obsolete as well as loading Frame format word and identifier word by TX Arbitrator (Timestamp still must be loaded though). This will simplify TX Arbitrator implementation and also save some amount of logic!