beaglev-fire and updating...?

silver2row · June 11, 2024, 4:26am

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…

lranders · June 11, 2024, 7:52am

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…

silver2row · June 11, 2024, 9:03am

I will try…

RobertCNelson · June 11, 2024, 1:20pm

Let the clock sync

silver2row · June 11, 2024, 11:13pm

@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…

RobertCNelson · June 12, 2024, 1:12am

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,

silver2row · June 23, 2024, 11:01am

Sir,

how do I make the clock up-to-date?

Seth

P.S. Could it be that the PCIe overlay is loaded?

/proc/device-tree/chosen/overlays/
├── name
├── PCIE-M2-GATEWARE
└── ROBOTICS-CAPE-GATEWARE

1 directory, 3 files

lranders · June 23, 2024, 11:12am

It normally happens automatically, once you have some kind of network connection…
(NTP)

silver2row · June 23, 2024, 11:14am

I have a network connection. It is not happening…

I am getting an error in certificate verification error when I use apt update.

Seth

lranders · June 23, 2024, 11:16am

Yes, it’s still related to your clock being off by +128 days.
Certificate verification relies on your clock being right.

You might be able to help it along if you try:
sudo date -s '2024-06-23 12:34:56'

silver2row · June 23, 2024, 11:22am

date --version…

date (GNU coreutils) 9.1

Okay. got it. Thank you, I will try it.

Seth

P.S. I tried the command. It shows now: Could not connect to repos.rcn-ee.com:80. Connection Timed Out. Hmm…I will keep searching for ideas. If you know of another way, please let me know.

lranders · June 23, 2024, 11:24am

What does it say if you do an ip addr?

You can also try and ping something…

silver2row · June 23, 2024, 11:25am

Update

@lranders and @RobertCNelson …

Okay. I had to do what @lranders stated as the command and then get_kernel_update script and then update/upgrade via apt.

Seth

silver2row · June 23, 2024, 11:31am

@lranders ,

Hey there once more or again…

ip a states my IP Address as USB and eth0.

Seth

P.S. I checked the software status of :9090 and updated via ssh instead. Anyway, thank you.

Update (Again)!

Okay…so I ran a command to find failed services…

● motd-news.service loaded failed failed Message of the Day

is this an issue?

lranders · June 23, 2024, 11:33am

Would you mind posting the entire output from ip addr?

silver2row · June 23, 2024, 11:36am

Hello @lranders ,

I would rather not. I am sorry. It is just my IP Address for the board.

Seth

lranders · June 23, 2024, 11:39am

It’s really not dangerous. If you’re dubious, you can mask out the MAC.
( it might show us what’s going on )

silver2row · June 23, 2024, 11:47am

Oh.

I am sorry. It is too late. I need to flash another image. I broke it somehow…

I think the update and upgrade, when it worked and without updating the gateware image via the command sudo apt install bbb.io-gateware, created a bad image and along with the get_kernel_update script.

Blah…

Seth

P.S. Sorry to bother you during my trials.

silver2row · June 23, 2024, 11:52am

@lranders ,

This seems to be an ongoing issue with my board, e.g. I checked past circumstances…

imx219 1-0010: failed to read chip id 219

Seth

P.S. Okay…I will show it off:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:04:a3:10:96:dc brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.57/24 metric 1024 brd 192.168.0.255 scope global dynamic eth0
       valid_lft 172705sec preferred_lft 172705sec
    inet6 fe80::204:a3ff:fe10:96dc/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:04:a3:10:96:db brd ff:ff:ff:ff:ff:ff
    altname end0
4: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd :: permaddr 52a9:aff8:998c::
5: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:04:a3:10:96:df brd ff:ff:ff:ff:ff:ff
    inet 192.168.7.2/24 brd 192.168.7.255 scope global usb0
       valid_lft forever preferred_lft forever
    inet6 fe80::204:a3ff:fe10:96df/64 scope link
       valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:7b:28:58:ab brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

lranders · June 23, 2024, 12:10pm

Alrighty; nothing out of the ordinary there.

You can ignore the imx219 error; it’s because you got no camera connected.