Klipper on Duet 3 Mainboard

dc42

@luke-slaboratory, the USB peripheral on the SAME70 is different from the one on the SAM4E.

Leave the cache disabled on the SAME70 initially, get it working without cache first.

Luke'sLaboratory

@dc42 said in Klipper on Duet 3 Mainboard:

@luke-slaboratory, the USB peripheral on the SAME70 is different from the one on the SAM4E.

Leave the cache disabled on the SAME70 initially, get it working without cache first.

Hi! Thank you!!!!!

Yeah I saw in the docs that it has a high-speed USB bus instead of a full-speed USB bus. Any documentation thats quick to share that I could read through to make the transition from the full-speed on the SAM4E? (Honestly just being pointed to the relevant lines of code the firmware would be great) Klipper only needs ~10kb/s max, so as long as its consistent I'm happy.

As for the cache - are you referencing the quad SPI flash at 0x80000000?

dc42

@luke-slaboratory said in Klipper on Duet 3 Mainboard:

Any documentation thats quick to share that I could read through to make the transition from the full-speed on the SAM4E? (Honestly just being pointed to the relevant lines of code the firmware would be great) Klipper only needs ~10kb/s max, so as long as its consistent I'm happy.

All I can suggest is that you look at the code that RRF uses to interface to the USB peripheral, at https://github.com/Duet3D/CoreN2G/blob/3.3-dev/src/SAM4S_4E_E70/SerialCDC.cpp. It calls the USB stack in ASF 3, which is at https://github.com/Duet3D/CoreN2G/tree/3.3-dev/src/SAM4S_4E_E70/asf/common/services/usb. That code in turn calls the USB driver for whichever type of USB peripheral is present.

As for the cache - are you referencing the quad SPI flash at 0x80000000?

No, the memory cache built into the SAME70. It greatly improves performance, but it is tricky to use with DMA.

Luke'sLaboratory

@dc42

Thank you so much! I'm not a embedded dev (Mechanical Engineer here) so it gets hard for me to tell where all the things are coming/going, so this will probably be a big help!!! -

re: Cache - I'm not sure what klipper does regarding the cache - the only characteristics I've played with are the ram location, bootloader offsets, that kind of thing. I'll put my nose back in the datasheets and see what I can come up with!

Thank you!!

Andrey 0

@luke-slaboratory Hello.
Did you manage to make a config for Duet 3 6HC?

Andrey 0

@dc42 Hello.
Did you manage to make a config for Duet 3 6HC?

Luke'sLaboratory

@andrey-0 No. I have not successfully flashed the duet3 6hc with Klipper. I am finalizing my work on the config for the Mini 5 (trying to get the external clock to work for better clock sync) before moving to the 6hc, 3hc, and 1lc.

Andrey 0

@luke-slaboratory Thank you! I will wait.

Andrey 0

@luke-slaboratory Hello.
Did you manage to make a config for Duet 3 Mini 5 or Duet 3 6HC?

Luke'sLaboratory

@andrey-0

Hi!

I'm still learning on microcontroller code, and I've been tasked to integrate the external clock on the d3 mini. this will take additional time. the config+flash settings that I have posted on the PR work fine for now, but my final merge will be more accurate timings for multi-MCU sync.

Andrey 0

@luke-slaboratory Hello.
Did you manage to make a config for Duet 3 Mini 5 or Duet 3 6HC?

Luke'sLaboratory

@andrey-0

Thanks for the interest.

You can visit my github to get a config and flashing information that will work with the mini 5. I haven't yet got it working with the external crystal (which is the condition for merging it into mainline klipper), but using the internal crystal it absolutely works and works well.

dc42

@luke-slaboratory said in Klipper on Duet 3 Mainboard:

I haven't yet got it working with the external crystal (which is the condition for merging it into mainline klipper), but using the internal crystal it absolutely works and works well.

Why does Klipper want to use an external crystal?

Luke'sLaboratory

@dc42

I might have not explained correctly, There's an External Clocking Crystal on PB22/PB23 per the schematic (which was released after I started this project) - The build that I was flashing+using on the Mini5+ didn't set up the clock using an external crystal (or is it just called a clock?) instead using the internal clock. They have requested that I use the external crystal that's baked into the board as they believe it will aid in multi-mcu sync with better clock predictions.

I think they're going for "if its there, use it"

Luke

Andrey 0

@luke-slaboratory

Good evening.

I am trying to run klipper on Duet 3 6HC.

Why, after applying the changes recommended by this link https://github.com/KevinOConnor/klipper/pull/4133/commits/0d5c6d3c029e68875c4adfe3cdc18913ec71bed8, after command make menuconfig, klipper gives an error, here is a photo of the error.

Thank you very much!

lukeslaboratory opened this pull request in KevinOConnor/klipper

closed Config: Add Generic-Duet3-Mini.cfg Board Config #4133

Luke'sLaboratory

@andrey-0

Hi - my PR is only for the Mini5+. it doesn't work at all on the 6hc yet.

rockydubb

@luke-slaboratory Hi, did anyone get around to getting the Duet 3 6HC board to work with Klipper successfully?? Ive been searching since last night on how to get this working just to try it out ... but no luck. Thanks.,

Luke'sLaboratory

@rockydubb

I have two 6hc's on my desk right now in various states of klipper-ification. We're currently trying to figure out something spooky in the clock code - it initializes serial comms on UART1 correctly, but something goes haywire immediately after and it freaks out and stops talking.

Sorry, but we are working on it.

rockydubb

@luke-slaboratory Wow, okay great to hear you guys are working on it. Thanks for letting me know! I'll be looking forward to trying it out once its ready. Thanks for the update!

slaz

@luke-slaboratory Is there any chance that you got further on this? Would appreciate it lots. Thanks lots in advance for all the work you do