CerboGx version 3.70 installs, restarts but still in the old version 3.66. If I choose to reboot it in 3.70 CerboGx still starts in 3.66.
Hi @GeorgeD,
That’s a strange issue.
Could you try one of the alternative methods of updating firmware?
Are you able to see what free disk space there is and are any third party mods or drivers loaded?
1 Like
@GeorgeD I can try to update / have a look if you want.
986 Mb free space
@Ewky That is a different problem.
Is there a log where I could find the error?
I found this, does it mean anything?
root@einstein:~# cat /data/log/dmesg.old | grep -iE ‘err|fail|crit’
[ 0.127983] /soc/interrupt-controller@1c81000: Fixed dependency cycle(s) with /soc/interrupt-controller@1c81000
[ 0.200751] armv7-pmu pmu: hw perfevents: no interrupt-affinity property, guessing.
[ 6.838096] sun4i-emac 1c0b000.ethernet (unnamed net_device) (uninitialized): failed to request dma channel. dma is disabled
[ 6.849427] sun4i-emac 1c0b000.ethernet (unnamed net_device) (uninitialized): configure dma failed. disable dma.
[ 7.379263] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.victronenergy,cerbo-gx.bin failed with error -2
[ 7.771158] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 12.889124] Bluetooth: hci1: BCM: failed to write update baudrate (-110)
[ 14.969097] Bluetooth: hci1: BCM: Reset failed (-110)
root@einstein:~#
No, if we want to figure out what is going on, you need a UART TTL cable to connect to the debug connector, which is inside the device. It is the boot loader doing this, the update goes fine, marked as the one to boot, but the boot loader refuses to do it. But the boot loader runs before linux, there is no log of it.
if you want to try to fix it yourself, see Venus OS reinstall, but mind the warnings. That will reinstall everything, including boot loader etc and all settings will be gone.
no, this is the part that matters
root@einstein:~# fw_printenv | sort
…
setroot=if test “${version}” = 1; then setenv bootpart 1:2; setenv mmcroot /dev/mmcblk1p2; else setenv bootpart 1:3; setenv mmcroot /dev/mmcblk1p3; fi
version=1
…
root@einstein:~# mount
/dev/mmcblk1p3 on / type ext4 (rw,relatime,mb_optimize_scan=0)
The boot loader is instructed to boot /dev/mmcblk1p2, but it boots /dev/mmcblk1p3
There is a small problem with the fresh install, everything needs to be reconfigured. Is there a way to save the current configuration and then apply it after the fresh install? Can I wait, I don’t have to install 3.70 right away, maybe you can find the problem. I saw on the community that there is also 3.67, it is a problem jumping from 3.66 to 3.70, there are some intermediate changes that need to be done in stages
Sure it can wait, actually preferably, since if possible I would like to understand what is going on, but it is something exceptional.
No, the v3.67 update will have the same problem.
Ok, thank you, I’ll be here!
I will order a VE.Direct - USB cable. Is the one in the attached link good? What can I connect with, is putty ok? Is there a tutorial for this? Victron Energy Cablu de interfață VE.Direct la USB
Hi @GeorgeD
I’m pretty sure he’s talking about this: Venus OS: Root Access [Victron Energy]
1 Like