Duet 2 Ethernet and SBC

wilriker

@smoki3 So worst case: you fry the SAM4E on the Duet or the ARM of the RPi. That's easy.

Let's put the answer about speed this way: currently the default configuration for Duet Software Framework (which controls the SPI speed) is set to 8 MHz for a Duet 3 (which coincidentally has virtually the same max SPI speed as a Duet 2). And so far there have been very to no occasions where this would not have sufficed. So if you run it at 15MHz (with ~500R series resistors) you are still about twice the speed of the normal D3-SBC speed. I guess you run into step-generation limits before you see issues with SPI speed.

smoki3

@wilriker
allright. I will test it soon!

smoki3

@wilriker does the duet 2 provide enough current on the 5 volt circuit to power the pi? Or is it better to use a separate stepdown module

dc42

@smoki3 said in Duet 2 Ethernet and SBC:

@wilriker does the duet 2 provide enough current on the 5 volt circuit to power the pi? Or is it better to use a separate stepdown module

The 5V regulator on Duet 2 does not provide enough current to power a Pi safely.

A Former User

@wilriker said in Duet 2 Ethernet and SBC:

I tested with no resistors and with 500R

thanks for your effort with this btw! ~~which branch would be the best bet to build Duet2_SBC_RTOS/Duet2CombinedFirmware.bin?~~ nvm checking that all the repos have been switched from dc42 to duet3d github turned out to be an idea

smoki3

@bearer I build 3.02 branch with the SBC Configuration. This should work.

The build have a different file name. So you have to rename it to flash it over DWC

wilriker

@smoki3 Yes, for initial flashing you have to rename it or flash it via bossa (as I did). If you also build DuetIAP and put this into the /sys folder of DSF you can from then on do regular flashing by just uploading the firmware file as is in DWC.

smoki3

@wilriker is it a different DuetIAP as the normal build which is released on GitHub?

wilriker

@smoki3 Yes, it's a new version that will be part of the RRF 3.2.0. You have to clone DuetIAP and have to build SAM4E_SPI_RAM build configuration. This will create a file name Duet2_SBCiap_2SBC.bin.

A Former User

@wilriker did you see anything like https://forum.duet3d.com/post/162547 in your testing?

(that is with 330R inline on the MOSI, MISO and SCK signals, but the ESP is in place with its pins as hi-z and sleeping).

i'll see if I can't put some 2.0mm headers on there so I can switch between WiFi and SBC but will take a while

wilriker

@bearer I remember that I have seen the

6/26/2020, 11:51:59 AM	Connection to Duet established
6/26/2020, 11:52:01 AM	Warning: Lost connection to Duet (Board is not available (no data response))

cycle at least once but I don't remember what the reason/solution was (as there were a lot of errors at that time ). And I have only ever tested with a Duet 2 Ethernet.

Unlikely but: did you use the GPIO0 on the ESP as the TransferReady pin? I remember that while testing I got confused that the header for Ethernet does not have all the pins that the ESP needs and thus some contact points where not what I expected in the first place. Usually if you get that wrong DSF will complain about Duet not being available, though.

EDIT: I only now saw that you get a connection every once in a while (in your example to issue M115). That means basic connection is working. And if SPI speed would be too high that would result in checksum errors rather than no data errors.

EDIT2: There have been a lot of refactorings lately. Let me quickly check if it still works on my test hardware.

EDIT3: That still works (although I get an error with DCS not being able to deserialize a status update but that's something different).

A Former User

@wilriker haha! Don't worry about it too much, it was just a stab in the dark as I had someone to help me with the wiring. I'll get back to it in a couple of weeks.

Anyways yes, i did use gpio0 or EDR_CONN as the net is called, which looked to be the same pin the w5500 uses, and as M115 did manage to sneak through I presumed that was ok. And despite not seeing checksum errors I tried dropping the SPI speed but made no difference.

I just wanted to see if it was possible to not remove the ESP, so far either i messed up hi-z firmware, or it has to GTFO. Thanks for taking a look!

smoki3

I finished my prototype

It has a 5V 3A regulator on it for the raspberry

A Former User

@smoki3 said in Duet 2 Ethernet and SBC:

It has a 5V 3A regulator on it for the raspberry

have you considered the load on the 1A fuse for the fans when you're taking a good chunk out for the 5v buck?

dc42

@bearer said in Duet 2 Ethernet and SBC:

I just wanted to see if it was possible to not remove the ESP, so far either i messed up hi-z firmware, or it has to GTFO. Thanks for taking a look!

If the firmware sets up the ESP reset pin and EN pins as outputs in the low state, then I think it should work without disconnecting the ESP. The additional capacitance of the ESP pins might reduce the maximum available SPI speed a little, but that speed isn't critical.

A Former User

@dc42 said in Duet 2 Ethernet and SBC:

If the firmware sets up the ESP reset pin and EN pins as outputs in the low state

I feel like I'm missing something obvious here; will have a think or two and make a new topic when I've figured it out, or figured out that I'm not gonna figure it out

~~edit: nope, doesn't compute.~~ as suspected, were missing something obvious ..

smoki3

@bearer said in Duet 2 Ethernet and SBC:

@smoki3 said in Duet 2 Ethernet and SBC:

It has a 5V 3A regulator on it for the raspberry

have you considered the load on the 1A fuse for the fans when you're taking a good chunk out for the 5v buck?

Yes you are right. I thought the always on Fan are directly connected to VIN

A Former User

@smoki3 said in Duet 2 Ethernet and SBC:

@bearer said in Duet 2 Ethernet and SBC:

@smoki3 said in Duet 2 Ethernet and SBC:

It has a 5V 3A regulator on it for the raspberry

have you considered the load on the 1A fuse for the fans when you're taking a good chunk out for the 5v buck?

Now you are right. I thought the always on Fan are directly connected to VIN

might not be a problem, you should have 3-400mA left for fans driven by Vin, I was just trying to make sure you'd take it into account.

edit: I've used some of these type of things to tap the fuse for putting on a step down for fans (mini - not low profile, ATM or ATP fuse)
https://www.ebay.com/sch/i.html?_nkw=atp+fuse+tap

smoki3

../src/Libraries/Fatfs/diskio.c:51:10: fatal error: ctrl_access.h: No such file or directory
   51 | #include "ctrl_access.h"
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make: *** [src/Libraries/Fatfs/diskio.o] Error 1
make: *** Waiting for unfinished jobs....

I get this when I try to build DuetIAP. Building in mac.

A Former User

@smoki3 said in Duet 2 Ethernet and SBC:

ctrl_access.h: No such file or directory

i got the same, but as long as you can use Bossa to do any programming after the inital flashing you don't need the IAP binary