Duet 3 6hc and raspberry pi 3 B+ DCS not started
-
yes sir! I started with that and did all of the testings from that post before I started this one. I can try the pin process again?
-
@Macgyver1307 said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:
I can try the pin process again?
If you do, copy paste the output so we can catch anything amiss along the way. If using putty just use the mouse to drag and select text, which will automatically be copied to the clipboard ready to paste in the forum. Then highlight the text (in the forum post editor) and use the Code formatting button (5th button from the left after bold, italics etc).
-
ok sounds good ill start the process again and display the outputs. thanks for the help!
-
pi@duet3:~/spidev-test $ RDY=22 CS=24 ; { gpio -1 mode $CS out > gpio -1 mode $CS out > gpio -1 mode $RDY in > gpio -1 write $CS 1 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)" > gpio -1 write $CS 0 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)" > { ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.0 && echo RX should equal TX. ;} | tail -n3 | cut -b-100 ;} (Pin RDY/22) 1 should equal 1 (Pin CS/24) (Pin RDY/22) 0 should equal 0 (Pin CS/24) TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 RX should equal TX. * list item -
well I tried 22 to 28 ad 24 to 28 with the same output. I would post it but the form says its spam.
-
@Macgyver1307 said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:
I would post it but the form says its spam.
3 posts in a row to the same thread in a short amount of time probably flagged you. Please try again.
-
I'm going to wait till Tuesday and loaded up a fresh pi -4 and see if I still have issues. thanks, Phaedrux!
-
The first bit looks to confirm your Chip Select, and Ready pins are working but the next bit would suggest a problem with the jumper between MISO and MOSI or a problem with the Pi. Did you place a jumper over (physical) pins 19 & 21 as well as 22-24?
TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00This is also in line with the error from DSF.
-
here is the output .
-
sorry I had to snip it because it gets flagged as spam if I put it in as code. jumpers installed on 19-21 and 22-24 . pi is on my desk with nothing attached.
-
@Macgyver1307 said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:
jumpers installed on 19-21 and 22-24 . pi is on my desk with nothing attached.
you only need to run it once with RDY=22 CS=24; the test for 19 and 21 is defined by the
-D /dev/spidev0.0parameter to thespidev_testcommand.So it would look like the SPI bus isn't working on the Pi. You can try to move the jumper (will require a wire) to 35 and 38 (and repeat test with
-D /dev/spidev0.1to see if the other SPI bus is working, which you could then use. -
Just to be 110% sure; you placed the jumper like shown on the picture right, both at the same time?
@bearer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:
-
-
@bearer said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:
-D /dev/spidev0.1
pi@duet3:~/spidev-test $ RDY=35 CS=38 ; { gpio -1 mode $CS out; gpio -1 mode $RDY in; gpio -1 write $CS 1 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)"; gpio -1 write $CS 0 && echo "(Pin RDY/$RDY) `gpio -1 read $RDY` should equal `gpio -1 read $CS` (Pin CS/$CS)"; { ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.1 && echo RX should equal TX. ;} | tail -n3 | cut -b-100 ;} (Pin RDY/35) 0 should equal 1 (Pin CS/38) (Pin RDY/35) 0 should equal 0 (Pin CS/38) TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 RX should equal TX. pi@duet3:~/spidev-test $ -
-
the
spidev_testutility test the MISO and MOSI pins from the SPI bus, so by defining them as RDY and CS you're maybe messing with the results?the white jumper is on MISO and MOSI for
spi0.0spi0.n and the red jumper is onspi0.1spi1.n so, but that doesn't really matter as your previous run showed RDY and CS is okay (so the white jumper is less important in the context of testingspi0.1spi1.n)Leave wires as is (on the last picture), reboot pi to ensure any settings to the GPIO pins are cleared and run
sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.0to test MISO/MOSI from spi0.0. (white wire) and
sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev0.1
sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2to test MISO/MOSI from
spi0.1spi1.2. (red wire)?Either your enviroment or your hardware is failing the SPI loopback test as it stands now. The first line will test MISO/MOSI from spi0.0 and the last line will test MISO/MOSI from
spi0.1spi1.2 - ignoring RDY/CS for now. -
Hmm, spidev0.1 won't work. that is still the same spi bus, but CE1 instead of CE0.
To also enable the auxiliary SPI device (three slave selects) add the line dtoverlay=spi1-3cs to /boot/config.txt.
in other words
echo dtoverlay=spi1-3cs | sudo tee -a /boot/config.txt && sudo rebootand run
sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2(the .2 part only signifies it should use BCM pin 16 (physical pin 36 for CE)then it should allow testing the other SPI bus, (sorry for the confusion, I must have misunderstood the devicetree stuff for that as I've been using that spibus only with an custom overlay for the intended chip, which doesn't seem to create a device node but still works.)
-
@bearer said in Duet 3 6hc and raspberry pi 3 B+ DCS not started:
should
pi@duet3:~ $ sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2 spi mode: 0x0 bits per word: 8 max speed: 8000000 Hz (8000 KHz) TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒. RX | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................................ pi@duet3:~ $ -
@Macgyver1307 I'm not sure what would cause that to fail on both SPI ports, which is why I dragged out the logic analyzer and double checked the test setup, and its does work both with the software and the hardware.
It could be there is something wrong with the Raspberry Pi image, but given you used the DuetPi image that is pre-configured it shouldn't matter.
If the rPi4 doesn't work come Tuesday, you're best bet is probably to either download the DuetPi image afresh - or you can get a jump on it now if you can find the inclination to do so.
pi@duet3:~ $ sudo ~/spidev-test/spidev_test -v -s 8000000 -D /dev/spidev1.2 spi mode: 0x0 bits per word: 8 max speed: 8000000 Hz (8000 KHz) TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒. RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒. pi@duet3:~ $![2020-05-24 16_45_12-Logic 2 [Logic Pro 8 - Connected].png](/assets/uploads/files/1590331619823-2020-05-24-16_45_12-logic-2-logic-pro-8-connected.png)
-
yeah crazy it's not working. the sd card is the one from the duet 3 box I got last week. my duet 3 is working in standalone mode for the moment. this pi had a gpio header touch screen the image before I used it as a duet pi. the question is do I wait till Tuesday with the new PI 4 and just try the sd card in it or do I flash a new complete fresh start on it?
