After having the auto-provisioning up and running I still have a small imperfection in play.
Whenever mtd -r write <IMAGE-NAME>.bin firmware finishes it does not do the -r because it complains about not being able to [e]rase a block. ...it exits with 1
Writing from 20211027-pan35-blusser-9-5.bin to firmware ...
[e]Failed to erase block
mtd verify doesn't end well either.
After a reboot the omega seems to be running my custom firmware happily, so I dont worry too much yet, but it keeps nagging
I have followed the instructions closely, also tried a couple of times more to make a new .bin file using the dd method.
This is how that runs:
root@Pandora3-74F3:/mnt/mmcblk0# dd if=/dev/mtd3 of=20211108-pan35-blusser-9-5.bin
64896+0 records in
64896+0 records out
Any idea where i should look?
I need to deploy my custom firmware build to my Omega2S+ based devices, but since a new board will not have a wireless connection I need to use the ethernet connection also built into my board. So there is no reliance upon ipv4 address, this script finds the connected ipv6 device, uses scp to transfer the firmware to the device, then executes sysupgrade on the device.
Have you tried downloading the latest firmware to /tmp/ on the Omega and doing a sysupgrade /tmp/<firmware-image> manually?
If your Omega has network, you can pull the firmware from an ssh shell and perform the upgrade.
If your Omega doesn't have upstream connectivity, you can scp (or pscp on windows) the firwmare image downloaded to your workstation/laptop over to the Omega to perform a manual upgrade.