Sign In

Don't have a Xilinx account yet?

  • Choose to receive important news and product information
  • Gain access to special content
  • Personalize your web experience on Xilinx.com

Create Account

Username

Password

Forgot your password?
XClose Panel
Xilinx Home
Reply
Contributor
rahulrs84
Posts: 38
Registered: ‎10-06-2010
0

IMPACT Read Status Register fails

I am using an ML605. I used Impact to erase the BPI flash device and do a blank check. Both succeeded.
When I attempt to do a "Read Device Status" under Impact, I get a red box message "ReadStatusRegister Failed"
The Flash device is a Numonyx P30.
The JTAG is operating at 3 Mhz (I reduced the TCK from 6 Mhz following some posts on the forum).
Any clues on how to overcome this ?
The impact log is as follows:
--------------------------------------
INFO:iMPACT - Current time: 9/29/11 5:35 PM
// *** BATCH CMD : ReadStatusRegister -p 2 -bpionly 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 16700000.
Validating chain...
Boundary-scan chain validated successfully.
2: Device Temperature: Current Reading:   29.70 C, Min. Reading:   28.72 C, Max. Reading:   40.53 C
2: VCCINT Supply: Current Reading:   1.011 V, Min. Reading:   1.008 V, Max. Reading:   1.014 V
2: VCCAUX Supply: Current Reading:   2.502 V, Min. Reading:   2.496 V, Max. Reading:   2.508 V
'2': Read Status Register command is not supported for 28F256P30.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
Thanks 
RRS
Xilinx Employee
jlarkin
Posts: 164
Registered: ‎08-10-2007
0

Re: IMPACT Read Status Register fails

rahulrs84,

 

This post would be better served being moved to the Other Tools thread, as the issue appears in iMPACT, and is an iMPACT error.

 

However, I believe I can help answer this for you.

The problem here is you are trying to read the status register of the P30.  ReadStatusRegister in iMPACT is intended to be used to read the status register of Xilinx FPGAs, not third party flash devices.

For more info on the Status Register, please see Answer Record 24024: http://www.xilinx.com/support/answers/24024.htm