Forum Discussion
Can you clarify better what signals you can and cannot see? You say you "see the ones driven by the logic", but you can't see "the signals coming from the IP"? It's not clear what you mean by this. Like you can see the address bits (signals from logic to IP) but not readdata from the IP?
If you are talking about the memory signals that go out to the external memory, you can't tap those signals assuming you are using the hard controller.
My issue is the the avalon bus signals that are outputs of the IP. Namely, readdata, datavalid, and ready. They do not show up in signaltap neither presynthesis nor post fitting. Signals used as input to the controller which are driven by RTL show up fine.
- sstrell8 months ago
Super Contributor
ready is not an Avalon signal. Do you mean waitrequest?
Can you show your design instantiation or design in Platform Designer and screenshots of what you're seeing when you try to tap the nodes in Signal Tap? If you're leaving signals unconnected, they may have been optimized away.
- JuanEscobedo8 months ago
New Contributor
Hello,
I have attached the source RTL of my top level design and the top level RTL of the DDR3 controller generated by the wizard for your reference.
As you can see, avl_ready is indeed one of the ports of the avl interface for the DDR3 controller.
Below are the screenshots of the signals that show in post-fitting and pre-synthesis: