Occasional Contributor
Regular ContributorHi
We have not hear from you and this Case is idling. It is not recommended to idle for too long.
Therefore following our support policy, I have to put this case in close status. My apologies if any inconvenience cause
Hence, This thread will be transitioned to community support.
If you have a new question, feel free to open a new thread to get support from Intel experts.
Otherwise, the community users will continue to help you on this thread. Thank you
If you feel your support experience was less than a 9 or 10,
please allow me to correct it before closing or let me know the cause so that I may improve your future support experience.
Regards,
Wincent_Intel
Occasional ContributorWow, it's a carbon-copy from my post on 2/21. Is that <Alt><F3> or <Alt><F5>? (or more likely one followed by the other?)
Two days "idling", then scraped off your shoe. Nice. Nothing says "please go away" like being transitioned to community support.
The demo design included with the PCIe Avalon-MM core produces a Platform Designer entry that has a "generic component" instead of the PCIe core proper. This Generic Component appears to have all of the 2000-ish P-Tile parameters unrolled as a flat file (further evidence that Intel/Altera knows the PCIe Avalon-MM core generator is broken.) While no doubt comprehensive, this is not particularly useful unless you have the P-Tile API document that describes all of the various parameters and their inter-relationships. Any chance Intel/Altera can publish the API so we, the community, can move forward? The P-Tile hardware supports the Avalon-MM interface. The script generating the parameters is broken. Intel/Altera doesn't want to support it. Give me the ability to fix it myself.
