Duet 2 Ethernet and SBC

smoki3

@bearer but the have to be two as far I got it right

wilriker

@smoki3 The second file http.json is for the DWS (Duet Web Server) not relevant for the problem here.

This is a shot in the dark but please try adding

# Fix core frequency to have constant SPI clock speed
core_freq=250
core_freq_min=250

to your /boot/config.txt and reboot the RPi. It might be that Duet 2 does not like RPi's default SPI frequency shenanigans (neither do I )

smoki3

@wilriker said in Duet 2 Ethernet and SBC:

@smoki3 The second file http.json is for the DWS (Duet Web Server) not relevant for the problem here.

This is a shot in the dark but please try adding
# Fix core frequency to have constant SPI clock speed
core_freq=250
core_freq_min=250
to your /boot/config.txt and reboot the RPi. It might be that Duet 2 does not like RPi's default SPI frequency shenanigans (neither do I )

So this doesn't help. Same behaviour as before
It wired because it only happens while homing.

smoki3

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

ed
[warn] Bad header checksum (expected 0x40cc, got 0xe30e)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000004)
[warn] Bad header checksum (expected 0xc340, got 0xa71d)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000004)
[warn] Bad header checksum (expected 0x40cc, got 0xcdbd)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000004)
[warn] Restarting transfer because the number of maximum retries has been exceeded
[warn] Bad header checksum (expected 0x0040, got 0x5620)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x0002005f)
[warn] Bad header checksum (expected 0x0000, got 0x4260)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x0002005f)
[warn] Bad header checksum (expected 0x0000, got 0x4260)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x0002005f)
[warn] Restarting transfer because the number of maximum retries has been exceeded
[info] Flashing RepRapFirmware
[info] Verifying checksum
[error] Firmware checksum verification failed
[info] Flashing RepRapFirmware
[info] Verifying checksum
[error] Firmware checksum verification failed
[info] Flashing RepRapFirmware
[info] Verifying checksum
[error] Could not flash the firmware binary after 3 attempts. Please install it manually via bossac.
[warn] Bad header checksum (expected 0x80ac, got 0xbe3b)
[warn] Note: RepRapFirmware didn't receive valid data either (code 0x0002005f)
[info] Application has shut down

A Former User

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

A Former User

@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.

A Former User

@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

A Former User

@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.

A Former User

@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?

A Former User

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.