Da Vinci MCU unable to connect

General Discussion
1

Basic Information:

Printer Model: Da Vinci 1.0 Pro
MCU / Printerboard: original davinci motherboard, processor SAM4e8e AU
Host / SBC Pi 4
klippy.log loaded
klippy.log (305.8 KB)

Describe your issue:

I finally got it flashed, i’m fairly sure using the information I found in this thread

and a few other places,
I got it to show the serial path after flashing using the settings for it provided by DaVinci10 who has done a tramendous amount of work on these printers,

however, when restarting klipper it says printer is not ready despite the serial port being available. and after a few minutes it defaults to

Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer```

what am I doing wrong? is it the cpu settings? it seems to flash just fine?
...
2

Hello @EleriLove !

You took his serial?

1 Like
3 
[mcu]
serial = /dev/serial/by-id/usb-Klipper_sam4e8e-if00

This does not look like a correct serial. Either not correctly flashed or the information from ls /dev/serial/by-id/* not correctly entered.

4

I used the serial from the
ls /dev/serial/by-id/*

5

hmmm, I coppied it directly from the putty output, i’m curious now if the pins at launch in make menuconfig are incorrect… what would you suggest for figuring out the pins on my own?

6

here’s an output of my terminal directly from the rpi 4 ssh connection, right after a reflash. and a copy of the settings I used to flash it with.

/dev/serial/by-id/usb-03eb_6124-if00
Davinci@DaVinci:~/klipper $ sudo service stop klipper
[sudo] password for Davinci:
stop: unrecognized service
Davinci@DaVinci:~/klipper $ sudo service klipper stop
Davinci@DaVinci:~/klipper $ make flash FLASH_DEVICE=/dev/serial/by-id/usb-03eb_6                                                                                                                                                             124-if00
  Building out/autoconf.h
  Flashing out/klipper.bin to /dev/serial/by-id/usb-03eb_6124-if00
Entering bootloader on /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00                                                                                                                                                             .0-usb-0:1.4.1:1.0
Device reconnect on /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-                                                                                                                                                             usb-0:1.4.1:1.0
lib/bossac/bin/bossac -U -p /dev/serial/by-path/platform-fd500000.pcie-pci-0000:                                                                                                                                                             01:00.0-usb-0:1.4.1:1.0 -e -w out/klipper.bin -v

Erase flash

Done in 4.581 seconds
Write 26272 bytes to flash (52 pages)
[==============================] 100% (52/52 pages)
Done in 0.366 seconds
Verify 26272 bytes of flash
[==============================] 100% (52/52 pages)
Verify successful
Done in 0.295 seconds
Davinci@DaVinci:~/klipper $

    Micro-controller Architecture (SAM3/SAM4/SAM E70 (Due and Duet))  --->
    Processor model (SAM4e8e (Duet Wifi/Eth))  --->
    Communication interface (USB)  --->
    USB ids  --->
(!PC25,!PD6,!PD5,!PD3) GPIO pins to set at micro-controller startup

the ls /dev/serial/by-id/* then changes to

ls: cannot access '/dev/serial/by-id/*': No such file or directory

which was… not what it was doing last night,

7

You noticed that this is different from:

So, your board cannot have been flashed correctly in the first place.

In addition, there are reports that this MCU has troubles with newer Debian OS versions. See this link, which so far seems unsolved. If it is related to your board, I cannot tell.
The only solution seems to be flashing the board under a different Linux OS. Once correctly flashed, it should work.

It is my understanding that a successfully flashed board should return something like:

/dev/serial/by-id/usb-Klipper_sam4e8e_00313753383436313139303139303535-if00

I do not own this or a similar board, so I cannot offer much more guidance.

1 Like
8

you’re brilliant mate, I’ll give it a try, i’m sure I can find an older mainsail os iso somewhere,

9

Thanks to the Illustrious help of @Sineos we were told that there’s a known issue with debian 11 specifically that causes the original board for the Davinci 1.0 pro systems to utterly be incapable of flashing,

at first I was under the impression that I needed an older operating system, however with some reading, and guidance from my friend LuiGoalma, known for his work in DS hacking, we theorized this would work if we just… went to Debian 12.

I quickly flashed the debian 12 version of raspbian os and installed Klipper with Kiauh along with mainsail and… I think everything else?

and then flashed the board the normal way, uppon doing so we did immediately succeed in flashing the firmware and now have something that like @Sineos said looks like this as the output of the ls /dev/serial/by-id/* output

/dev/serial/by-id/usb-Klipper_sam4e8e_003135534A594E4B3230303231303034-if00

which is more in line what we thought, from here it should be easier for others with this board to avoid the pitfalls I’ve faced with this project in the furture,

Happy printing and thank you so much to the Klipper community for your fast and knowledgable contributions.

edit: uppon further reading it seems we are unable to get the original mainboard to control the nozzle as it is a second processor controlled over uart from the first as stated here by the ever helpful Davinci10

will likely have to have a second board in here as well to control hotend,

3 Likes
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.