Part Number: TMS320F28335
Please tell me.
Does this errata also occur in SCC mode?
The measures described in Workaround cannot be used in SCC mode.
Do I have to change to eCAN mode?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: TMS320F28335
Please tell me.
Does this errata also occur in SCC mode?
The measures described in Workaround cannot be used in SCC mode.
Do I have to change to eCAN mode?
Hi Haraeesh, Thank you for your reply.
Is there a workaround that can be done in SCC mode?
For example, is it not possible to operate the CCR bit by detecting the incomplete transmission with another timer or cycle processing?
Yes, what you suggest is indeed possible. However, that involves software overhead and also tying up a timer. Using the built-in Timestamp counter is a lot easier. Is there a reason why you want to use SCC mode and not the eCAN mode (which offers more features)?
Hi Hareesh.
I found the errata after the development phase was over and I started combinatorial testing. We are considering whether to change to eCAN mode or use SCC mode as it is. The amount of modification and the degree of impact on the system when changing to eCAN mode are unknown.
If you have to incorporate the workaround using an external timer anyway, it might be easier to switch to eCAN mode and use the built-in timeout mechanism. You are best positioned to take the decision based on what is best for your application. I am only commenting from the ease-of-implementation point of view.
Think about which one is better.
Not sure if you are asking me a question or if you are saying you will think which approach is better. If it is the former, I regret I cannot make a specific recommendation. You know your application best and a decision cannot be taken without a thorough knowledge of the application/development constraints.