This example is similar to the one used for the analyze-hw
subcommand. Here a
PDI is programmed on the wrong targeted device. This is the command used for this
example:
pdi_dbg_util program -t 0 -u TCP:myhost:3121 design_top.pdi
Again, the -t option is not required because the target device is 0. However, it was added to illustrate using the target index option.
The output of this example is similar to the following:
INFO: Programming device with: design_top.pdi
Device program progress ━ 21% Aborted
An error occurred during programming: PLM Error Major 0x326 Minor 0x14 occurred during programming.
Analyzing Error Status....
No Errors found for rom
PLM Major Error: 0x0326
--------------------------------------------------
Name: XLOADER_ERR_GEN_IDCODE
Description: Error if Vivado configured part (IDCODE) mismatches with the actual part
PLM Minor Error: 0x0014
--------------------------------------------------
Name: XLOADER_ERR_IDCODE
Description: IDCODE mismatch
In this output, the program
subcommand starts by configuring the
device with the PDI file. The programming status denotes the progress; in this case,
it ceases at 21% due to a reported error. The error status is presented, initiating
the analysis process. The analysis involves deciphering the error and subsequently
concluding the analysis.