Duet 2 Ethernet and SBC

how long is the cable used, and what type of cable is it?

smoki3

@bearer it's a normal ribbon cable with a length of 8cm

@smoki3 said in Duet 2 Ethernet and SBC:

8cm

should be okay, still try lowering "SpiFrequency": 8000000, to say 2000000 in /opt/dsf/conf/config.json and restart DCS (sudo systemctl restart duetcontrolserver) ?

wilriker

IAP is fixed now also on master branch.

@wilriker said in Duet 2 Ethernet and SBC:

IAP is fixed now also on master branch.

btw i think there was a slight hickup with it refusing M997 S0 - but can't reproduce it after it did update with both DWC asking to update and M997 without S0.

wilriker

@bearer Since there is only one type of firmware to update it is unnecessary to provide a Snnn parameter to M997 in the first place but I agree that it should not result in either a warning or worse an error. If you can reproduce it, please post here.

wilriker

@smoki3 said in Duet 2 Ethernet and SBC:

If I try to flash the firmware over DWC I also get checksum error

If everything is working as expected you should not get any checksum errors at all. If you get them more than once something is still wrong.
Have you made sure that both the Duet 2 and the Raspberry Pi share a common ground connection?

smoki3

@bearer said in Duet 2 Ethernet and SBC:

8000000

This doesn't help

smoki3

@wilriker said in Duet 2 Ethernet and SBC:

@smoki3 said in Duet 2 Ethernet and SBC:

If I try to flash the firmware over DWC I also get checksum error

If everything is working as expected you should not get any checksum errors at all. If you get them more than once something is still wrong.
Have you made sure that both the Duet 2 and the Raspberry Pi share a common ground connection?

Yes both are connected directly to ground

smoki3

I tried now different cables, direct wiring without PCB and 470ohm resistors.

But always the same issue.

Also tried now without resistors, same issue

@T3P3Tony said in Duet 2 Ethernet and SBC:

We are considering a small hardware board to provide the physical interfacing and signal buffering.

if the series resistance is deemed all that is needed, then a few crimps and a printed part goes a long way:

Btw, is there a part# for the nylon stand offs? gonna try a pogo-pin version for the Wifi

gtj0

Jeez. I take some time off and this happens.

smoki3

@wilriker
Today I am back from holidays. I tried to investigate a bit more but it does not help. I disassembled the Duet 2 Ethernet from my printer so I have no other cables in the near of the board. I also made a new cable out of a shielded ethernet cable to avoid any EMC troubles. But still the same. If I try to flash the firmware for example I get many checksum errors.

@bearer
are you now able to flash the firmware over DWC? I always get checksum error.

@smoki3 said in Duet 2 Ethernet and SBC:

are you now able to flash the firmware over DWC?

with both the Wifi and Ethernet (Duets) yes

smoki3

@bearer so I mean with the SBC connected

Which raspberry do you use?

yes yes, update wifi and ethernet boards with RRF3.2 over SPI from the SBC, Once I shortened the wires and had my novice crimp the resistors instead of trying to solder its all good at 8Mhz.

edit: one 4B 4GB, 3B+ and some 2B tested.

smoki3

@bearer How short are your cables?

I'd say the first was about 40cm with questionable soldering, No Bueno... after revisiting it with crimps I'd say 20cm/26AWG(maybe it was 28?) and 15cm/30AWG loose wires, not in a ribbon. 470R resistor crimped in somewhere along the MISO, MOSI and SCK lines.

smoki3

@bearer

wired.... I don't understand why it is not working for me. My cables are less than 10cm, tried different resistors from 100 Ohm up to 500 Ohm. I soldered but this should normally better than just crimping. Also tried loose wires.

It would surprise me if it was a signal integrity issue if it works for other operations than flashing, but at this point I'd get the scope out and take a look.