Ultimaker 3 suddenly no display and unresponsive button

[gr5 2,179]

There's a lot of info on my page about UBOOT because I spent many days getting past that step.  The good news is that you guys don't have any UBOOT issues so skip all that.  There's also tons of info about UBOOT on olimex out there on the internet, lol.  Olimex goes way beyond just Ultimaker printers.

[jordyR 2]

16 minutes ago, gr5 said:

There's a lot of info on my page about UBOOT because I spent many days getting past that step.  The good news is that you guys don't have any UBOOT issues so skip all that.  There's also tons of info about UBOOT on olimex out there on the internet, lol.  Olimex goes way beyond just Ultimaker printers.

Let's go slow 😉 it's Alot information to take in i'm smart with pc's not with code programming. So i buy a olimex serial cable, i plug in in my pc and the i van flash the UM recovery firmware do the board? Just like the SD but with a screen and more feedback of what is happening on the board

[gr5 2,179]

Everytime you boot your olimex it spews out tons of information.  It tells you what OS is booting, what drivers are being installed, what services are starting up.  Also eventually the UM software starts running as well including the recovery programs and it spews out stuff as well to the console.  Every.  Time.  You.  Boot.

 

Until now that information just goes to those 3 pins and is never observed.

 

So you leave the SD card in the olimex and power up and look at all that info you have been missing all this time.  That's the first step.  Read it all - look for error messages - try to see where things go badly (usually near the end).  Post the result and let me look at it.

[gr5 2,179]

As I explain on the website you will need to connect the other end of the serial cable to a computer such as PC, Mac, Linux and you will need software on that computer to see the output coming from the Olimex board. 

[jordyR 2]

2 hours ago, gr5 said:

As I explain on the website you will need to connect the other end of the serial cable to a computer such as PC, Mac, Linux and you will need software on that computer to see the output coming from the Olimex board. 

Ok i order the cable, what software do i need? on my windows pc.

 

also i did a thing -_- when i put a screen into the olimex hdmi port and i turn on the printer without the SD in the board, i get the linux logo and this text. looks like nothing is happening 😕

second time i put the SDcard in the olimex and then start de printer up i got this scrambeld lines on my screen.

 

not sure what to think of this, just maybe wayting after i got the cable.

[jordyR 2]

also is this cable of amazon OK?

or this cable?

[gr5 2,179]

It's a 3 pin cable.  Not sure what the 4 pin cable does.  I'd just get the official one if it won't take too long.  There are many other cables that work.  They are all called "usb to serial cable" or something like that but some are 5V and some are 3.3V and I'm not sure which you need or if it even matters or if it can damage the olimex or what.

 

Google can help with that of course: "which serial cables are compatible with olimex lime2?"

 

As for software - PLEASE READ MY WEBSITE - lol!

[gr5 2,179]

Okay I don't mention the software.  I think I used putty?  Or actually I think I used my linux machine.  What operating system do you have?  You need different software for each machine.  Hyperterminal should work if you already have that.  Putty I think will work.  There are probably over 300 programs on the PC that are good terminal programs through a "COM" port (assuming you have a PC.  I'd just google it.  I *do* talk about proper baud rate.  Olimex website also talks about baud rate and how to hook up cables (seemingly backwards as TX connects to RX!).

 

[jordyR 2]

On 7/14/2023 at 3:34 AM, gr5 said:

Okay I don't mention the software.  I think I used putty?  Or actually I think I used my linux machine.  What operating system do you have?  You need different software for each machine.  Hyperterminal should work if you already have that.  Putty I think will work.  There are probably over 300 programs on the PC that are good terminal programs through a "COM" port (assuming you have a PC.  I'd just google it.  I *do* talk about proper baud rate.  Olimex website also talks about baud rate and how to hook up cables (seemingly backwards as TX connects to RX!).

 

i got the olimx able, so is the red wire TX and green RX of the other way around?
i got windows 10 64bit, what program do i use forreading the olimex board with the cable?

[jordyR 2]

On 7/13/2023 at 2:32 PM, SCA_B said:

I figured out the same thing -I also think it's hidden behind the LAN port



I ordered a serial to USB cable today and hope I can save some 300 Euros that way.
What software do you use for the serial connection - Arduino?

thanks for your page and the time you invested in solving this particular problem 

hi, did you got any luck to fix your UM3 again? i just got my serial cable

[SCA_B 10]

I managed to connect the serial cable correctly:


Install driver:
https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-SERIAL-F/
(->software: https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/_resources/win_x86_x64_drivers_usb_cable.zip)

install putty:
https://www.putty.org/

open window in putty:

maybe change COM3 to COM1->device manager tells you where the serial USB cable is connected

now you should have a black serial window and you can power up your ultimaker

 

[SCA_B 10]

My read out got the sad robot- time to format the drive:
 

##################################################
#                   ▄▄▄      ▄▄▄                 #
#                   ███████▄▄███▄                #
#                 ▄███  ▄▄   ▄▄ ▐█               #
#              ▄██  ██ ▀▀▀   ▀▀▀▐█▄              #
#              ███▄▄██  ▄▄▄▄▄▄▄ ▐██              #
#               ██████ ▀       ▀ ▐█              #
#            ▄████▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█▄           #
#          ████▐█ ▐████████████████▌▐██▄         #
#        ▐███▌▄▄█ ▐████████████████▌▐█▄█         #
#         ███████ ███████▀▀ ▀██████▌▐██▌         #
#         ███████ █████████ ██▐████▌▐██▌         #
#        ▄███████ ██████▄██████████▌▐█▀█         #
#        ████  ▐█ ▐████████████████▌▐█ █▌        #
#        ▀███ ███   ▀▀▀▀            ▐██▀         #
#           ▀▀████▄▄████████████████▀            #
#             ▐████████▀▀████▀▀▌  █▌             #
#            ▄██████  █  ▐███▄▄█▄▄██             #
#            ████████▀▀▀█▀████▀    ██            #
#            █████████    ▐███     ██            #
#              ▀███▄█▄▄▄▄▄███▀▀▀▀▀▀▀             #
#                                                #
# Starting busybox rescue and recovery shell.    #
# Tip: type help<enter> for available commands.  #
#                                                #
##################################################

 

[SCA_B 10]

On 7/13/2023 at 9:55 PM, gr5 said:

As I explain on the website you will need to connect the other end of the serial cable to a computer such as PC, Mac, Linux and you will need software on that computer to see the output coming from the Olimex board. 

I forgot my cardreader and will continue on wednesday- 
anyone knows if keyboard works via putty? it does nothing when I connect it.
GR5 - did your keyboard show input when connected or did you connect your keyboard on the board directly?

 

[gr5 2,179]

In putty there should be a window that is spewing out information.  Well before it spits out the sad robot is valuable information.

 

In putty, once it stops booting, you should be able hit the return key on your keyboard and it should prompt for a username (use root) and/or password (use "ultimaker" typically - also try "root" "password" or lookup on the olimex website what the recovery password is typically but ultimaker setup the root password somehow.

 

So you can log into debian linux and there are thousands of commands you can do to look around.  But more importantly save *all* of the boot process.

 

There should be a way in putty to log all output into a file.  If I remember right.  I haven't used putty in about 5 years.  I used to use it every day.

 

[gr5 2,179]

How to output everything in putty to a file: https://www.dell.com/support/kbdoc/en-us/000116043/dell-emc-networking-how-to-use-putty-exe-to-save-output-to-a-file

[gr5 2,179]

By the way, you are doing fantastic - you got the serial cable working!  Congratulations!  This is a big step.

[gr5 2,179]

28 minutes ago, SCA_B said:

GR5 - did your keyboard show input when connected or did you connect your keyboard on the board directly?

I entered text through putty.  Start with enter key.  If that does nothing then recheck the cabling.

 

If you plug in a USB cable I think it goes to a different console than the one through putty.  You would need to get the hdmi cable outputing info before plugging in a usb keyboard.  I think.  More information on the olimex  forums.

[jordyR 2]

HI, i did the same with serial cable.

 

this is the readout:

 

U-Boot SPL 2016.05-ultimaker-00017-g68b3b1c (Apr 09 2018 - 14:28:14)
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
DRAM: 1024 MiB
Trying to boot from MMC1

U-Boot 2016.05-ultimaker-00017-g68b3b1c (Apr 09 2018 - 14:28:14 +0200) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0 (SD), SUNXI SD/MMC: 1
In:    serial
Out:   serial
Err:   serial
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
Press CTRL-c to interrupt Ultimaker boot up.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
9219 bytes read in 241 ms (37.1 KiB/s)
## Executing script at 43100000
gpio: pin PI13 (gpio 269) value is 0
gpio: pin PI13 (gpio 269) value is 1
Setting bus to 2
Setting bus to 1
Article number: 236a-ffffffff
3880696 bytes read in 265 ms (14 MiB/s)
** File not found 236a-ffffffff.dtb **
31141 bytes read in 132 ms (229.5 KiB/s)
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux-4.14.32-ultimaker
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3880632 Bytes = 3.7 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 43000000, end 4300a9a4

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.32-ultimaker (root@runner-v8xsaqay-project-11447330-concurrent-0) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #3 SMP Thu Aug 19 07:54:44 UTC 2021
[    0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Olimex A20-OLinuXino-LIME2-eMMC
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 64 MiB at 0x7c000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: Using PSCI v0.1 Function IDs from DT
[    0.000000] random: fast init done
[    0.000000] percpu: Embedded 16 pages/cpu @eb69d000 s34956 r8192 d22388 u65536
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 259840
[    0.000000] Kernel command line: um_an=236a console=tty0 fbcon=map:63 root=/dev/mmcblk0p2 ro rootwait rootdelay=2 rootfstype=ext4 console=ttyS0,115200 earlyprintk
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 962620K/1048576K available (5120K kernel code, 473K rwdata, 1604K rodata, 2048K init, 259K bss, 20420K reserved, 65536K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xb0000000 - 0xf0000000   (1024 MB)
[    0.000000]     pkmap   : 0xafe00000 - 0xb0000000   (   2 MB)
[    0.000000]     modules : 0xaf000000 - 0xafe00000   (  14 MB)
[    0.000000]       .text : 0xb0008000 - 0xb0600000   (6112 kB)
[    0.000000]       .init : 0xb0800000 - 0xb0a00000   (2048 kB)
[    0.000000]       .data : 0xb0a00000 - 0xb0a76720   ( 474 kB)
[    0.000000]        .bss : 0xb0a7d34c - 0xb0abe1d4   ( 260 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000007] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.008088] Switching to timer-based delay loop, resolution 41ns
[    0.014610] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.024124] clocksource: hstymp_bits=14 max_order=18 bucket_order=4
[    0.912756] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.922635] Key type asymmetric registered
[    0.926957] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    0.934503] io scheduler noop registered
[    0.938825] io scheduler cfq registered (default)
[    0.944276] sun4i-usb-phy 1c13400.phy: could not find pctldev for node /soc@1c00000/pinctrl@1c20800/usb0_id_detect_pin@0, deferring probe
[    0.960506] sun4i-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[    1.025836] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    1.035180] console [ttyS0] disabled
▒[    1.059091] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 48, base_baud = 1500000) is a U6_16550A
[    1.068217] console [ttyS0] enabled
[    1.068217] console [ttyS0] enabled
[    1.075274] bootconsole [earlycon0] disabled
[    1.075274] bootconsole [earlycon0] disabled
[    1.105214] 1c28c00.serial: ttyS1 at MMIO 0x1c28c00 (irq = 49, base_baud = 1500000) is a U6_16550A
[    1.122140] loop: module loaded
[    1.126403] libphy: Fixed MDIO Bus: probed
[    1.131342] sun7i-dwmac 1c50000.ethernet: PTP uses main clock
[    1.137113] sun7i-dwmac 1c50000.ethernet: no reset control found
[    1.143265] sun7i-dwmac 1c50000.ethernet: no regulator found
[    1.149014] sun7i-dwmac 1c50000.ethernet: Ring mode enabled
[    1.154594] sun7i-dwmac 1c50000.ethernet: DMA HW capability register supported
[    1.161856] sun7i-dwmac 1c50000.ethernet: Normal descriptors
[    1.175838] libphy: stmmac: probed
[    1.179302] mdio_bus stmmac-0:00: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    1.188798] mdio_bus stmmac-0:01: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[    1.199344] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.205918] ehci-platform: EHCI generic platform driver
[    1.211671] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.217945] ohci-platform: OHCI generic platform driver
[    1.223639] usbcore: registered new interface driver usb-storage
[    1.230805] sunxi-rtc 1c20d00.rtc: rtc core: registered rtc-sunxi as rtc0
[    1.237615] sunxi-rtc 1c20d00.rtc: RTC enabled
[    1.242261] i2c /dev entries driver
[    1.246839] axp20x-i2c 0-0034: AXP20x variant AXP209 found
[    1.260125] ldo1: supplied by regulator-dummy
[    1.264781] ldo2: supplied by regulator-dummy
[    1.270383] ldo3: supplied by regulator-dummy
[    1.276134] ldo4: supplied by regulator-dummy
[    1.280589] vdd-io-pg: Bringing 3000000uV into 3300000-3300000uV
[    1.287137] ldo5: supplied by regulator-dummy
[    1.292590] dcdc2: supplied by regulator-dummy
[    1.297804] dcdc3: supplied by regulator-dummy
[    1.303730] axp20x-i2c 0-0034: AXP20X driver loaded
[    1.312575] sdhci: Secure Digital Host Controller Interface driver
[    1.318868] sdhci: Copyright(c) Pierre Ossman
[    1.324535] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[    1.388014] sunxi-mmc 1c0f000.mmc: base:0xf0947000 irq:30
[    1.398001] sunxi-mmc 1c11000.mmc: allocated mmc-pwrseq
[    1.445027] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.455323] mmc0: new high speed SDHC card at address 0002
[    1.460886] sunxi-mmc 1c11000.mmc: base:0xf0949000 irq:31
[    1.461459] mmcblk0: mmc0:0002 00000 7.32 GiB
[    1.462878]  mmcblk0: p1 p2
[    1.474275] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.484409] ledtrig-cpu: registered to indicate activity on CPUs
[    1.491513] Registering SWP/SWPB emulation handler
[    1.497065] registered taskstats version 1
[    1.501226] Loading compiled-in X.509 certificates
[    1.507128] Key type encrypted registered
[    1.521197] ehci-platform 1c14000.usb: EHCI Host Controller
[    1.526833] ehci-platform 1c14000.usb: new USB bus registered, assigned bus number 1
[    1.535293] ehci-platform 1c14000.usb: irq 33, io mem 0x01c14000
[    1.567717] ehci-platform 1c14000.usb: USB 2.0 started, EHCI 1.00
[    1.574105] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.580936] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.588177] usb usb1: Product: EHCI Host Controller
[    1.593058] usb usb1: Manufacturer: Linux 4.14.32-ultimaker ehci_hcd
[    1.599434] usb usb1: SerialNumber: 1c14000.usb
[    1.604717] hub 1-0:1.0: USB hub found
[    1.608612] hub 1-0:1.0: 1 port detected
[    1.613527] ehci-platform 1c1c000.usb: EHCI Host Controller
[    1.619263] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[    1.627363] ehci-platform 1c1c000.usb: irq 38, io mem 0x01c1c000
[    1.638735] mmc1: new DDR MMC card at address 0001
[    1.644185] mmcblk1: mmc1:0001 P1XXXX 3.60 GiB
[    1.649038] mmcblk1boot0: mmc1:0001 P1XXXX partition 1 16.0 MiB
[    1.655215] mmcblk1boot1: mmc1:0001 P1XXXX partition 2 16.0 MiB
[    1.661243] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[    1.668353] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    1.675167] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.682451] usb usb2: Product: EHCI Host Controller
[    1.687334] usb usb2: Manufacturer: Linux 4.14.32-ultimaker ehci_hcd
[    1.693707] usb usb2: SerialNumber: 1c1c000.usb
[    1.698325]  mmcblk1: p1 p2 p3
[    1.703584] hub 2-0:1.0: USB hub found
[    1.707416] hub 2-0:1.0: 1 port detected
[    1.712321] ohci-platform 1c14400.usb: Generic Platform OHCI controller
[    1.719082] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3
[    1.727287] ohci-platform 1c14400.usb: irq 34, io mem 0x01c14400
[    1.801894] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    1.808726] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.815952] usb usb3: Product: Generic Platform OHCI controller
[    1.821891] usb usb3: Manufacturer: Linux 4.14.32-ultimaker ohci_hcd
[    1.828259] usb usb3: SerialNumber: 1c14400.usb
[    1.833777] hub 3-0:1.0: USB hub found
[    1.837590] hub 3-0:1.0: 1 port detected
[    1.842422] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[    1.849154] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4
[    1.857219] ohci-platform 1c1c400.usb: irq 39, io mem 0x01c1c400
[    1.931904] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    1.938731] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.945956] usb usb4: Product: Generic Platform OHCI controller
[    1.951897] usb usb4: Manufacturer: Linux 4.14.32-ultimaker ohci_hcd
[    1.958265] usb usb4: SerialNumber: 1c1c400.usb
[    1.963507] hub 4-0:1.0: USB hub found
[    1.967328] hub 4-0:1.0: 1 port detected
[    1.972208] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[    1.983518] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    1.989336] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
[    1.997417] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.004245] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.011492] usb usb5: Product: MUSB HDRC host driver
[    2.016460] usb usb5: Manufacturer: Linux 4.14.32-ultimaker musb-hcd
[    2.022828] usb usb5: SerialNumber: musb-hdrc.1.auto
[    2.028449] hub 5-0:1.0: USB hub found
[    2.032268] hub 5-0:1.0: 1 port detected
[    2.036868] sunxi-rtc 1c20d00.rtc: setting system clock to 1970-01-01 00:00:08 UTC (8)
[    2.045308] vcc3v0: disabling
[    2.048349] vcc5v0: disabling
[    2.051341] ahci-5v: disabling
[    2.057260] Freeing unused kernel memory: 2048K
Checking command availability.
[ is a shell builtin
break is a special shell builtin
continue is a special shell builtin
echo is a shell builtin
exec is a special shell builtin
findfs is /sbin/findfs
mktemp is /bin/mktemp
modprobe is /sbin/modprobe
mount is /bin/mount
mv is /bin/mv
poweroff is /sbin/poweroff
readlink is /usr/bin/readlink
reboot is /sbin/reboot
shutdown is a function
sleep is /bin/sleep
switch_root is /sbin/switch_root
umount is /bin/umount
watchdog is /sbin/watchdog
Enable frame-buffer driver.
[    4.260377] sun4i-drm display-engine: bound 1e60000.display-backend (ops sun4i_backend_ops [sun4i_backend])
[    4.270581] sun4i-drm display-engine: bound 1e40000.display-backend (ops sun4i_backend_ops [sun4i_backend])
[    4.280902] sun4i-drm display-engine: No panel or bridge found... RGB output disabled
[    4.288795] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops sun4i_tcon_ops [sun4i_tcon])
[    4.298409] sun4i-drm display-engine: No panel or bridge found... RGB output disabled
[    4.306272] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops sun4i_tcon_ops [sun4i_tcon])
[    4.427702] rc_core: IR keymap rc-cec not found
[    4.432266] Registered IR keymap rc-empty
[    4.436443] rc rc0: RC for sun4i as /devices/platform/soc@1c00000/1c16000.hdmi/rc/rc0
[    4.444492] input: RC for sun4i as /devices/platform/soc@1c00000/1c16000.hdmi/rc/rc0/input0
[    4.453165] sun4i-drm display-engine: bound 1c16000.hdmi (ops sun4i_hdmi_ops [sun4i_drm_hdmi])
[    4.461842] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.468478] [drm] No driver support for vblank timestamp query.
[    4.974457] [drm] Cannot find any crtc or sizes
[    4.979564] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
[    4.996846] ssd1307fb 3-003c: fb0: Solomon SSD1307 framebuffer device registered, using 1024 bytes of video memory
cat: write error: Invalid argument
/dev/mmcblk0p2
Checking for updates ...
Attempting to mount '/dev/mmcblk0p1'.
[    5.142998] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x2000)
[    5.152083] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 1th superblock
[    5.160292] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x2005)
[    5.167829] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 2th superblock
[    5.175518] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x2000)
[    5.183045] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 1th superblock
[    5.190722] F2FS-fs (mmcblk0p1): Magic Mismatch, valid(0xf2f52010) - read(0x2005)
[    5.198219] F2FS-fs (mmcblk0p1): Can't find valid F2FS filesystem in 2th superblock
[    5.229872] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
No update image 'um-update.swu' found on '/dev/mmcblk0p1', tryin[    5.302786] F2FS-fs (mmcblk0p2): Magic Mismatch, valid(0xf2f52010) - read(0x5d60)
g next.
Attempting to mount '/dev/mmcblk0p2'.
[    5.312506] F2FS-fs (mmcblk0p2): Can't find valid F2FS filesystem in 1th superblock
[    5.329840] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Found 'um-update.swu' on '/dev/mmcblk0p2', moving to tmpfs.
[    7.037940] [drm] Cannot find any crtc or sizes
Attempting to unmount '/mnt/update' before performing the update.
Attempting to mount '/tmp/tmp.VDQuL5/um-update.swu' to '/mnt/update_img'.
[    9.438907] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[    9.446421] squashfs: SQUASHFS error: unable to read xattr id index table
Successfully mounted 'um-update.swu', looking for '/mnt/update_img//usr//sbin/start_update.sh' script.
Copying '/mnt/update_img//usr//sbin/start_update.sh' from the update image.
Copied update script from image, cleaning up.
/dev/mmcblk0p2
Got 'start_update.sh' script, trying to execute.
Warning: Unexpected 4th argument, ignoring for now
Checking command availability.
[ is a shell builtin
echo is a shell builtin
exit is a special shell builtin
mktemp is /bin/mktemp
mount is /bin/mount
mountpoint is /bin/mountpoint
rmdir is /bin/rmdir
shift is a special shell builtin
umount is /bin/umount
Preparing toolbox ...
[    9.738792] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[    9.746304] squashfs: SQUASHFS error: unable to read xattr id index table
Successfully mounted '/usr/share/jedi-system-update/um-update_toolbox.xz.img' on '/tmp/um-toolbox.XXj9QiXF'.
Running toolbox update ...
Checking command availability.
[ is a shell builtin
chroot is /usr/sbin/chroot
echo is a shell builtin
eval is a special shell builtin
exit is a special shell builtin
mount is /bin/mount
mountpoint is /bin/mountpoint
shift is a special shell builtin
tr is /usr/bin/tr
umount is /bin/umount
Preparing update...
Mounting firmware update file.
[   10.118891] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[   10.126404] squashfs: SQUASHFS error: unable to read xattr id index table
Successfully mounted '/tmp/tmp.VDQuL5/um-update.swu' to '/tmp/um-toolbox.XXj9QiXF//mnt/update_root_mnt'.
Performing update...
chroot script execution additional environment:

DISPLAY_TYPE=uc2
PARTITION_TABLE_FILE=jedi_emmc_sfdisk.table
SYSTEM_UPDATE_CONF_DIR=/etc/jedi_system_update/
SYSTEM_UPDATE_SCRIPT_DIR=/usr/libexec/jedi_system_update.d/
TARGET_STORAGE_DEVICE=/dev/mmcblk1
UPDATE_ROOT_MNT=/mnt/update_root_mnt
UPDATE_SAVE_MNT=/mnt/update_save_mnt
SOFTWARE_INSTALL_MODE=restore
executing: //usr/libexec/jedi_system_update.d//09_load_extern_modules.sh
Only insert kernel modules in update mode
executing: //usr/libexec/jedi_system_update.d//15_check_guid.sh
Reading GUID from i2c EEPROM ...
GUID read from EEPROM: '0x23 0x6a 0xff 0xff 0xff 0xff 0x30 0x61 0x1e 0xe6 0xe6 0xc1 0x41 0x8d 0x97 0x86'.
Valid GUID.
executing: //usr/libexec/jedi_system_update.d//20_save_data.sh
Skipping data backup step, because we are in: 'restore' mode.
executing: //usr/libexec/jedi_system_update.d//30_prepare_disk.sh
Partition resize not required.
executing: //usr/libexec/jedi_system_update.d//50_update_files.sh
5.3.0
[   10.868599] random: crng init done
cat: write error: Invalid argument
Updating to Ultimaker version: 5.3.0
[   10.913606] f2fs_msg: 6 callbacks suppressed
[   10.913618] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   10.923896] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   10.929433] F2FS-fs (mmcblk1p2): Failed to get valid F2FS checkpoint
[   10.936372] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   10.942332] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   10.947861] F2FS-fs (mmcblk1p2): Failed to get valid F2FS checkpoint
mount: mounting /dev/mmcblk1p2 on /tmp/um-target_root.MaBkkJ failed: Invalid argument
Error: unable to mount '/dev/mmcblk1p2'.
Cleaning up update_target: ok
Cleaning up, unmount: '/tmp/um-toolbox.XXj9QiXF//mnt/update_root_mnt'.
Cleaning up, unmount: '/tmp/um-toolbox.XXj9QiXF//mnt/update_save_mnt'.
Cleaning up, unmount: '/tmp/um-toolbox.XXj9QiXF/proc'.
Cleaning up, unmount: '/tmp/um-toolbox.XXj9QiXF/dev'.
Cleaning up, unmount: '/tmp/um-toolbox.XXj9QiXF/tmp'.
Error: Failed to run toolbox update '/tmp/um-toolbox.XXj9QiXF//usr/sbin/start_update.sh /tmp/um-toolbox.XXj9QiXF /tmp/tmp.VDQuL5/um-update.swu /dev/mmcblk1 uc2 restore'.
Cleanup: umount '/tmp/um-toolbox.XXj9QiXF'.
Error, update failed: executing '/tmp/tmp.VDQuL5/start_update.sh /tmp/tmp.VDQuL5/um-update.swu /dev/mmcblk1 uc2 restore'.
Trying old interface firmwares <= 5.2.16.
Warning: Missing argument, could be SOFTWARE_INSTALL_MODE? Defaulting to update.
Warning: Missing argument, could be SOFTWARE_INSTALL_MODE? Defaulting to update.
Checking command availability.
[ is a shell builtin
echo is a shell builtin
exit is a special shell builtin
mktemp is /bin/mktemp
mount is /bin/mount
mountpoint is /bin/mountpoint
rmdir is /bin/rmdir
shift is a special shell builtin
umount is /bin/umount
Preparing toolbox ...
[   11.378805] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[   11.388942] squashfs: SQUASHFS error: unable to read xattr id index table
Successfully mounted '/usr/share/jedi-system-update/um-update_toolbox.xz.img' on '/tmp/um-toolbox.XXHiJyLe'.
Running toolbox update ...
Checking command availability.
[ is a shell builtin
chroot is /usr/sbin/chroot
echo is a shell builtin
eval is a special shell builtin
exit is a special shell builtin
mount is /bin/mount
mountpoint is /bin/mountpoint
shift is a special shell builtin
tr is /usr/bin/tr
umount is /bin/umount
Preparing update...
Mounting firmware update file.
[   11.738841] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[   11.746355] squashfs: SQUASHFS error: unable to read xattr id index table
Successfully mounted '/tmp/tmp.VDQuL5/um-update.swu' to '/tmp/um-toolbox.XXHiJyLe//mnt/update_root_mnt'.
Performing update...
chroot script execution additional environment:

DISPLAY_TYPE=9066
PARTITION_TABLE_FILE=jedi_emmc_sfdisk.table
SYSTEM_UPDATE_CONF_DIR=/etc/jedi_system_update/
SYSTEM_UPDATE_SCRIPT_DIR=/usr/libexec/jedi_system_update.d/
TARGET_STORAGE_DEVICE=/dev/mmcblk1
UPDATE_ROOT_MNT=/mnt/update_root_mnt
UPDATE_SAVE_MNT=/mnt/update_save_mnt
SOFTWARE_INSTALL_MODE=update
executing: //usr/libexec/jedi_system_update.d//09_load_extern_modules.sh
[   12.102194] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   12.108183] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   12.113682] F2FS-fs (mmcblk1p2): Failed to get valid F2FS checkpoint
[   12.120707] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
mount: mounting /dev/mmcblk1p2 on /tmp/um-target_root.JElCbj failed: Invalid argument
Error: unable to mount '/dev/mmcblk1p2'.
Cleaning up, unmount: '/tmp/um-toolbox.XXHiJyLe//mnt/update_root_mnt'.
Cleaning up, unmount: '/tmp/um-toolbox.XXHiJyLe//mnt/update_save_mnt'.
Cleaning up, unmount: '/tmp/um-toolbox.XXHiJyLe/proc'.
Cleaning up, unmount: '/tmp/um-toolbox.XXHiJyLe/dev'.
Cleaning up, unmount: '/tmp/um-toolbox.XXHiJyLe/tmp'.
Error: Failed to run toolbox update '/tmp/um-toolbox.XXHiJyLe//usr/sbin/start_update.sh /tmp/um-toolbox.XXHiJyLe /tmp/tmp.VDQuL5/um-update.swu /dev/mmcblk1 9066 update'.
Cleanup: umount '/tmp/um-toolbox.XXHiJyLe'.
Error, update failed: executing '/tmp/tmp.VDQuL5/start_update.sh /tmp/tmp.VDQuL5/um-update.swu /dev/mmcblk1 9066'.
A critical error has occurred, entering recovery mode.

##################################################
#                   ▄▄▄      ▄▄▄                 #
#                   ███████▄▄███▄                #
#                 ▄███  ▄▄   ▄▄ ▐█               #
#              ▄██  ██ ▀▀▀   ▀▀▀▐█▄              #
#              ███▄▄██  ▄▄▄▄▄▄▄ ▐██              #
#               ██████ ▀       ▀ ▐█              #
#            ▄████▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█▄           #
#          ████▐█ ▐████████████████▌▐██▄         #
#        ▐███▌▄▄█ ▐████████████████▌▐█▄█         #
#         ███████ ███████▀▀ ▀██████▌▐██▌         #
#         ███████ █████████ ██▐████▌▐██▌         #
#        ▄███████ ██████▄██████████▌▐█▀█         #
#        ████  ▐█ ▐████████████████▌▐█ █▌        #
#        ▀███ ███   ▀▀▀▀            ▐██▀         #
#           ▀▀████▄▄████████████████▀            #
#             ▐████████▀▀████▀▀▌  █▌             #
#            ▄██████  █  ▐███▄▄█▄▄██             #
#            ████████▀▀▀█▀████▀    ██            #
#            █████████    ▐███     ██            #
#              ▀███▄█▄▄▄▄▄███▀▀▀▀▀▀▀             #
#                                                #
# Starting busybox rescue and recovery shell.    #
# Tip: type help<enter> for available commands.  #
#                                                #
##################################################
sh: can't access tty; job control turned off
/ #
 

[jordyR 2]

also when i start putty and start up the UM3 without SD firmware recovery i got this information

 

U-Boot 2016.05-ultimaker-00017-g68b3b1c (Apr 09 2018 - 14:28:14 +0200) Allwinner                                                                                                                                                              Technology

CPU:   Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 1, SUNXI SD/MMC: 0 (eMMC)
In:    serial
Out:   serial
Err:   serial
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
Press CTRL-c to interrupt Ultimaker boot up.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
MMC: no card present
scanning bus for devices...
Found 0 device(s).

SCSI device 0:
    Device 0: not available
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found

USB device 0: unknown device
ethernet@01c50000 Waiting for PHY auto negotiation to complete......... TIMEOUT                                                                                                                                                              !
ethernet@01c50000: No link.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-cc-bd-d3-00-17-a7
ethernet@01c50000 Waiting for PHY auto negotiation to complete......... TIMEOUT                                                                                                                                                              !
ethernet@01c50000: No link.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
ethernet@01c50000 Waiting for PHY auto negotiation to complete......... TIMEOUT         

[gr5 2,179]

So here is the relevant error:

Error: unable to mount '/dev/mmcblk1p2'.

 the 1 in blk1 is the SSD on the olimex.  P2 means partition 2.  I talk about this in my unbricking web page.

 

The latest firmware for UM3 appears to be 5.3.0.  This is very unfortunate!!  The firmware people added code somewhere around 5.7 (for S3, S5, S7 only) that will automatically handle the above error and reformat mmcblk1p2.

 

So you need to (as a minimum) reformat partition 2 on mmc blk1.  By the way there are more errors shown but we already know the problem is partion 2.

 

[   12.102194] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   12.108183] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527
[   12.113682] F2FS-fs (mmcblk1p2): Failed to get valid F2FS checkpoint
[   12.120707] F2FS-fs (mmcblk1p2): invalid crc_offset: 64527

 

 

So you need to format the partition.  You will need f2fs.  This is getting more complicated unfortunately but this is 100% the problem and similar to what I expected.  What I didn't realize is that this recovery image is so old - about 5 years old maybe?  And it doesn't have the better recovery code that is in 5.7.X.

 

Anyway once it finishes printing out the sad robot, it's time to hit the Enter key on your keyboard and try to log in.  If it asks for username and password, username is root and I'm not sure of password.  It might not ask for either - it might be that you are already logged in.

 

Read the stuff on my web page.  I try to walk you through the steps.  They aren't trivial but not too bad either.  Try to jump right to the f2fs format commands.  Step 5.  If it doesn't know the command it means the f2fs partition code isn't installed.  So you can read about apt-get.  You will need your printer on the internet to use apt-get.  Anyway I'm just repeating what is already written up in the unbricking document.  If step 5 doesn't work go back to step 1, getting the network working so you can use apt-get to get the f2fs formatting ability.

 

Even once you get f2fs working, it might fail the format command.  Try a few times.  If it won't format you need to repartition.  I talk about that as well.  At least you don't have to install any software to repartition!

[gr5 2,179]

I wonder what would happen if you used the S5R1 firmware recovery on the UM3.  Would it repartition and reformat before it notices it's on the wrong hardware?  If that works then you can switch back to the UM3 recovery as the partitions would be all formatted by the S5R1 recovery procedure and the UM3 recovery uSD would now work.  Potentially.

[jordyR 2]

20 minutes ago, gr5 said:

I wonder what would happen if you used the S5R1 firmware recovery on the UM3.  Would it repartition and reformat before it notices it's on the wrong hardware?  If that works then you can switch back to the UM3 recovery as the partitions would be all formatted by the S5R1 recovery procedure and the UM3 recovery uSD would now work.  Potentially.

That could be the case, where van i find the S3 of S5 firmware 

[gr5 2,179]

on.  my.  web.  page.

[gr5 2,179]

You may think you want these recovery firmwares here: https://support.makerbot.com/s/article/1877434822572

 

But they have purposely hidden the S5R1 firmware because the S5R1 printer has deadly exposed voltages near where the uSD goes in so they want you to sign wavers, talk to a human, etc etc.  (all you have to do is keep it unplugged while your fingers are within a meter of the printer) But I have the firmware available on my web page.  And you don't want to use the newer firmwares because UM no longer uses Olimex in the newest printers.

 

If you read my web page it explains which version of the firmware is too old for the auto-formatting and which version is new enough to have it.

[gr5 2,179]

I'd get the oldest version that still has the auto-partitioning which is explained on my web page.