Configuration bitstream in FPGA is specific to vendor. It is difficult to understand bitstream format and eventually impossible to know how bits are placed in LUTs, flip flop, multiplexer, input and output interconnection network in FPGA. Normally user is not interested in knowing internals of FPGA, however it is believed that by opening the internals of FPGA, development would become very fast as it is achieved by open source community. In this paper we have proposed a simplified methodology to map configuration bitstream to its programmable resources targeting Spartan-3A FPGA. A simple AND gate design implemented in VHDL under different constraints. Correlation between different locations of AND gate is established with frame address register, XDL file report, FPGA editor and device view in PlanAhead. Keyword-Bitstream, Configuration memory, FPGA, FAR, NCD, XDL I. INTRODUCTION It is widely believed that the analysis of bitstream format is a tedious task. Increase in the complexity of digital circuit design demand for FPGA with more resources is increasing. FPGA has applications in wide variety of domains like space, telecommunications, networking, handheld devices etc. FPGA based industries demand CAD tools for design and development to meet time-to-market design metric. Like in open source communities, FPGAs development techniques are not open and certain things are vendor specific. Hence third party tools development has limited scope. If bitstream format would have been opened to users then possibility of cloning the device and IPs would have increased. Development on design tool side demands FPGAs internal details. Knowing FPGA bitstream definitely helps further development. Beside this, research communities and academicians are interested in knowing bitstream details. Limited work has been done in this direction. A bitstream is a file that contains programming information for an FPGA. FPGAs bitstream is generated by CAD tools and configures (reconfigures) resources on FPGA fabrics to implement desired design. Fig. 1 depicts general structure of bitstream file during configuration. Bitstream file is viewed as file containing header for device name, architecture, and date information. After the start header it has synchronization word, device identification along with various device initialization commands. Most of the data is for actual configuration of FPGA. Last part of bitstream again contains command registers like CRC, DESYNC etc. and then FPGA goes into start sequence operation. These details are contains in bitstream file. Each FPGA device has its own bitstream format to configure itself.