beaglev-fire and updating...?

Hello,

I can connect to the BeagleV-Fire but I cannot update/upgrade the board so far. Gateware can be updated via the command with sudo only and without the . pre-period for the command:

cd /usr/share/beagleboard/gateware
. ./change-gateware.sh default

So, the command that worked for me is this one:

cd /usr/share/beagleboard/gateware
sudo  ./change-gateware.sh default

Anyway, what can I do if anything to get back to working order. I have tried with the online program but it is giving me these ideas:

Hit:2 http://ports.ubuntu.com lunar InRelease 
Hit:4 http://ports.ubuntu.com lunar-security InRelease
Hit:5 http://ports.ubuntu.com lunar-updates InRelease                   
Ign:1 https://repos.rcn-ee.com/debian-riscv64 lunar InRelease           
Ign:3 https://debian.beagleboard.org/riscv64 lunar InRelease
Ign:1 https://repos.rcn-ee.com/debian-riscv64 lunar InRelease
Ign:3 https://debian.beagleboard.org/riscv64 lunar InRelease
Ign:1 https://repos.rcn-ee.com/debian-riscv64 lunar InRelease
Ign:3 https://debian.beagleboard.org/riscv64 lunar InRelease
Err:1 https://repos.rcn-ee.com/debian-riscv64 lunar InRelease
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate.  Could not handshake: Error in the certificate verification.
Err:3 https://debian.beagleboard.org/riscv64 lunar InRelease
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate.  Could not handshake: Error in the certificate verification.
Reading package lists... Done                            
E: Release file for http://ports.ubuntu.com/dists/lunar-security/InRelease is not valid yet (invalid for another 127d 20h 13min 19s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/dists/lunar-updates/InRelease is not valid yet (invalid for another 127d 22h 40min 26s). Updates for this repository will not be applied.

Please send guidance…

Have you tried any of the suggestions you get if you Google “apt The certificate is NOT trusted”?

Alternate gateware can be uploaded to the Beagle manually; all is not lost…

I am not certain that an image reload via the procedure here is enough to also reprogram the FPGA part.
( scroll down to the eMMC part )

I’m sure @RobertCNelson has some insight here… :smiling_face:

1 Like

I will try…

Let the clock sync

1 Like

@RobertCNelson ,

How would I allow the clock to sync? With rsync or some way I am not familiar with currently?

Seth

Update…

Okay. I think the 128 Days to sync is excessive but I can wait if need be…

By default, time is kept in sync by systemd-timesyncd, the normal answer is to just plug in ethernet and as long as you have it working network it’ll sync right up…

That’s stating your clock is 128+ days out of date…

Regards,