uart_syslink assert
Posted: Fri Apr 24, 2020 5:24 pm
Hello,
implementing some new features in the stabilizerTask, I made the following observation:
As soon as I attach the Loco Positioning Deck I get an assert message tracing back to line 379 of uart_syslink.c. Detaching the deck the firmware keeps on running as desired.
Do you have some advice how to handle this issue? Would it be recommendable to transfer my code to another task, trying to solve this issue by means of task priorities? In fact some parts of the code - related to waypoint planning - are not time-critical but there is some amount of data which had to be passed between this task and the stabilizer task which is the reason why I tried to avoid this so far implementing my algorithm in - maybe not as effective as desired - an iterative fasion.
One minor question I am just curious about: What is the purpose of the compressState/compressSetpoint functions, are they just for processing Logging data?
Any advice would be appreciated! So far, have a nice weekend
Klaus
implementing some new features in the stabilizerTask, I made the following observation:
As soon as I attach the Loco Positioning Deck I get an assert message tracing back to line 379 of uart_syslink.c. Detaching the deck the firmware keeps on running as desired.
Do you have some advice how to handle this issue? Would it be recommendable to transfer my code to another task, trying to solve this issue by means of task priorities? In fact some parts of the code - related to waypoint planning - are not time-critical but there is some amount of data which had to be passed between this task and the stabilizer task which is the reason why I tried to avoid this so far implementing my algorithm in - maybe not as effective as desired - an iterative fasion.
One minor question I am just curious about: What is the purpose of the compressState/compressSetpoint functions, are they just for processing Logging data?
Any advice would be appreciated! So far, have a nice weekend
Klaus