Wondering About the Auto-Generated "portNum" Parameters #2128
Unanswered
John-P-Cargille
asked this question in
Q&A
Replies: 1 comment
-
After successfully building my project and running it in the gds, my code actually failed some "Fw::Assert"s, when I ran commands, which I found later to be caused by me passing the "opcode" parameter from the command handler into my pOut_out() calls as an argument. Changing this argument to 0 fixed the issue, but I'm still not sure why it did. Maybe it was struggling to translate from hexadecimal to decimal? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey All,
I keep seeing an auto-generated parameter in my port handler functions called
const NATIVE_INT_TYPE portNum
. What are you generally supposed to supply as an argument for this parameter, when you make a call to some Port P "pOut_out()"? Should it be an opcode, if you're making the port call from inside a command handler? Should it be 1 as a default to indicate success? What is the actual purpose of this parameter? I also don't know if there's a difference in how this portNum parameter is generated for synchronous versus asynchronous ports.Thanks!
Beta Was this translation helpful? Give feedback.
All reactions