boot.scr file solutions

Problem #1 - your printer simply can't find the right boot file as illustrated by those TIMEOUT messages above

Above message implies it can't find the boot.scr file and you need to either remount the recovery image and create such a file or tell UBOOT to look for mmc_boot.scr instead.  To do the later:

Solution #1 option A (needs serial cable):
 I think you either hit ctrl+c and/or hit enter a few times and it should give you a new prompt each time you hit enter.  You can type  "help" or "?" for all the U-BOOT commands but here's what you need to do to get it to boot your uSD.  Okay I lost my notes.  You need to use I think printenv to see the variables and setenv to change one of them.  So maybe google "olimex u-boot commands" or something but first try printenv and among what it shows you should be:
boot_scripts=boot.scr.uimg boot.scr
You need to add mmc_boot.scr so something like:
=> setenv boot_scripts boot.scr.uimg boot.scr mmc_boot.scr
=> boot
Then type boot as shown.  Before you do that type printenv to make sure I showed you the setenv command properly.  I remember it wasn't too hard to figure out.  Maybe if you type "setenv ?" or "? setenv" it will tell you what to do.  Or maybe I used google.


Solution #1 option B (doesn't need serial cable):

Alternatively you can edit the img.  I have an edited image ready for you to use right now but only 5.7.2 or 6.4.0 and they ONLY work for R1 of the S5 (S5 with robot on side panels R2 has "U" on side panels).
http://gr5.org/gr-S5-R1.img                               (this is version 5.7.2 - for S5 R1 printers only)
http://gr5.org/um-restore-6.4.0-R1-gr.img        (this is version 6.4.0 -  for S5 R1 printers only)
http://gr5.org/um-restore-7.1.3-S5R1.img        (this is version 7.1.3 -  for S5 R1 printers only)

Other image files:
https://software.ultimaker.com/releases/firmware/9066/stable/5.3.0.20211003/um-restore-5.3.0.20211003.img   (UM3 only)


How to edit an img file from within linux - george notes - I have ubuntu:

# sudo -s  <-- I think you need to be root to do the following steps
# losetup -Pf gr.img  <-- I previously renamed Ultimakers img file to "gr" to save typing
# losetup | grep gr.img
/dev/loop35         0      0         0  0 /media/geo/ExtraDrive1/ultimaker/gr.img               0     512

fdisk -lu /dev/loop35      <-- "loop35" comes from the grep/search above -- odds are 99% it will be a different number
mkdir mm                     <-- you have to create an empty folder before you can mount something
mount /dev/loop35p1 mm/

Use df to see if available space
make edits:
cp mmc_boot.scr to boot.scr

cd ..
umount mm

remove loop mount:
kpartx -d -v gr.img