Honored Contributor
Honored ContributorMy sdram devices don't show up in my BSP Linker for some odd reason, even if I regenerate a new project. Is it because they require 28 bits to address? They are NOT hooked up to the instruction master, but I don't think that should matter at all. When generating the BSP the sdram memory devices show up in the Memory Map, but aren't available for me to map to any part of the system. If I try to "Add Memory Device" It says that the device 'sdram' is not recognized in the SOPC info, although it is clearly in the Memory Map. I tried manually mapping the sdram device in the BSP Editor, but this caused the memory addresses to overlap with the real sdram device. I tried pointing my sdram device to the heap, compiled and it obviously didn't work. I got a dtrap error and no results.
memory map window (http://i.imgur.com/3pwdhvn.png) generated linker script tab (http://i.imgur.com/aetvh4o.png) Does anyone know how I can make the sdram show up in the BSP Editor? I thought it should do that automatically. I made a test project with one of the DE2-115 demonstration .sopcinfo files, and that sdram showed up fine without a problem. After switching the SGDMA memory read/write sources to the onchip_mem (now expanded to 8Mbits, which is absurd), I can receive the packets, and actually see the wheels turning! Things like the eth struct actually capture the source/destination MAC addresses and the payload appears to be there. Another sample I tried was the DE2-115 VERY BASIC Tx/Rx_Frame sender. It sends and receives packets! I spied on them in signal tap and even captured one of the ping packets from a laptop which had various 192.168.1.1/192.168.1.234 data in it. But now I am experiencing a completely different issue. It seems that once the NicheStack finds a relevant packet, such as a ping/telnet packet, the whole software goes berzerk and just restarts. The debugger states "Stopped due to shared library event". Even running without the debugger, it nets the same results, just I don't get to see the "Stopped due to shared library event" error. When the system receives packets that are not relevant (random broadcasts, or pings/telnets to the wrong IP), it doesn't restart. It only happens when the device is targeted. I tried Recompiling/Clean/Rebuilding BSP and Quarus Projects, but got the same results. Usually when the system gets the ping packet, I am able to sniff one packet escaping through the TX_SGDMA in SignalTap, but after that it seems to just reboot. Interestingly enough, it looks like the response ping packet (all the information in the packet is correct). However, it seems like the TSE is ignoring the packet since I never see any activity on the network switch. I will look into this and see if I can figure out what's going on. Let me know if you have any suggestions!
