^

AR# 37626 13.x EDK - "ERROR:EDK:1002 - Data2mem invocation failed"

Data2mem errors when it processes a bit file that has the Quad SPI bus width option set (bitgen "-g SPI_buswidth:4" option). Data2mem also errors when you have the bitgen option -g next_config_addr:0X0000 set. Both of these settings enable multi-boot bitstreams.

How can I work around these problems?

Using the -g SPI_buswidth:4 option produces "ERROR:EDK:1002 - Data2Mem invocation failed."

There are two ways to work around this issue:
  • Do not use Quad mode to configure the FPGA from SPI Flash.
  • BitGen can successfully run data2mem if presented with the -bd option.
  1. After creating the EDK project bitfile and compiling the software program, open an XPS shell and "cd implementation"
  2. Run bitgen with the following options:
    "bitgen -f bitgen.ut -g SPI_buswidth:4 -bd ../TestApp_Memory_microblaze_0/executable.elf -w system.ncd download.bit"
  3. Replace ../TestApp_Memory_microblaze_0/executable.elf as appropriate.

Using the -g next_config_addr produces "ERROR:EDK:1001 - Data2Mem generated errors during execution."

There are two ways to work around this issue:
  • Do not use the next_config_addr option and manually create the header file. (See ML605 Multiboot reference design for an example.)
  • BitGen can successfully run data2mem if presented with the -bd option.
  1. After creating the EDK project bitfile and compiling the software program, open an XPS shell and "cd implementation"
  2. Run bitgen with the following options:
    "bitgen -f bitgen.ut -g SPI_buswidth:4 -bd ../TestApp_Memory_microblaze_0/executable.elf -w system.ncd download.bit"
  3. Replace ../TestApp_Memory_microblaze_0/executable.elf as appropriate.
AR# 37626
Date Created 08/25/2010
Last Updated 07/14/2011
Status Active
Type
Tools
  • EDK - 12.1
Feed Back