ISE does not initialize the bitstream of a EDK project

I have a project EDK system.xmp in ISE. ISE does not initialize the bitstream even if I do a update bitstream in ISE. I had to import ISE to EDK and do update bitstream so that it works on my FPGA board. Looks like EDK does it correctly and not ISE. I also tried to use my project in ISE with an export to ProjNav with the EDK tool. Same thing I had to import my ISE project to EDK to initialize it correctly.

I also tried to put my .elf and .bmm file in ISE. But does not change anything. I use ISE 7.1.04i and EDK 7.1.02i I found my answer to initialize my bitstream at: Exporting a EDK design to Project Navigator

formatting link

It is important that i use my EDK project in my ISE project and not the other way around.

Why does ISE do not initialize the memory of the BRAM or bitstream?

Francis St-Pierre

École Polytechnique de Montréal
formatting link

Key Words: EDK in ISE, ISE with EDK, system.xmp in ISE project, unintiliazed .bit

Reply to
Francis
Loading thread data ...

I have a project EDK system.xmp in ISE. ISE does not initialize the bitstream even if I do a update bitstream in ISE. I had to import ISE to EDK and do update bitstream so that it works on my FPGA board. Looks like EDK does it correctly and not ISE. I also tried to use my project in ISE with an export to ProjNav with the EDK tool. Same thing I had to import my ISE project to EDK to initialize it correctly.

I also tried to put my .elf and .bmm file in ISE. But does not change anything. I use ISE 7.1.04i and EDK 7.1.02i I found my answer to initialize my bitstream at: Exporting a EDK design to Project Navigator

formatting link

It is important that i use my EDK project in my ISE project and not the other way around.

Why does ISE do not initialize the memory of the BRAM or bitstream?

Francis St-Pierre

École Polytechnique de Montréal
formatting link

Key Words: EDK in ISE, ISE with EDK, system.xmp in ISE project, unintiliazed .bit

Reply to
Francis St-Pierre

"Francis" schrieb im Newsbeitrag news: snipped-for-privacy@polymtl.ca...

1 the .BMM support in ISE has been a problem forever. 2 DO NOT USE import or export between ise edk

the only way to get it working properly is to add the edk as submodule in ISE project, to update the sw you double click on it, then compile the sw in xps and close xps and run bitgen in ISE.

the only known way to me todo it.

Antti

Reply to
Antti Lukats

Francis I used to run this little script (below) after running ProjNav. There are other options to data2bram that help verify the correct data is going to the right bram. This worked with ISE6_2.

-Newman

####################################################################### # This script runs data2bram to populate BRAMs with program information. # This is automatically generated by LibGen. # ####################################################################### echo Initializing BRAMs with program information ... echo Inserting executable image

data2bram -bm implementation/system_bd -bt projnav/system -bd ppc405_i/code/executable.elf tag bram1 -o b projnav/download.bit

Reply to
Newman

formatting link

I have the EDK project within an ISE project.

From version 7.1 (I think, but not sure), I have been forced to follow this procedure:

  1. Compile new/updated project
  2. Tools/Clean Bits (took a while to fin this!)
  3. Go to ISE and Uopdate Birtstream with Processor Data

And there you are.

Reply to
Zara

Thanks for the answer. In ISE 7.1, data2bram has been changed to data2mem. This is already done in ISE, it prints out:

Analyzing file microblaze_UNI/code/executable.elf... Running Data2Mem with the following command: data2mem -bm implementation/system_bd -bt implementation/system.bit -bd microblaze_UNI/code/executable.elf tag bram1 -o b implementation/download.bit Memory Initialization completed successfully.

Looks like it initialize it, but program runs correctly only when imported back to EDK and doing a Update Bitstream.

Newman wrote:

Reply to
Francis

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.