I am working with a cmod-s6 and have an application working properly when I program it using a bit file and the Digilent Adept program. The application uses the 4 LED's on the board to indicate state and they change every second. It also spits out RS232 data every second at 115.2 Kbaud. All nice and happy when programed via Digilent Adept. However, When I program it by creating an MCS file, from the same bit file, and write this to the onboard SPI flash device using IMPACT as described is a post I found on this forum it runs about 4 times slower. The application uses two DCM-SP, one to generate 50MHz from an 8MHz MEMs oscillator I've driven a pin with and the other to make 12.5 MHz from the same oscillator. I'm using ISE 14.6 and have checked the CCLK configuration as recommended.
Here is a copy of what I'm referencing when creating the MCS file. I'll also attach the Verilog module that the DCM-SP reside in.
To me its the same bit file and should do the same thing no mater how its programmed. What am I missing?
Thank you for your help.
-Aaron
This can be programmed using Xilinx iMpact.
1. Create BIT file using ISE
- make sure the Generate Programming File/ Properties/ Startup Options/ FPGA Start-Up Clock is CCLK
- otherwise iMpact will prompt and fix this CCLK option
- optional: to speed up the boot process increase the "Configuration Rate" and "Set SPI Configuration Bus Width" to 4
2. Create .MCS file
- start iMpact, (press No then Cancel)
- Create PROM File, SPI Flash, Configure Single FPGA, ->, 128M(bit), Add Storage Device, ->, browse desired "Output File Location", OK
- Add Device - OK, locate the earlier ISE generated BIT file, No, OK, Generate File...
3. Flash programming
- start iMpact, (press No then Cancel)
- Boundary Scan, Initialize Chain
- Right click on SPI/BPI above the FPGA symbol, Add SPI/BPI Flash, locate the .mcs file, SPI PROM, S25FL128S, (optional: for faster programming set Data Width 4)
- Right click FLASH, Program, OK
Question
apailes
Hello,
I am working with a cmod-s6 and have an application working properly when I program it using a bit file and the Digilent Adept program. The application uses the 4 LED's on the board to indicate state and they change every second. It also spits out RS232 data every second at 115.2 Kbaud. All nice and happy when programed via Digilent Adept. However, When I program it by creating an MCS file, from the same bit file, and write this to the onboard SPI flash device using IMPACT as described is a post I found on this forum it runs about 4 times slower. The application uses two DCM-SP, one to generate 50MHz from an 8MHz MEMs oscillator I've driven a pin with and the other to make 12.5 MHz from the same oscillator. I'm using ISE 14.6 and have checked the CCLK configuration as recommended.
Here is a copy of what I'm referencing when creating the MCS file. I'll also attach the Verilog module that the DCM-SP reside in.
To me its the same bit file and should do the same thing no mater how its programmed. What am I missing?
Thank you for your help.
-Aaron
This can be programmed using Xilinx iMpact.
1. Create BIT file using ISE
- make sure the Generate Programming File/ Properties/ Startup Options/ FPGA Start-Up Clock is CCLK
- otherwise iMpact will prompt and fix this CCLK option
- optional: to speed up the boot process increase the "Configuration Rate" and "Set SPI Configuration Bus Width" to 4
2. Create .MCS file
- start iMpact, (press No then Cancel)
- Create PROM File, SPI Flash, Configure Single FPGA, ->, 128M(bit), Add Storage Device, ->, browse desired "Output File Location", OK
- Add Device - OK, locate the earlier ISE generated BIT file, No, OK, Generate File...
3. Flash programming
- start iMpact, (press No then Cancel)
- Boundary Scan, Initialize Chain
- Right click on SPI/BPI above the FPGA symbol, Add SPI/BPI Flash, locate the .mcs file, SPI PROM, S25FL128S, (optional: for faster programming set Data Width 4)
- Right click FLASH, Program, OK
clk_gen_50MHz.v
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.