UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Newbie ajfengr
Newbie
9,369 Views
Registered: ‎10-05-2012

ERROR:Bitstream:25 - 0xd5ae bytes loaded up from 0x0 would exceed promsize 0x8000.

I'm using iMPACT version 14.2 (P28.xd).  I'm programming a Spartan-3AN device, xc3s50an.  The datasheet indicates this device has 1M bits of Flash, of which 437,312 are available for device configuration.  Here's what I get when I try to run iMPACT:

 

Override chain at index 0.
Overriding chain at index 0.
   Sector_Addr  Page_Addr   PO2_Addr   Non-Binary_Addr
1 128 32768 65536 
2 256 65536 131072 
3 384 98304 196608 
'1': Loading file 'C:/xilinx/trace_cpld/trace_cpld.bit' ...
INFO:iMPACT - Elapsed time =      0 sec.
done.
INFO:iMPACT:501 - '1': Added Device xc3s50an successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
file : C:/xilinx/trace_cpld/trace_cpld.bit  used size : 437312
Add one device.Next Start Address=d593
INFO:iMPACT - Current time: 9/3/2013 3:13:39 PM
Total configuration bit size = 437312  bits.
Total configuration byte size = 54664 bytes.
ERROR:Bitstream:25 - 0xd5ae bytes loaded up from 0x0 would exceed promsize 0x8000.

 

     Why is iMPACT failing?  We found an older version of iMPACT (11.1) in a standalone package.  And it seems to work fine.  What's wrong with this version now?  Another odd symptom is when I add the FPGA device to iMPACT, the tool indicates it has 131,072 bits available.  But that's wrong, it should be 1M bits.

     Thanks!

 

 

0 Kudos
1 Reply
Moderator
Moderator
9,362 Views
Registered: ‎06-05-2013

Re: ERROR:Bitstream:25 - 0xd5ae bytes loaded up from 0x0 would exceed promsize 0x8000.

Hi,

It is the issue with Impact 14.2.

To work around this issue Roll back to a previous version of the software.


This issue will be resolved in a future release of software.

 

Thanks,

 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos