I’ve tried 3 Pi boards now. Two new Pi Zero 2 Ws and one Pi Zero. None of them connect to the Farduino…seem unlikely to be the Pi boards themselves.
I presume they’re tested before they leave the warehouse, but 3 bad boards in a row seems improbable.
I only have the estop button and foir motors connected, but would that affect the Farmduino to Pi connection?
@FarmDano seems not likely to be RPi Zero problem
Just check that you flashed the SDHC for the RPi Zero 2 W using the rpi3 disk image ?
The RPi Zero connection to the Farmduino Express is serial asynch. Via the 40 pin Header ( pins 8 and 10 )
I used this for the Zero 2 W:
When I attempt firmware flash, I get an error:
@jsimmonds Is there a way to check those pins for data?
Find a friend with a 'scope or a logic analyzer ?
Apparently ( I’ve never done this ) you can use the Arduino IDE to “talk” to the Farmduino Express ( unplug the RPi Zero W first ) which might help isolate your issue ?
I have some debug info in the log:
“\navrdude: Version 6.3-20171130\n Copyright © 2000-2005 Brian Dean, http://www.bdmicro.com/\n Copyright © 2007-2014 Joerg Wunsch\n\n System wide configuration file is “/etc/avrdude.conf”\n User configuration file is “/root/.avrduderc”\n User configuration file does not exist or is not a regular file, skipping\n\n Using Port : /dev/ttyAMA0\n Using Programmer : wiring\n Overriding Baud Rate : 115200\navrdude: stk500v2_ReceiveMessage(): timeout\navrdude: stk500v2_ReceiveMessage(): timeout\navrdude: stk500v2_ReceiveMessage(): timeout\navrdude: stk500v2_ReceiveMessage(): timeout\navrdude: stk500v2_ReceiveMessage(): timeout\navrdude: stk500v2_ReceiveMessage(): timeout\navrdude: stk500v2_getsync(): timeout communicating with programmer\n\navrdude done. Thank you.\n\n”
It appears to attempt to flash, cycles 11 times, then repeats. Do you feel this is normal for the farmduino?
Looking at the source code that flashes firmware into the
Farmduino, yes this is normal
The failure suggests that the RPi Zero W cannot receive any valid message from the Farmduino
( 40-pin header, physical pin 10 )
@jsimmonds I just noticed the software thinks I have a Pi 3…would that affect anything?
" The failure suggests that the RPi Zero W cannot receive any valid message from the Farmduino
( 40-pin header, physical pin 10 )"
Does that mean that all the boards I tried, GPIO 15 is perhaps dead?
I touched a multimeter to it…has .62 through it…so something is here…just don’t know what
Hooked up my Zero to the app with no farmduino, just the board. The connection looks the same, so there’s no talking at all between the Pi and the Farmduino. Feeling hopeless here
Marc from Farmbot said I should just buy the whole electronics box in September, which means I wasted my funds on the Farmduino and all Pi Zeros/2ws.
You could try to fiddle around with that reset function. This was a fix for my device a long time ago when I had similar issues and the same log output. Simply keep the reset button pressed until the flash starts. This will most likely take a few tries until you find the right timing. In my opinion its also easier if you can upload a sketch using Arduino IDE, but you would need a TTL USB converter to access the rx/tx pins on your farmduino.
Thanks, Ascend! All great info
@Ascend With that cable, which pin would you use? I’ll try anything at this point. Ordering the cable tonight
My timing seems off…
Again, probably not.
Are you confident with those “press-fit” 40-pin header connectors that you’re using ?
( seems to me that they would depend alot on the integrity of the plated-through holes and the connecting traces on both the Farmduino and the RPi PCBs !)
They appear to be the major difference between your DIY and a FarmBot Inc. electronics box (?)
That’s what I mentioned earlier . . the correct FBOS disk image file for RPi Zero 2 W is named
farmbot-rpi3-15.3.2.img ( this is because the Zero 2 W architecture closely resembles the RPi3 B Plus )
Really good point, that I didn’t even notice. This is really important and should be checked. Even though it would be really bad luck if all 3 Raspberries would not get proper contact.
I just painted the connection layout using colors that are good to see. The colors of your cable are most likely different. You should also check if your converter does have a 5V output to supply the Rpi and the serial bus gate U6. This way you should be able to upload firmwares to your arduino using a generic Mega 2560 in Arduino IDE.
In the following picture, its wired like this:
Red : +5V on pin 4 (2 works aswell)
Brown : GND on pin 6
Blue : TX on pin 8
Yellow : RX on pin 10
‘Are you confident with those “press-fit” 40-pin header connectors that you’re using ?’
I was not confident that the ‘press-fit’ were working and have been soldered (the newest 2w didnt use a ‘press-fit’ at all to rule this out, so I used a traditional soldered one) None of them are seen by the Farmduino.
At Marc’s request, I checked if the 5v and 3v pins were getting power (with a multimeter) and they were. A bit after that, he said I should buy the electronics box assembled when available.
" Even though it would be really bad luck if all 3 Raspberries would not get proper contact."
If Im being honest, being told to buy more after having some evidence the Farmduino I just bought doesnt work, doesnt feel very good.
@Ascend Greatest diagram EVER. Thank you