Got it. I fat fingered the register location in the XML, so my
verilog was never catching the message. Once I got them synced up
it seems to take the message. Thanks!
On 05/04/2017 01:40 PM, Jason Matusiak
wrote:
EJ,
I made modifications to my C++ files and now GRC isn't complaining
anymore!!! Thank so much, that was a huge help.
Now I am trying to strobe some values into my block to make sure
it is working, but I am not getting the results I expect. So I
believe that my block is expecting a PMT value with a name of
"offset" and an integer value to follow. What i tried to do in a
Message Strobe block (as well as a Periodic Message Source), was
to set the Message PMT to be:
pmt.cons(pmt.intern("offset"), pmt.to_pmt(10))
If I connect it to the print input of the Message Debug block, I
see the output:
******* MESSAGE DEBUG PRINT ********
(offset . 10)
************************************
But I am not sure why there is a '.' in the middle there. Is
there some other way that I should be setting up the PMT message?
TIA!
On 05/03/2017 10:17 AM, EJ Kreinar
wrote:
Hi Jason,
I believe I have seen this issue when I did not register
the message port correctly, or when names did not match
between GRC and the message port name.
Hope this helps,
EJ
|