On 2007-03-09, Sylvain Munaut <tnt-at-246tNt-dot-com@youknowwhattodo.com> wrote:
> Hi everyone,
>
> I just installed a new workstation, a Core2 duro running linux 64 bits.
> But I can use data2bram on it, it crashes every time. I've tested with both 8.2 and 9.1 (both with latest service pack). For 8.2 I even tried the 32b and the 64 version.
>
> Using this utility is really important for me to update picoblaze and microblaze software without a need to recompile each time I want to test a new firmware.
>
> Has anyone encountered such an issue ?

I once came upon a system where data2mem would crash completely
under Windows. To make the matter worse this was during a visit
to a company in Shanghai and I really needed to get the design
working quickly on their machine. I don't remember what I did
to solve this but I'm afraid that I gave up on data2mem and
just recompiled the design every time. If I remember correctly
I have also encountered some crashes if the input files to
data2mem are not correct (such as errors in the .bmm file).

You could also try to run data2mem on a different machine. data2mem
does not depend on any other Xilinx library so you don't need a
full install.



Another way to solve your problem if you have no luck at all
in getting data2mem to work could be to use the following flow:

xdl -ncd2xdl yourdesign.ncd
perl acustomperlscript.pl yourdesign.xdl yourbramcontents.txt
xdl -xdl2ncd yourdesign.xdl

Unfortunately this would not be very well integrated into the EDK
flow (which I assume you are using for microblaze at least). Not
to mention that you would have to write the perl script yourself.

/Andreas

Hi everyone,

I just installed a new workstation, a Core2 duro running linux 64 bits.
But I can use data2bram on it, it crashes every time. I've tested with both 8.2 and 9.1 (both with latest service pack). For 8.2 I even tried the 32b and the 64 version.

Using this utility is really important for me to update picoblaze and microblaze software without a need to recompile each time I want to test a new firmware.

Has anyone encountered such an issue ?

	Sylvain