Simulation terminates with assertion failed at findmodule function, why?
Do not hook up two generic interfaces such as “AMPromiscous and AMStandard” or “GenericComm and GenericCommPromioscous” into the same application. Normally, you need to choose one of them and make use of all around the application. However, there are TinyOS examples such as DSDV around that uses both. We modified DSDV to use only one of them. Under normal circumstances, TinyOS first tries to deliver message with the promioscous version if delivery fails, it tries it again with Standard delivery. NesCT does not have this functionality and expects you to use only one of them.
Related Questions
- When attempting to run a simulation, I get the following Authorware error stating: "Function ReadExtFile on local files not allowed in non-trusting mode." What should I do?
- Simulation terminates with assertion failed at findmodule function, why?
- Is there documentation about the Simulation Function Blocks?
