Flashing the firmware #80
Comments
|
Thanks for making this. I will add in my process and pictures. Process:
One thing that I want to note is that I had to remove the Pot on r27. I originally removed it, added conductors to the legs and re-attached it. The VIC board was hitting the top of it and would not press down all the way with r27 in it's original spot. I then removed it entirely to see if the image stability would change. It got better, but was still off by a lot. I have not reinstalled it while attempting to update the board since I don't even have the JST hooked up from the VIC to the board during programming. I could try that. What I have tried:
What I have not tried:
Pictures of all the things:
|
|
The things you did not try 1 - 3 should not make any difference. Especially 2 and 3 are totally unrelated to the FPGA. But actually it would make sense to check for the stability of the 3.3 volt rails on the FPGA board. If you have an oscilloscope you could check of there is some noise present. Probe both sides of each of L1 - L3. Also try to just program CFM0 (configuration flash memory 0) and not UFM (user flash memory) in one step and see if this alone would succeed. You could then try to programm the other part independently. When switching to a different quartus version also does not make a difference, I have just one last idea: By the way: It is interesting how different the two USB-Blaster devices look at the inside. |
|
The board was verified working by myself using the dedicated signal generator as outlined in #47 so it has been flashed successfully in the past however I couldn't remember what version of firmware was programmed. I have also occasionally had difficulties with programming the boards but often it would start writing and then fail at random percentages of completion rather than just abort at 4%. For reference, my USB blaster looks different to both of the ones @amerika13 has:
|
|
I tried UFM and CFM0 individually and they both stop at 4%. Here are the log messages from the Quartus System window.
@bodgit did tell me that when he programmed the chip, he had all the flags checked. Including Security Bit. I don't know anything about security on these guys, but I hope that didn't lock the chip out from being updated in the future. Is that perhaps the issue? The Security Bit option is greyed out and unusable for me. I'm not sure what that entails and I've googled quite a bit on the subject and have learned very little as there isn't much discussion. And what little there is, is divisive.
|
|
I can choose the Erase option for CFM and UFM and it will say that it was 100% successful. But the Blank-Check option also fails at 4% as does Verify. |
|
This security bit may indeed be something. I actually never used it and I could not even check it anyways, so I never bothered. Same as you, I don't even know what this actually does. It would be a real bummer if this now actually renders your FPGA permanently unusable. |
|
@amerika13 Do you have a scope? It would make sense to check how TCK, TMS and TDI look at the board end, and TDO at the programmer end. |
I do, but I only got it a couple weeks ago and would need to learn it. Siglent SDS1104X-E 4-Ch 100MHz |
|
Hi all, got the same "4%" problem here as all the people above. I tried different Quartus Versions on W10, W11 and Linux and also three (!) different USB-Blasters, even the more expensive Terasic one. Problem still persists. |
|
Additional comment: The security bit on my programming interface of Quartus is not set. By the way erasing the chip works on my side, too, but the blank check also fails at 4%, no matter what USB Blaster or operating system I use. |
I suspect what is more likely is that I just ticked everything that could be ticked. Given nobody else can enable that security bit, in all likelihood I wouldn't have been able to either. |
OK, so your issue is identical to mine then. I will be pulling the board from the c64 today, powering it separately and removing the jumper for 12v to set it back to the way it was when it was originally programmed and then try again. That is a long shot to try, but I might as well. |
|
I also have exact same problem, it fails at 4%. Board was confirmed working before my programming attempt. Tried 2 different USB blasters and two different computers, both with Windows 11 and Quartus version 21.1. |
|
Tried with Quartus 18.1 on Windows 11 and it worked! I'm using Waveshare Altera USB blaster. |
|
This are good news!!! :-) |
|
I haven't gotten to test it yet, but using Quartus 18.1 so far looks to have at least gotten me this far. Programming and verify went through without issue to 100%. I'll be able to test after I get off work.
|
|
I would love to know if there's some software other than Quartus that can do the JTAG programming. If you're not actually developing the FPGA code, Quartus is a lot to download just for that purpose. |
|
I was able to program the board using OpenOCD 0.11. You will also need:
My OpenOCD config file adapter driver usb_blaster jtag newtap 10m02 tap -irlen 10 -expected-id 0x031810d My command line openocd.exe -f videomod.cfg -c init -c "svf firmware_2.11_beta1.svf" -c shutdown -l out Initially you may wish to drop PS. @bodgit please see my private message on BeamRacer forum. ;) |
|
I flashed the device successfully with firmware 2.10 yesterday late evening, testing included. Everything worked like a charm. The component mod is perfectly up and running. Thanks to all for their effort. A success story, so far! |
|
I would like to report the same findings. Quartus Lite 21.2.0.842 errors out at 4%. Quartus Prime Lite 18.1 successfully programmed 2.10 onto my c0pperdragon composite video mod. Running on Windows 10 x64, using a very inexpensive ($9) USB blaster from Amazon. Now my PAL C64 250407 rev. A with the bad clock circuit bypassed (clock from FPGA) has beautiful stable component video picture without any glitches. Hurray! Many thanks to flegmatik for discovering the working version. |
|
I haven't discovered it, I just used the same version as c0pperdragon. Figured to try the version that works for the guy that created |
|
I recently built my 2nd one of these, but forgot many of the problems with Quartus 18.1 and my cheap USB-Blaster clone. Essentially Windows just does a BSOD as soon as I plug the Blaster in. I suspect it loads the driver expecting a different IC then crashes as the clone Blaster is not the same hardware. I know there is a way around this by changing the driver but it's a pain when it BSOD's every time. Then I tried installing Quartus into Linux but it would only install 60% then halted. So I used my Raspberry Pi 3 with OpenOCD. You can use the config files as above in laubzega's post but make sure the path for the svf file is exact. If You use lower case where there is a capital it will fail with a "no such file or directory error". I had all files in documents but You still need to provide the path for the svf file separately. I've added the svf file here for anyone who doesn't want to install Quartus just to convert the file. |
|
Hi @Imperious685, |
|
I ordered the boards from PCBWAY and the parts from Digikey then built it myself. You can not currently get the FPGA's from anywhere so unless they become available again You won't be able to get one of these. This is off topic for this subject anyway so Copperdragon may remove these comments later. |
|
FPGAs are back in stock at Mouser, I didn't want to believe it myself until I actually had them in my hands. After a wait of two and a half years, I finally finished building this mod, only to hit a horrible issue when attempting to program the FPGA which crapped out at 4%. I was cursing the cheap USB Blaster clone I bought from eBay in 2021, but thanks to this thread it was that later version of Quartus that was the problem. I am now running Quartus Prime 18.1 on Windows (I'm a Linux user but Debian 12 doesn't play nice with 18.1) and it works perfectly. Once again, thank you all for sharing this info. @c0pperdragon you are a legend! |
|
Congratulations! Building the boards successfully is no easy task. |
|
I tried using a CH552 based programmer and it couldn't even detect the FPGA. I've now gotten an FTDI 2232 based programmer that can detect the FPGA but I get an immediate failure when I go to flash. I've tried a few different DLLs from different FTDI based programmers but the result is always the same. Not sure what I'm doing wrong. Has anyone been able to flash this device with one of these FTDI programmers? Thanks. Info (209060): Started Programmer operation at Tue Nov 07 21:17:44 2023 |
|
I'm pretty sure I used an Altera Blaster to update mine some years ago. Could be wrong - it's been a while since I last played with my C64.Sent from my iPhoneOn Nov 7, 2023, at 3:21 AM, insanity213 ***@***.***> wrote:
I tried using a CH552 based programmer and it couldn't even detect the FPGA. I've not gotten an FTDI 2232 based programmer that can detect the FPGA but I get an immediate failure when I go to flash. I've tried a few different DLLs from different FTDI based programmers but the result is always the same. Not sure what I'm doing wrong. Has anyone been able to flash this device with one of these FTDI programmers? Thanks.
Info (209060): Started Programmer operation at Tue Nov 07 21:17:44 2023
Info (209017): Device 1 contains JTAG ID code 0x031810DD
Error (16353): Expected the Max 10 device at index 1 to be of type compact, flash or analog, but detected device of type invalid instead. Ensure that you are using the correct programming file.
Error (209012): Operation failed
Info (209061): Ended Programmer operation at Tue Nov 07 21:17:45 2023
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
FWIW, seems that the cheap FTDI and CH552 based USB blasters are just junk. I grabbed the Terasic blaster from Mouser and it works perfectly. |
|
The one I have looks like this:
It was very cheap, about £8 and it works. Your mileage may vary of course. |
|
Tried it with Quartus 18.1 on Windows 11 (latest Version). Unfortunately I can't install the drivers without disabling "driver signature" in Windows 11. When I do this and install the driver, Windows 11 crashes the moment I plug the USB Blaster in. |
I'm running Quartus 18.1 on Windows 11 here with a cheap USB Blaster from eBay and it's working fine:
|
|
Seems that there are different versions of this cheap UBS Blaster and some of them are totally useless unless you flash a custom firmware: https://www.downtowndougbrown.com/2024/06/fixing-a-knockoff-altera-usb-blaster-that-never-worked/ |
|
I first ordered a USB Blaster Adapter for 5 EUR. The one with the blue Label saying Rev .C. it doesn't work at all. Bluescreen in Windows, no function under Linux. I tried for hours flashing the doug browns firmware, but i couldn't get a programmer running under linux correctly fashing this thing. I tried Debain 12 and Ubuntu 22.04 LTS and created udev rules. And don't install Virtual Box before trying to flash, because it interferes with the USB devices. If you want to put the ch552 in bootloader mode, better use a 10k resistor than shorting the pins. After all i orderd another adapter "USB Blaster V2" with a golden label from Waveshare for 37 EUR. This got the job done, out of the box, in windows 11 with Quartus 18.1. I got my kit from VGP. Don't expect the preinstalled firmware to be uptodate.
|
Recently I got some requests about problems with upgrading the firmware using an USB-Blaster. Instead of using e-mails I would like to collect the relevant information into this thread. Maybe this could be of some use to other users as well, so please share your experiences here.
To get a common baseline I will describe my current procedure for flashing the firmware.
When the programming does not immediately abort, this means that there is at least a working connection to the USB-Blaster and the FPGA. I could also force an error-abort at 4% by selecting the checkboxes in the "Blank-Check" column.
Use this image as a reference of what I am doing:
The text was updated successfully, but these errors were encountered: