XMD clears core configuration registers after "dow"?

[jmonteiro-dme]

Hi,

We need to download a software project using SDK (or XMD directly) to the on-board DDR3 RAM. We have noticed an issue related to the "dow" XMD command: when the sw application is downloaded, XMD resets the configuration of the PLBv46 PCIe core. As consequence, the PCIe configuration space is reset and we cannot communicate from the PC to the ML605 endpoint no more untill the PC is reset.

Is there any reason to why XMD resets this (or any other) core configurations? Isn't it supposed to simply load the DDR3 with the sw according to the linker script? If this is an issue, is it possible to overcome?

Best,

JM

[elzinga]

Hi JM,

There was an incorrect SDK default behavior where it would do a system reset instead of only a processor reset.  This default behavior was corrected in version 12.3.  What version of the tools are you using and do you see this problem with just XMD as well as with SDK?

[jmonteiro-dme · Accepted solution]

Hi elzinga,

We are using V12.2. We have figured out that by passing:

debugconfig -reset_on_run disable

after "connect mb mdm" in XMD, it no longer resets the system. Also if we pass

debugconfig -reset_on_run processor enable

it resets only the processor when the program is started. This was our desired behaviour.

Best,

JM