|
If you are using any of the following Xilinx family and you load
your hardware via JTAG and IMPACT: Spartan-3 Spartan-3E Spartan-3A Virtex-II Virtex-II Pro Make sure that the “Pulse PROG” check box is checked in the programming
dialog box. I had the same problem that you are experiencing, and the issue
was that, at power-up, my hardware loads a default Xilinx image to the Xilinx
part. If you do not set “Pulse PROG” prior to using IMPACT to JTAG load your Xilinx
image, the part will not erase, and you will end up writing the new image on
top of the old one. On my hardware this resulted in malfunction of my SDRAM,
which caused Linux to hang at “New klimt: 0xXXXXXXXX”. Also my hardware would pass
a memory test because the Xilinx image that contained the memory test was very
similar to the default image that was loaded at power-up. I did not notice the
problem with SDRAM until I loaded the linux image using xmd and did manual memory
write then read back. From:
owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Thierry
Parrain Hi, I
want to develop a BSP for a Xilinx Board but i have some few problems with the
distribution v0.30-rc1 from Petalogix. Here
below the log: Found
romfs @ 0x8c1df000 (0x00134000) ####
klimit 8c1f8000 #### Moving
0x00134000 bytes from 0x8c1df000 to 0x8c1f7aec New
klimit: 0x8c32c000 And
nothing appends…… Can
you help me. Kind
regards. |