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: 
Visitor kskmyk
Visitor
167 Views
Registered: ‎04-24-2019

XC7K480T-L2FF901I Configuration time

Jump to solution

デバイス「XC7K480T-L2FF901I」を「マスターBPIモード」、コンフィグICは「S29GL01GS11DHV010」を使用した場合、最大コンフィグビットストリーム時のコンフィグ時間を計算した結果、『約1.87sec』(クロック周波数:5MHz時)となりました。
(条件:コンフィグレーション ビットストリーム長さ=149,880,032bit、FlashROMのデータ長=16bit)
仕様的にコンフィグ時間は『0.5sec』程度に抑えたく、方法があればご教示をお願いいたします。

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Xilinx Employee
Xilinx Employee
137 Views
Registered: ‎01-10-2012

Re: XC7K480T-L2FF901I Configuration time

Jump to solution

@kskmyk 

Please be informed the Community Forum is in english.  Community members will be able to guide and respond to you quickly.

I dont see anything wrong with your estimation of 1.87Sec for the Config data in BPI 5Mhz use case.

For BPI Async mode you will max out at 10Mhz as the Flash would not allow async accesss faster than that, So even with 10Mhz (Assume you use EMCCLK to avoid the Tolerance limitaion of CCLK) you still wont be able to reach 0.5sec config time.  Depends on the design though, You can check if compression helps to reduce the bitstream size, you can enable compression in Bitstream settings (BITSTREAM.GENERAL.COMPRESS)  and check how much reduction you  can get, Refer to UG908 for settings.

The realistic alternative will be to use SelectMapx32 or SPIx4 with faster clock configuration mode. (Use EMCCLK if CCLK tolerance needs to be addressed)

 

 

1 Reply
Highlighted
Xilinx Employee
Xilinx Employee
138 Views
Registered: ‎01-10-2012

Re: XC7K480T-L2FF901I Configuration time

Jump to solution

@kskmyk 

Please be informed the Community Forum is in english.  Community members will be able to guide and respond to you quickly.

I dont see anything wrong with your estimation of 1.87Sec for the Config data in BPI 5Mhz use case.

For BPI Async mode you will max out at 10Mhz as the Flash would not allow async accesss faster than that, So even with 10Mhz (Assume you use EMCCLK to avoid the Tolerance limitaion of CCLK) you still wont be able to reach 0.5sec config time.  Depends on the design though, You can check if compression helps to reduce the bitstream size, you can enable compression in Bitstream settings (BITSTREAM.GENERAL.COMPRESS)  and check how much reduction you  can get, Refer to UG908 for settings.

The realistic alternative will be to use SelectMapx32 or SPIx4 with faster clock configuration mode. (Use EMCCLK if CCLK tolerance needs to be addressed)