OK, I have a weird problem. I have a block I wrote a couple of months
ago that doesn't seem to be working anymore. I don't think I've updated
anything within uhd-fpga except for some patches that Jonathon sent me
so that I could add the logic in that keeps blocks from blasting data
before the axi interface is setup.
My block is a dataGenerator, basically the same as your siggen, but it
uses a .coe data file for its generated data. What I've noticed is that
when I run your bitfile that you ship, that siggen works fine. When I
run my bitfile, siggen no longer outputs anything to my specAn. When I
try my block and look at it on chipscope, it isn't outputting anything
out until I set the "enable" checkbox (like siggen), so that is good.
When I click "enable," I see the data passing through my block as it
should, but I don't see anything on the specAn, I also don't see the red
LED light up to show that I am transmitting anything on the X310.
If I look at my block going into a fileSink instead of the radio, it
starts blasting data immediately (I think that is a QT issue because
your siggen does that as well), but it looks bit perfect.
What bothers me is:
1) Why does the transmit LED not light up when my block is in play?
and
2) Even in this crappy state, if I use the nocblocks for some other
purpose that doesn't involve the radio (like looking at a freqSink),
everything looks good..... Why would that be?
Those two thing lead me to believe that something is happening to my
radio on start, but I am not sure what or why. Has anyone seen this
before? If not, any idea of things I can debug, or gotchays that might
cause the radio to act up? I'm pulling my hair out on this one.....
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
