Hello,
I'm integrating CCP module to my project.
I find a problem that, one byte is 16 bit in F28335. But it seems that one byte is 8 bit in the ASAP2 definition.
------------------------------------------------------------------------------------------------------------------------------------
Take Command UPLOAD for example(from CAN Calibration Protocol Version 2.1)：
Position Type Description
0 byte Command Code = UPLOAD 0x04
1 byte Command Counter = CTR
2 byte Size of data block to be uploaded in bytes
3...7 bytes don't care
A data block of the specified length (size), starting at current Memory Transfer Address 0 (MTA0) , will be copied into the corresponding DTO data field. The MTA0 pointer will be post-incremented by the value of 'size'.
------------------------------------------------------------------------------------------------------------------------------------
I seems that almost all the CCP tools like Vector CANAPE, ETAS INCA define one byte 8 bit here
( byte Size of data block to be uploaded in bytes).
Then we have a problem.
Take UPLOAD 4*8 bit for example:
The MTA0 pointer in CCP tool will be post-incremented by 4
The MTA0 pointer in F28335 will be post-incremented by 2
The two MTA0 mismatch.
------------------------------------------------------------------------------------------------------------------------------------
Possible solution:
1 CCP can define one byte 16 bit. Just change the a2l file or CCP tool’s setting to support 16 bit byte. – But I don’t know whether CCP support 16 bit byte.
------------------------------------------------------------------------------------------------------------------------------------
Is there any other solution?
Thank you very much
