^
Advanced Search

AR# 38077 Virtex-6 - What causes the "Bad Packet Error" in the Status Register?

Description

When I perform a "Read Device Status" from iMPACT on my Virtex-6 device, the following error occurs:

[29] BAD PACKET ERROR : 1

What is the cause of this error?

Solution

During the first configuration, after SYNC word is detected, configuration logic checks for illegal packets on several fields:

OPCODE (i.e., op-code=11(reserved)),
Register address out of range
Bad packet type (only type-1, type-2 are legal).

It flags any illegal values as a "Bad packet error" in the Status Register. Once a "Bad packet error" is flagged, configuration logic loads no further data, but INIT is not pulled Low as this is not a CRC error.

Possible causes:

  • This can occur if you have some signal integrity issues corrupting packets.
  • The CCLK frequency isabove the data sheet specification.
  • Contention between RS and Address lines can cause this issue when loading from a BPI flash.
  • A processing error causes the issue. For iMPACT 12.1 and 12.2, this error occurs spuriously as the procedure used to perform a "Read Device Status" triggers a "Bad Packet Error". This issue is resolved in iMPACT 12.3.

Linked Answer Records

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
35448 12.x iMPACT - Known Issues N/A N/A

Actions

AR# 38077
Date Created 09/16/2010
Last Updated 02/25/2013
Status Active
Type General Article
Devices
  • Virtex-6 CXT
  • Virtex-6 HXT
  • Virtex-6 LX
  • More
  • Virtex-6 LXT
  • Virtex-6 SXT
  • Less
Tools
  • ISE Design Suite - 12.1
  • ISE Design Suite - 12.2
Feed Back