This is the EFI shell, it's what is left as the default boot option when all other options aren't available. Looking at the drives it seems that FS0 should work (EMMC AFAICT). If DiagOS didn't get a efibootmanager entry (it should have) you can generally do it manually:@oneplane I have both the 610 and 640. How did you manage to flash the dell diagnostics. I've tried on the 640 but now i just get the following screen and I think something went wrong.
View attachment 28559
i've desoldered the flashs and attached directly some cables to the pins, here is the schematics of the flash@mirochulovesnetwork which header/s did you use on the 610 to dump the images? I have a working 610 that is unmodified and I will be able to pull the CPLD and PIC images once i have a CH341A. A pinot would be very useful.
It looks like I had a issue and it didn't install the diagnostics. I've reflashed the usb drive with rufus in dd mode and turned off compatability mode in the bios and it then installed and I managed to update the bios, CPLD and PIC.This is the EFI shell, it's what is left as the default boot option when all other options aren't available. Looking at the drives it seems that FS0 should work (EMMC AFAICT). If DiagOS didn't get a efibootmanager entry (it should have) you can generally do it manually:
fs0:/
dir
(look for EFI or BOOT)
cd efi (or boot)
dir (yes again)
There should be a grub.efi, boot.efi, grubx64.efi or something like it, which you can launch (grubx64.efi [ENTER]) and that should then start the normal boot process.
The EFI boot manager entry can be fixed from within DiagOS, but let's make sure you at least get to there you need to go.
The 620 is a vep1400x. I used the ./vep1400x_ufw_2.2 command and it upgraded everything automatically.Thank you for the heads up. One question is the 620 a vep1400x or just a vep1400 model also did you have to update the clpd and pic too or did you only update the bios?
Sorry to hear that. Didn't think about removing the link.Hey guys, first time user here,
I was trying to flash the bios and the clpd using one linked by ralph (dumb me that didn't see the x in vep1400) but it ""bricked"" my 610 (still boots and accesses bios but network doesn't work, one light is permanently on)
Does anyone have a firmware updater that works with the 610, i can't find it anywhere.
Thanks
If I understand it correctly the I2Cwrite as its not persistant during upgrades of PFsense like the bios upgrade on the edge 640 and I will be deploying at a remote location. Therefore its of concirn and it needs to be a robust solution.The easiest way to disable the watchdog from the OS is using i2cwrite. This is also what is used in the DiagOS RC scripts.
Yes, the watchdog is controlled by a UEFI variable as well, I haven't looked for it yet, but UEFITool would be able to help you find it. It does require a firmware backup image or firmware upgrade image. DiagOS and the UFW package can get a UEFI image. Reading the SPI chip directly also works.If I understand it correctly the I2Cwrite as its not persistant during upgrades of PFsense like the bios upgrade on the edge 640 and I will be deploying at a remote location. Therefore its of concirn and it needs to be a robust solution.
I did however notice that if you boot the 610 into the UEFI shell that the watchdog is not kicking in as I was in it for over an hour with no restarts... It also looks like you can have a look through the bios using the SMBIOSVIEW command.
This might be a noob question but is it possible to deactivate the watchdog by booting into the UEFI shell and modifying the bios that way... similar to how some people reactivate under voltage function again on a locked down laptop bios?
Also are you able to update the bios from the UEFI shell on a EDGE 610?
I will have to wait for the CH341A to arrive and make a bios dump on the Edge 610... as I could not find the bios anywhere for the Edge 610 at all.Yes, the watchdog is controlled by a UEFI variable as well, I haven't looked for it yet, but UEFITool would be able to help you find it. It does require a firmware backup image or firmware upgrade image. DiagOS and the UFW package can get a UEFI image. Reading the SPI chip directly also works.
As for i2cwrite during upgrades: the write command only needs to be done once in the first 5 minutes of a boot, so as long as it is added directly after mounting the disk (so an early boot command) it will always be on time.
* The UEFI standard requires that the watchdog timer is set to five
* minutes when invoking an EFI boot option.
*
Please remember to post the dump here :- )I've tried the extracting the watchdog information using the IFRextractor but it doesn't find any information on the bios dumps from mirochulovesnetwork uploaded from his bricked edge 610. I am waiting for my CH341A to arrive and I will pull the unedited bios off my 610 and retry as the grub bootloader on the edge 610 is password protected so I cant even dig into that to see if they disable the watchdog in there