I updated to EDK 9.2 primarily b/c we are building a new project and I wanted the latest MPMC3 core. Here are some things that I have noticed while using it:
1) Instance name changes in the EDK GUI do not propagate to the MHS file. So if you change a name, and the GUI updates, the name changes back to what it was when the core was pulled in. You have to manually change the MHS for a name change to stick. No big deal. There is an easy workaround...but annoying.2) The MPMC3 configuration GUI displayed the correct address width and bank address width for my DDR2 memory. However, it did not propagate those parameters to the MHS. The core then uses the default MPD values...which are incorrect. I had to manually add the changed parameters to the MHS. What worries me is that there are other parameters that were not propagated to the MHS.
3) I am using one port of the MPMC3 as an NPI implementation. My custom IP is setup with the correct NPI information (Answer Record 24912). In EDK 9.1 the MPMC2 NPI port connected directly to my custom IP in the bus configuration tab area. Now I cannot connect the MPMC3 to my peripheral. There are 'No connections' available from the MPMC3 side of things. My custom peripheral looks the same as in EDK 9.1. I had to resort to manually connecting the bus interfaces in the ports tab.4) In simulation, the MPMC3 core goes into calibration mode and runs infinitely. I have dug into the HDL enough to know that it is stuck in one state of the physical layer cal routine. The DDR2 memory seems to be behaving itself.
5) I added an older OPB custom peripheral and all the bus IP and bridging IP needed. I assigned an address range for the custom IP. However, libgen would not update the xparameters.h file with that address info. I added it manually, but the next time libgen was run, that info was blown away.All of the above used to work when I had an EDK 9.1 project and an MPMC2 core. I've opened WebCases for most of these items.
Anyone working with EDK 9.2 experiencing these or other issues?