Hello,
I have the following setup:
I use a project that depends on the following drivers
When I debug the application I observe that it ends up in an assert statement through the following sequence of function calls:
See also the debug session call sequence
Now I found a similar ticket where one NXP tech-support employee labels this issue as a bug, which may be resolved in a future RTD package release.
To be sure, can you
Best regards,
M_SCH
Solved! Go to Solution.
Hi,
yes, this is RTD issue and will be fixed with next RTD release. It should be version 3.0.0, not sure of the release plan.
Not able to comment more.
BR, Petr
Hi,
yes, this is RTD issue and will be fixed with next RTD release. It should be version 3.0.0, not sure of the release plan.
Not able to comment more.
BR, Petr
Hello,
one more thing.
My current implementation relies on the FlexCAN_Ip_Receive function using interrupts. Which of the following options would you recommend for a temporary fix:
1. Modify the Osif_Internal.h file (so that it matches the implementation of the RTD AR 4.4.0, SW 1.0.0):
#define ResumeAllInterrupts() ASM_KEYWORD(" cpsie i")
#define SuspendAllInterrupts() ASM_KEYWORD(" cpsid i")
2. Use FlexCAN_Ip_ReceiveBlocking - keep in mind that I have multiple message buffers to query.
Best regards,
M_SCH