Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

Avalon MM Read of Custom module returns "deadc0de"

TuckerZ
New Contributor II
1,592 Views

Hello, 

 

I am having troubles diagnosing and solving this error. I mainly can't diagnose it because I don't know what is going on. 

 

I have created some custom HDL using SystemVerilog that I have put into a module and turned into a Platform Designer IP (_hw.tcl). This module uses an Avalon Memory Mapped Interface. I have compiled the project with no errors and programmed the target FPGA. When I attempt to read from the module using system console, I get back the 32 bit hex word "deadc0de". I am not sure what is generating that word because my code doesn't implement that. All reads to the module (this includes the base address and offsets) returns "deadc0de". 

 

I created two other modules with the same interface and they also have the same issue. I have other custom Platform Designer components using Avalon MM interfaces that were coded in VHDL by other people and they work. 

 

What is returning "deadc0de"? Why is it returning "deadc0de"?   

 

Thank you

0 Kudos
1 Solution
TuckerZ
New Contributor II
1,546 Views

I re-examined the Platform Design and I found the error. I had assumed the new modules were hooked up to System Console's Avalon port. They were not. "deadc0de" is the output from the default slave. I attempted a search of the code to find it originally, but it was hidden and I did not find it. Thank you for the direction. 

View solution in original post

0 Kudos
3 Replies
sstrell
Honored Contributor III
1,572 Views

Definitely need more information here, like what the system design looks like, maybe code of your custom component, etc.  If you are addressing a non-existent address space in a Platform Designer system, there is a "default agent" set to respond, so it could be that.  You don't mention what address you are trying to access.

Really just need more details.

0 Kudos
TuckerZ
New Contributor II
1,547 Views

I re-examined the Platform Design and I found the error. I had assumed the new modules were hooked up to System Console's Avalon port. They were not. "deadc0de" is the output from the default slave. I attempted a search of the code to find it originally, but it was hidden and I did not find it. Thank you for the direction. 

0 Kudos
SyafieqS
Employee
1,487 Views

I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, Please login to https://supporttickets.intel.com/, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.


p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution, give Kudos and rate 5/5 survey


0 Kudos
Reply