Apache Labs Community Forum

Hi guys.

My FPGA is version 11, so I downloaded version 17 from github. I started the flashwriter, loaded the V17 file and programmed the FPGA with V17. I shut down the G2 and turned off the PS. Restarted the G2 and started the p2app in the terminal and the version is still V11. I repeated the whole thing again but the FPGA is still at version 11! What am I doing wrong? ? ?

Can you send a copy of the messages from the text box on the flashwriter app? It runs through a sequence of erasing, programming and verifying; with a progress bar for each. I've never known the FPGA not to be programmed after a verify when it reports success.

Also can you send the message it displays where it says it is V11 - I'm looking particularly for a message reporting that it is a fallback configuration and it should be reprogrammed.

Hi Laurence.

Here are the screenshots of the Flashwriter and P2app in the LX terminal after programming.

OK, the programming succeeded according to the messages. That looks perfectly normal.

And it has been fully powered off and back on again before you see the FPGA version messages?

Yes, the G2 was switched off overnight. PS off!

Could you humour me by disconnecting every single wire & cable from the radio, then reconnecting them? I want to exclude the Saturn board having been powered through USB or something. I just don't understand, unless somehow the power feed to the FPGA stayed on.

I will remove all cables and wires overnight and report what happened.

The G2 was switched off overnight without all cables and wires. But it still remains at V11! ! !

OK then the only remaining explanation is that the file you are programming with isn't actually the V17 configuration data. I have just reprogrammed my Saturn with the file that is in the github repository, and it reports V17 as expected. So the file in github is OK.

If you have done a "git pull" then the file should be on your G2 drive, in a location something like:
github/Saturn/blob/main/FPGA/saturnprimary2024V17.bin

Please do a git pull again to make sure that file hasn't been damaged; then point flashwriter at that location and try again.

Laurence, I've downloaded and tried again, but unfortunately it hasn't worked.

OK: one more possibility is that the V11 image has somehow been programmed into the fallback location. So although the other image is there, it doesn't get loaded because the code to try "primary" first is missing.

A V11 programmed into the fallback location would still report itself as the primary image, because that information is contained in the image itself.

The way to correct that would be as follows. Be aware that if power is lost during the process, the only way out would be to use a xilinx download cable.

1. download saturnfallback.bin
2. program that image as the **fallback** image.
3. re-program saturnprimary2024V17.bin as the **primary** image

if you powered the radio off and on between steps 2 and 3, it would be helpful to know what version it booted from. The fallback image actually contains 2 images - the fallback one and a primary one. The idea is you replace the primary one, but the fallback stays in place.

Laurence, that sounds good.
Unfortunately, I'm not a computer expert and LINUX is new to me.
Are there any instructions on how to do this?
I don't want to do anything wrong!

Roger GT wrote:Laurence, that sounds good.
Unfortunately, I'm not a computer expert and LINUX is new to me.
Are there any instructions on how to do this?
I don't want to do anything wrong!

Hi Roger,

we can make a phone / Anydesk (portable) meeting. I will never use Teamviewer again!
I am not at home today, will be back late, but have two days off (Mo & Di).
I fixed the problem on Peter's G2 last week.

Hi Norbert.
That sounds good and I thank you for your offer, which I gladly accept.
What time is convenient for you?

Just out of curiosity have you tried to load V12? I had a similar issue back moving from V10 to V12, I mentioned it somewhere else in the firmware update threads. I loaded V12 3-4 times yet P2APP continued to report V10. I loaded V11 and it reported V11, then loaded V12 with success. Maybe a fluke? I have zero Linux or technical abilities but just wanted to chime in on a past experience. I did help a friend update his from v11 to v17 without a hiccup. Best of luck you’ll get it!
73 John K5WC

Hello John,
I have flashed all versions from V12 to V17 but without success.

Hello Roger,
I can hardly comment here as I don't have an Anan G2, just a thought. Perhaps you could install an older version, e.g. V10, and then go from there to V12 or higher.

73 Joerg, DD8JM

Interestingly I've just been exchanging messages with Rick (one of the developers) on a different topic and he has had the same experience. The cause was, he had a primary image installed at the fallback location; and the fix was to re-install the fallback image at the fallback location, then flash the newest image at the primary location.


It only needs the same flashwriter use as you've already done. But use twice - flash the fallback with "boot image" set to fallback
Then flash V17 with boot image set to primary.

laurencebarker wrote:Interestingly I've just been exchanging messages with Rick (one of the developers) on a different topic and he has had the same experience. The cause was, he had a primary image installed at the fallback location; and the fix was to re-install the fallback image at the fallback location, then flash the newest image at the primary location.

It only needs the same flashwriter use as you've already done. But use twice - flash the fallback with "boot image" set to fallback
Then flash V17 with boot image set to primary.

This was the solution even in this case

My G2 is now up to date thanks to the kind support of Norbert DL8LAQ. Thanks also to Larence.

Best regards

Roger