In system memory content editor

Hello,

regularly, the editor shows all existing instances, when you scan the device. You can select one at a time to communicate with. You should first check in compilation report if both instances actually have been created. The memory instances must have an unique numeric instance ID in addition to the displayed name, but with default settings it is choosen automaticly. You can see this also from the report.

Regards,

Frank

Thanks,

I can's see the instance ID in the compilation report.

In the RAM summay of the Analysis & synthesis report I see the instantiation of the 2 RAMs but not a special ID number.

I did change the RAM ID but in the In system memory editor i see the RAMID name of an older run with 1 RAM, and I don't see the 2 ram ID's of the new run with 2 RAM's.

I don't get rit off the old ID name.

Regards,

Wim

Hello,

I thought it could be that the in-system memory content editor window shows outdated info, as it could happen with source&probe tool. But I saw, that when you perform a scan chain, you get always an updated display of all existing memory instances, respectively No Instances Found. So I think the only way to see outdated instance info is that the most recent compilation result wasn't loaded to FPGA. This could happen e. g. if you once selected a different *.sof file in JTAG Chain Confuguration or the JTAG configuration was overwritten from a different configuration source also in effect.

Regards,

Frank

Thanks,

I have find out that First you need to program the FPGA with the programmer itself and not to try to program it with the In System Merory Content Editor as can be done with Signal- tap tool.

I find now 2 RAMS with index 0 and 1.

Thanks for you help

Regards Wim