If you want, you can re-enable this in the earlier U-Boot by deleting the following portion of the setup_distroboot_efi variable:
fdt set "/soc/spi@20c0000" "status" "disabled"
I am concerned about the firmware configuration.
fw_printenv bootcmd
Cannot open /dev/mtd3: No such file or directory
If I understand correctly, two issues with these devices are linked, thus, I can only do modifications from U-boot with a serial converter in the new (non-testing) firmware?
(be careful attempting this remotely, the boot process will get stuck if not edited correctly)
What is the process here? I’d like to avoid bricking the device due to a small typo. I presume I go into the boot sequence and have some access to the configuration there, backup original config, remove the line, save it and hope for the best?
For now, I’ll look into the testing branch. Is there any documentation on switching the MTD configuration to test different SFP types for the testing firmware?
Older versions of some distributions contained a flash driver which was not able to access the NAND chip, and could corrupt it if used incorrectly
I’m curious to know more and wonder if this is documented anywhere.