-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Is there ability to flash Mercury 1 board on Linux? #1
Comments
Sorry you are having trouble programming your Mercury 1.
The Mercury 1 board uses an entirely different programmer utility that can
run on top of the mono runtime in linux. The reason for the different
program is that Mercury 1 has a slightly different interface to the flash
chip. The Mercury 2 board's interface was redesigned for faster programming.
Here's a link to the linux version of the Mercury programmer:
https://www.micro-nova.com/s/MercuryProg338_linux.tgz
To use the programming utility you will need to install the mono runtime
and use mono to run the utility. Here's how I do it on my debian based
machine:
tar -xvf MercuryProg338_linux.tgz
sudo apt install mono-complete -y
mono Mercury_Programmer.exe
Other resources can be found here:
https://www.micro-nova.com/resources-mercury
I hope this helps
|
@linknum23 That definitely helps. Thanks! One more question, if I may, my Mercury 1 board suddenly stopped holding the flashed data. Do you think I might have damaged the device or is there like a configuration in ISE that I could use to fix this? |
This sounds like a hardware issue, could you email us at support@micro-nova.com so we can see about correcting this for you? |
Hi,
I am one of the early purchasers for your Mercury 1 board and have contacted you a couple of years back regarding Linux support for Mercury board. I am glad that there is Linux support now for your new Mercury 2 board.
I was wondering if there is a chance to program Mercury 1 board with this tool? Hopefully there is one :)
Here is what I did so far;
Add to /etc/udev/rules.d/99-libftdi.rules;
Execute;
Execute;
With this I am able to see device is recognized now;
Any advice is appreciated. Best of luck in your future endeavours.
The text was updated successfully, but these errors were encountered: