02-05-2019 01:08 AM
I have the following situation:
I am debugging on SDK 2017.3 and at some point I get the message error described in the attachment.
I am attaching to the target so there is no need to check the ps init routine as recommended for this type of error on similar threads.
What possible issues could be for this issue?
02-11-2019 11:29 PM
Did you initialize the DDR controller either using the FSBL or the ps7_init script when launching the debug session? When the device is powered up the DDR controller is not configured so you need to configure it according to your hardware platform configuration (HDF file exported from Vivado).
02-12-2019 01:52 AM
Like I mentioned above I do not run as Standalone Application(therefore no ps7_init) but instead Attached to target. So there is nothing to initialize.
02-12-2019 02:27 AM
The fact of using "Atach to the running target" does not mean you don't need to initialize the memory. This debug type is commonly used when you boot the device from a valid boot image so the device is configured by your FSBL rather than the debugger.
02-12-2019 04:17 AM
When I choose the option to attach it to target, I do not see the ps7_init and DDR initalization options. The FSBL is part of standard zc702 BSP I assume? For sure I don't have my own FSBL. I think those initalization you talk about are made already by the image that is already running on the target before I attach another firmware.
Those options I saw only when debugging as standalone application. i have used Attach to target option fine until now without havind to initliaze something additionally.
I have attached a snapshot of SDK in this debug mode. Could you please point me to where I could check for options to initialize the memory?
02-18-2019 12:03 AM
As we both already mentioned the "Attach to running target" does not have any option to run the TCL script, because is commonly used to attach to a target that is already running and hence configured through the FSBL. The TCL script is part of your hardware platform project, not the BSP, and is based on the Vivado configurations exported to SDK.
What is not clear in your use case is which kind of boot image are you using on your side. Did you create the boot image? How did you create the FSBL? and the most important point, does the Vivado project used for the HDF file the DDR memory configured?
At the end of the day if your vivado configuration of the PS side does not have the DDR configured then neither the TCL script or the FSBL will initialize the DDR memory.