| View previous topic :: View next topic |
| Author |
Message |
gmiller
Joined: 07 Mar 2006
Posts: 105
Location: Simi Valley, CA.
|
 Posted: Mon May 19, 2008 3:19 pm Post subject: Downloading an image to the X5-400M EEProm |
 |
|
| Quote: | Question:
When I try to burn an image into the X5-400M it states this is a non approved Image as the Golden Image. Load an approved golden Image.
What is this about ? |
The VSPROM program has a feature that allows it to hold two bit images. A "user" image is the one set by default to be re-programmed by the user. And a safety image or "golden" that is programmed at the
factory, in case the user burns an image that has a problem, ie. wouldn't boot. At boot time, a jumper selects which image to boot.
The user is not allowed to burn the golden image for his own protection. The VSPROM has a check box that's used to select which image to burn. If it is checked, it will burn to golden one. This is not recommended. The check box should be always *unchecked* by the user. Please ensure that this check box is unchecked.
| Quote: | Question:
Through the Jtag interface :
We do not have the image of the second target in the scan chain. We
programed the Virtex5 anyway an it seems to perform correctly but Verify is not functioning so we are not sure of the outcome.
s the .bit for the second target mandatory or not ? |
The second target is the CPLD that programs the FPGA on boot-up. It should not be programmed or erased, just bypassed. FPGA program verification requires a mask file we don't provide.
The bit file has a checksum that is compared by the FPGA on programming; if it doesn't match, the part fails with an error message. Since the Jtag does this very strictly the end result is the verify is not needed.
| Quote: | Question:
If I burn a bad image how do I recover from this. |
You need Impact and Jtag.
Take a known good image .bit file. (Usually you can count on the one included in your ToolSet.).
Place the jumper on the X5-400M
(JP3 on Rev C and above, this is located on the edge near the P16 connector).
Restart the computer. The Golden image will now be loaded. This will allow you to burn in your default image to the user sector.
Note: you should not try to download to the Golden image sector. This is a safe image to fall back on. Contact Innovative if this needs to be changed for any reason. The default user image is where all loads should be done for user code. |
|
| Back to top |
|
 |
strusc
Joined: 06 Jan 2009
Posts: 12
|
| Posted: Wed Jun 03, 2009 9:41 am Post subject: JTAG EEPROM |
|
|
How can a user program the EEPROM without using VSPROM? If a user has custom firmware in the FPGA, programing in the Innovative core, rebooting, loading the driver, installing wxwidgets just to run VSPROM is a bit of a work around.
On revision E, what is JP2, is this the factory JTAG connector to the EEPROM? How do you load the original firmware into the flash at the factory, Can you provide the HDL / documentation on loading the EEPROM through the CPLD so that it can be injected into our custom FPGA code.
Thanks |
|
| Back to top |
|
|
judywp
Joined: 11 Sep 2009
Posts: 5
|
| Posted: Mon Oct 05, 2009 5:51 am Post subject: Use .BIT or >EXO file for VSPROM? |
|
|
| When Using VSPROM, does one provide the .bit file or do we need to create a .exo file. If the answer is to create a .exo file - what is the command line used to create this file. I only see .bit images supplied in the code examples. |
|
| Back to top |
|
|
Pat Carr
Site Admin
Joined: 02 Nov 2007
Posts: 244
Location: CA, US
|
| Posted: Mon Oct 05, 2009 9:44 am Post subject: |
|
|
You can use a .bit file with VSPROM. Change the file browser to display all files (*.*) and pick a .bit file.
There's no need to convert to .exo. |
|
| Back to top |
|
|
marco.palumbi
Joined: 16 Sep 2009
Posts: 17
Location: Rome - Italy
|
| Posted: Tue Oct 13, 2009 6:04 am Post subject: |
|
|
Hello,
I need some clarification about the first post of the thread.
can you explain better at the point
> Question:
> If I burn a bad image how do I recover from this.
1) why and how do I have to use Impact an Jtag: if I boot with the "golden" image, should I be able to flash the default image with Vsprom?
2) which is exactly the name of the default image and under wich directory I find it for Rev E board?
thanks
Marco |
|
| Back to top |
|
|
Pat Carr
Site Admin
Joined: 02 Nov 2007
Posts: 244
Location: CA, US
|
| Posted: Tue Oct 13, 2009 9:54 am Post subject: |
|
|
| marco.palumbi wrote: | > Question:
> If I burn a bad image how do I recover from this.
1) why and how do I have to use Impact an Jtag: if I boot with the "golden" image, should I be able to flash the default image with Vsprom? |
Yes, if you are able to boot the 'golden' image, then you could flash a default image with VSPROM. If, for some reason, you can't get an image loaded, you'd need Impact. For instance, it could happen that the CPLD gets accidentally erased, or both images are overwritten.
| Quote: | | 2) which is exactly the name of the default image and under wich directory I find it for Rev E board? |
In the latest builds, you would find the default image under 400M/logic/rev_e/rom with the name x5_400m_routed.bit. In previous releases, it would be under 400M/logic/rev_e/syn
There's also a copy of the image in /Hardware/Images/RevE |
|
| Back to top |
|
|
marco.palumbi
Joined: 16 Sep 2009
Posts: 17
Location: Rome - Italy
|
| Posted: Wed Oct 14, 2009 6:32 am Post subject: |
|
|
Some clarification:
1) in Vsprom from my windows installation there isn't any check box to chose from golden/user image to flash (i have Vsprom ver. 1.3.0.0)
2) I found x5_400m_routed.bit in C:\Innovative\X5-400M\Hardware\Images ( not .....Images//RevE ) and I tried to load it with Impact (without flashing): the led behavior is different and the host fails to enumerate the board over PCI.
what is wrong? |
|
| Back to top |
|
|
Pat Carr
Site Admin
Joined: 02 Nov 2007
Posts: 244
Location: CA, US
|
| Posted: Wed Oct 14, 2009 8:50 am Post subject: |
|
|
| marco.palumbi wrote: | Some clarification:
1) in Vsprom from my windows installation there isn't any check box to chose from golden/user image to flash (i have Vsprom ver. 1.3.0.0) |
That is correct behavior. The check box is hidden from the user, to avoid him accidentally overwriting the golden image.
| Quote: | | 2) I found x5_400m_routed.bit in C:\Innovative\X5-400M\Hardware\Images ( not .....Images//RevE ) and I tried to load it with Impact (without flashing): the led behavior is different and the host fails to enumerate the board over PCI. |
I suspect you have an old framework logic. Try downloading the latest release from here: X5 400M release
Or better, the beta release from here: X5 400M Beta release |
|
| Back to top |
|
|
marco.palumbi
Joined: 16 Sep 2009
Posts: 17
Location: Rome - Italy
|
| Posted: Wed Oct 14, 2009 9:56 am Post subject: |
|
|
hello Pat,
but Vsprom says to me that it is not a golden image and refuses to flash..
so which is the correct way to flash the user image?
Marco |
|
| Back to top |
|
|
Pat Carr
Site Admin
Joined: 02 Nov 2007
Posts: 244
Location: CA, US
|
| Posted: Wed Oct 14, 2009 10:51 am Post subject: |
|
|
| marco.palumbi wrote: | hello Pat,
but Vsprom says to me that it is not a golden image and refuses to flash..
so which is the correct way to flash the user image? |
I just ran an experiment to reproduce your issue. The CPLD has lost its image.
I'm attaching the CPLD image for flash type 128N which is the most common.
You'd need to burn it using Impact onto the CPLD device. Then power-cycle the PC (not warm reboot). |
|
| Back to top |
|
|
lkremer
Joined: 05 Mar 2010
Posts: 5
|
| Posted: Thu Jun 10, 2010 3:21 pm Post subject: No success load user image |
|
|
1- I had no success loading a user image into EEPROM using VsProm. I've checked out the image using USB JTAG. The image works fine when loading it via JTAG.
VsProm appears to work (see transcript attached), but when I reboot the default image appears to be loaded.
I've attached a copy of the VsProm transcript and the .bit file I'm trying to load.
2- I tried making a .EXO via the procedure in the X5-400m Framework Logic Usr Guide. Note, the instructions for for ISE 10.1. ISE 11 is a bit different. VsProm complains the the .exo is not a proper .bit file and chokes.
3- The manuals indicate tha the EEPROM can be loaded via the JTAG (using an EXO file), but I didn't find detailed instructions.
Notes: JP3 is open.
The X5-400m is mounted on an II PCI carrier card.
Can someone point me in a direction? |
|
| Back to top |
|
|
lkremer
Joined: 05 Mar 2010
Posts: 5
|
| Posted: Thu Jun 10, 2010 3:30 pm Post subject: No success load user image (cont.) |
|
|
Seems that a .bit is attachement is not allowed. I changed the extension from .bit to .txt (nothing else seemed to work). But then the file was too large.
Let me know if either the .bit or the .exo would be helpful and I'll send it via e-mail. |
|
| Back to top |
|
|
Pat Carr
Site Admin
Joined: 02 Nov 2007
Posts: 244
Location: CA, US
|
| Posted: Thu Jun 10, 2010 3:50 pm Post subject: |
|
|
The log indicates that your board is using an X Type ROM, not an N Type as attached in the previous post. It's likely you're using a newer board. The previously attached CPLD image won't work on your set up.
I'm attaching the CPLD version for X-Type ROM (ie. Flash memory).
Always remember to power-cycle the host computer after flashing with VSPROM. |
|
| Back to top |
|
|
lkremer
Joined: 05 Mar 2010
Posts: 5
|
| Posted: Mon Jun 14, 2010 6:42 am Post subject: |
|
|
Still nNo luck programming my FPGA image onto the X5-400m (rev F) card.
1 - Reprogrammed the CPLD with vsprom_x5.jed image attached to previous post using IMPACT.
2- Cycled power
3- Programmed FPGA user image with x5_400m_doppler3.bit image (attached to recent posting) using VSPROM.exe (log attached)
4- Cycled power
5-Image did not function as expected.
Note: My .bit file workes when downloaded to the FPGA via the JTAG, but it is volatite.
Any other suggestions? Is there a way to program the fpga's flash memory via the JTAG?
Thanks, Larry |
|
| Back to top |
|
|
Pat Carr
Site Admin
Joined: 02 Nov 2007
Posts: 244
Location: CA, US
|
| Posted: Tue Jun 15, 2010 1:37 pm Post subject: |
|
|
Given that your image (ie. doppler3) has trouble burning the flash thru VSPROM, you could try loading the stock image thru JTAG, restarting, burning the flash with your image, and then power-cycling to load it.
This may be a workaround, because for the next version, you'll have to repeat the cycle.
Did you have timing issues on your build? These could cause routing to be impaired, so unexpected issues may arise. |
|
| Back to top |
|
|
|
