X-Max3 fails to boot after attempted software update

3D Printing
1

Hey guys, Daniel here. Need some help. Yesterday I installed Obico via SSH to my X-max3. After that I notice some updates(Klipper and Moonraker) available on Fluidd, Did them, huge mistake. (MCU Protocol error This is frequently caused by running an older version of the firmware on the MCU(s). Fix by recompiling and flashing the firmware.

Sooo, I reinstall the latest version of the firmware and now I only have this message: THE SYSTEM STARTS ABNORMALLY. Printer won’t Boot and I can’t access it using Fluid or SSH.

contacted QIDI and they sent me a MKSCLIENT recovery file, with no success. Any tips??

2

It’s really annoying that they haven’t gone the last mile for making this printer Just Work with upstream and be able to take updates. I think that they are dependent on Makerbase who are probably where this restriction comes from.

Qidi are pre-selling a 32GB version of their EMMC board with a USB adapter:

That links to a version of the part you can buy now on aliexpress but at least to the US that has a projected delivery between November 28 and December 4.

It also provides a link to download a new image to write to EMMC. That would start over from scratch on updates, but I’d hope it would get you going. I think that you could get any Makerbase EMMC adapter and use it to write a new image to your existing card.

I haven’t found a replacement 8GB EMMC module that definitely declares itself to be compatible with Makerbase. It might be that the common modules for the nanopi are electronically equivalent?

Oh, I just found this one with a comment:

EMMC card and adapter both worked although I would have preferred a USB interface for the adapter over the microsd. Got this for a qidi x plus 3 printer, just right before they released their own. Securing screw in the wrong place but this can easily be held down with a printed bracket.

You can see the different mounting holes in these pictures, of the Makerbase unit:

image
image1080×1080 104 KB

vs. the NanoPi unit that is apparently electrically compatible but would need an adapter for the Qidi:

image
image960×1019 187 KB

That probably means that you could re-flash the images they provide with any nanopi-compatible microSD or USB adapter and those seem to be widely available and cheap.

One of the many youtube reviews linked at the top mentions that the reviewer did an update and that Qidi sent him a new EMMC module. So really since they don’t tell you in the documentation not to do normal updates, they should send you one for free as well. It’s most definitely their fault for shipping a unit that shouldn’t be upgraded, and then not mentioning it in their documentation.

That’s a really bad security practice, and eventually it would be nice to make the system upgradeable. But in the meantime, I placed an order for the 32GB module the moment it came out so that I’ll have it on hand if anything goes wrong…

Hope that helps!

3

Michael, that helped immensely. Already order the 32gb Emmc and im looking for an adapter to flash this existing one. So far, Qidi only give me instructions on how to repair Klipper and moonraker, but if this Emmc is busted as I suspect, I will ask them to send me a new one.

Tks a lot for you help.

Have a great day.

1 Like
4

If you can’t ssh in, it’s hard to fix…

I wonder whether it would be possible to flash a system image to a microsd card and boot off that? The MKS SKIPR on which the X-4 control board seems to be based supports booting from microsd. You might be able to:

  • Write the system image to a microsd card
  • Boot with the microsd card installed
  • Use ssh to get into the system running from microsd
  • Write the system image to the EMMC module from the system running on the microsd
  • Reboot without the microsd card installed.

That’s just a thought, nothing I’ve tried.

In any case, it would be only the contents of the EMMC that are the problem, so if they send you a new EMMC module, you could still use the old one as a backup — you would just need to write a new image to it.

5

That sounds a bit too advanced for me, I just learned how to ssh couple days ago. LOL

I got a windows pc now and will try to ssh using ethernet, since Macs don’t have ethernet ports anymore and using terminal to ssh is kind hard. if that don’t work I will try your way.

6

Ah, yes, updates are set up to overwrite the wifi configuration. That’s a very annoying design defect of this system. I ended up connecting mine to wired ethernet permanently.

7

No luck Michael, the system doesn’t recognize the sd card as the main boot image. I even try to boot without the EMMC on. Got the same message on the display and wasn’t able to ssh. I guess I will have to wait for the new EMMC card arrive once I wasn’t able to find an adapter to flash the old one here in Brazil.

8

I’m sorry! I wish it had worked. I hope the new EMMC card arrives soon! :crossed_fingers:

9

Hi Daniel,
Did you end up with a solution to this issue?
I am having the same issue now with identical steps to get there.
Install Obico,
Update in Fluidd,
Update causes MCU issues,
Flash using firmware from Qidi website,
No longer boots and instead shows abnormal boot error.

10

I replaced the EMMC, you can try to flash yours, but you will need the makerbase adapter.

I believe the better option is to buy the 32gb Emmc. That’s what I did. Along with it, comes the adapter to flash your old EMMC, so you end up with a spare EMMC.

1 Like
11

I did the exact same thing and am stuck. Can you explain to me what I need to do? Thanks!

12

did you find a solution, I have the same problem

13

Buy the 32gb EMMC from Qidi. You will need to update the system with the latest software after installing it.

14

Hi there i have bought the 32 GB Module from QIDI tech direcktly (beside from some custom problems , had to pay an extra fee of 26€ ) . I replaced the EMMC. But when it boots up its a brick. When is switch on the Qidi X plus 3 it runs into booting cycle and is unpacking the image in an grey screen.of progress, this comes than to 100% end.
And the Display is popping up in the blue scren of Failure Diagnosis…But i cant do noting on the screen it shows only
error:
nothing more i cant actuate firmware restart or klipper restart.
When i switch off and on it runs into depacking the image again .
Cant adjust WIFI or other things cause the softkey to setting dosnt work.
Any suggestions.

15

@Logiclinux Are you following QIDI’s instructions for writing an image to the EMMC modules? I believe that the modules don’t ship with an image installed because they are applicable to several printers, and you have to choose the right image for your printer.

16

Here’s a script for recovering in many cases without replacing the eMMC

17

and work it now ?

18

I had the same problem after a Klipper version update from Fluidd’s setup page… I was able to fix it by the following steps, which require two USB flash drives:

a) Flashed a microSD card with xindi-20230309.img by using Balena Etcher;
b) opened the boot partition of the microSD card and added a uEnv.ini file with the following contents:

dtb_name=/dtb/rockchip/rk3328-roc-cc.dtb
bootargs=root=/dev/sda1 console=uart8250,mmio32,0xff130000 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian

c) inserted the microSD card in a microSD to USB adapter and inserted the USB adapter in the USB port at the top;
d) waited a long time for the system to boot and the regular main screen show at the printer display;
e) ssh to the printer using user mks and the default password
f) inserted another USB flash drive into one of the USB ports in the mainboard at the back;
g) in the ssh screen typed: lsblk to see if all 3 block devices were recognized. the default eMMC should show as mmcblk1, the microSD should show as /dev/sda1 and the USB flash drive in the back should show as /dev/sdb1
f) followed the steps in Bill Kerney’s GitHub: [GitHub - billkenney/revert_qidi_software: revert klipper and moonraker to working versions from qidi’s repo, and install the latest working version of fluidd] to replace the contents of the eMMC with the contents in the xindi-20230309.img file;
g) removed the microSD adapter from the top USB port and the secondary flash drive from the back USB port;
h) rebooted the printer (should boot from the eMMC now) and waited for the main screen to show up;
i) ssh into the printer again with the same credentials as above;
j) followed the steps in the same web page linked about making sure to use the section that was compatible with MY X-Max3: qidi_3series_recovery/README.md at main · billkenney/qidi_3series_recovery · GitHub
k) reboot again and rejoice.

As always your mileage may vary and I’m not responsible if you end up screwing your printer even more.

2 Likes
19

Please note that you need to replace the paths in the dd statement with the correct device names on your instance. If you copy Bill Kerney’s commands as shown in his page, it will probably NOT work because your printer may map devices a little different (my did: /dev/mmcblk1 instead of mmcblk0 and maybe your /dev/sdax will map differently. Be aware and make the correct changes to your environment.

2 Likes
20

Unreal, I just bought one of these and ran into the same issue after I did an initial bency print. I litterally got one print in and then got the error, that MCU version wasnt right. I then updated the two directories ( moonraker needed sudo) and then the printer updated and brought me to the same damn place you guys were at.

My issue is, I bought this thing for the printer bed size so I can make less trips to the printer after my surgery in 2 days. I wont be able to get the part in time and I am sad I wont get to use this thing now…

One GD test print in.

My X1C and Kobra3 never have software problems.

I have the 5 head XL coming, but thats going to be a porch ornament for a few months lol.

Whhyyyyyyy!!!

Thanks for getting us the solution though!