Compiling Incorrect Firmware

General Discussion
1

Basic Information:

Printer Model: Elegoo Neptune 3 Max
MCU / Printerboard: ZNP Robin Nano DW V2.2
Host / SBC Pi4 PiOS Lite
klippy.log

Describe your issue:

The klipper.bin created is wrong. While the Printer flashes the file and renames it to .CUR (The bootloader renames it to .CUR upon “Successful”) the printer itself appears to not startup properly. MCU error states it cannot connect.

The few firmware uploaded online by other owners for this FDM printer work, but compiling it myself does not. I don’t want to use those other klipper firmwares since the only ones I’ve found are compiled for UART, while I want to verify that everyting works while still using the printers USB connector. Even when I compile to use the UART connector, it is still a bad firmware file.

A screenshot shows the repearing loop in my compiled klipper.bin
I tried building on my Desktop and the file is indentical as well.

The firmware is correct enough that the printer bootloader flashes it. However it then gets stuck in a loop.

firmware_hex
firmware_hex2115×751 209 KB

Unless I’m completely misundertanding everything, I don’t know how to proceed from here. Unless i need very specific versions of the build tools and whatever it relies on. If recent updates to various things have broken the ability to compile firmware. And other Neptune 3 Max Klipper owners have yet to update this OS.

2

It is known to work. Likely, you are not following the right process for this board. See Klipper-for-Elegoo-Neptune-series-3D-Printers/Neptune 3 Pro, Plus, Max/Neptune 3 Max/printer.cfg at main · TheFeralEngineer/Klipper-for-Elegoo-Neptune-series-3D-Printers · GitHub

3

Unfortunately their GitHub page and YouTube Channel is what I initially followed. When I ran into the issue I started searching elsewhere if it was a known problem. They to my bad luck did not upload a N3 Max firmware.

I tried cloning the Klipper repo several times hoping it was a bad download.

I’ll have to later tonight solder cables and attempt the UART connections.

If that failed, I would again think that one or several of the dependencies have been updated and are no longer compatible. I’ll post later on the package versions

My Desktop is running latest Fedora and the pi4 is on the latest piOS. Both fresh installations.

4

I’m not sure that I understand what you are referring to.
The recommended approach is:

  1. Set up your Pi with PiOS
  2. Install Klipper and the additional ecosystem via KIAUH
  3. Build and flash firmware according to the instructions linked above (first few lines)
  4. Determine the correct serial path
  5. Set up printer.cfg
  6. Restart Klipper

If this does not work:

  1. Carefully follow Issues flashing the printer board
  2. Provide the klippy.log as initially requested anyway
5

Compiling the firmware with USB communication still does not work. However, when selecting UART as the communication. Then a correct firmware is created.

My specific N3Max Motherboard has the J17 UART pins connected to PA2 and PA2 / UART2