Everything was working great a couple days ago, but now everytime I try and run druid, it says ‘can’t find crow device’, and crow doesn’t seem to be responding to incoming triggers. I’ve tried rebooting, different USB cables and still nothing. Am I missing something?

ran into this the other day, do the steps outlined here help?

I haven’t tried forcing the bootloader yet because I was confused about what a jumper was, and it was hard to tell what I needed to do.

gotcha – a jumper is just a bit of plastic-enclosed metal that goes over pins on a board to open, close or bypass circuits:

image

if you don’t have any, you can just use a regular ole (unpatched) patch cable and just place it on the top and middle pin in this orientation:

power on your synth with the cable touching those two pins and after a second or two, you can remove the patch cable. crow will be in bootloader mode.

the reason why a cable works as a jumper is because either is just metal bridging the pins

can i use i2c cables on the center pins or ground pins when booting up? i tried with an unplugged patch cable and i’m still getting the ‘can’t find crow device’ after i power up.

no, different construction.

once you use the patch cable to bridge the ground and center pin (either side of the two columns of pins, doesn’t matter), you used terminal to successfully connect to crow and were able to successfully execute ./erase_userscript.sh? or did those steps fail? in other words, druid will still report ‘can’t find crow device’ until you perform those steps. just looking to figure out where things are going wonky :slight_smile:

No problem----after I did the grounding with a patch cable, I typed ‘druid’ into the terminal and still got the ‘can’t find crow device’ message.

SCOTTs-MBP:~ scottburton$ druid

can’t find crow device

SCOTTs-MBP:~ scottburton$ ./erase_userscript.sh

-bash: ./erase_userscript.sh: No such file or directory

SCOTTs-MBP:~ scottburton$ ^^c

-bash: :s^^c: no previous substitution

SCOTTs-MBP:~ scottburton$

This is what it’s giving me unfortunately.

gotcha, thanks for that!

the trouble is that you cannot perform this task through druid:

  1. please open a fresh terminal session (quit terminal if it’s open and start it again)
  2. use cd to change directory to the downloaded firmware folder
  3. then you can enter ./erase_userscript.sh

you should not be executing druid at all. do those steps work?


Having trouble using the cd command?

  • Mac: right click the unzipped crow-vx.x.x folder and then press the OPTION key. This will reveal a Copy “crow-vx.x.x” as Pathname action. Select it and then paste into terminal after cd [spacebar] .
  • Windows: hold the SHIFT key and right click the unzipped crow-vx.x.x folder. This will reveal a Copy as path action. Select it and then paste into terminal after cd [spacebar] .
  • Linux: right click the unzipped crow-vx.x.x folder and select “ Copy ”. Then, simply Paste into terminal after cd [spacebar] .

okay I’ve got that part to work, and now there is this, when i try to execute flash.sh

SCOTTs-MBP:crow-v1.0.0 scottburton$ ./flash.sh

dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.

Copyright 2010-2016 Tormod Volden and Stefan Schmidt

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature

dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!

Deducing device DFU version from functional descriptor length

dfu-util: No DFU capable USB device available

SCOTTs-MBP:crow-v1.0.0 scottburton$

thanks so much for walking me through this!

happy to help!

apologies, but you are executing commands that are not part of the instructions :joy:. this is a super helpful data point to have, but it’s also causing some false negatives

the only things you should be typing into a fresh terminal session to clear a persistent ‘can’t find crow device’ status are:

  • cd [wherever your downloaded crow firmware folder is]
  • ./erase_userscript.sh

this just means that the bootloader isn’t running (or crow isn’t connected via USB)-- can you try forcing it again by power cycling your synth and placing the cable on those aforementioned pins?

I tried it and got the same message:

dfu-util: No DFU capable USB device available

blugh, I’m sorry for the trouble! dm’ing you :slight_smile:

closing the public loop: @scotttburton got it all working on their own!

3 Likes

Thanks again for the patience.

1 Like

hey friends

need some help installing druid
i have followed the steps for mac and have confirmed i’m running python 3.8.0 in terminal

next step when i try upgrading setuptools this error prints:

ERROR: You must give at least one requirement to install (see "pip help install")

    WARNING: You are using pip version 19.2.3, however version 19.3 is available.

    You should consider upgrading via the 'pip install --upgrade pip' command.

@glia what command are you typing to install setuptools? it should be this:

pip3 install --upgrade setuptools

Note the -- is not a comment like in Lua, but part of the command. Perhaps just copy & paste your terminal session?

good observation

last night i tried verbatim first and then without what i assumed might be a comment

will try again in a minute when i’m at terminal

ok next step of trouble shooting
how exactly should druid be opened?

just typing “druid” into terminal? cause i tried that and it’s telling me “command not found”

should crow already be connected to open druid?

1 Like

Druid would not open for me until I connected to crow

Also you need to cd into the directory where you have put the Druid scripts or it won’t know where to look for them

1 Like

After running pip3 install monome-druid it’s supposed to work to just run druid, but your terminal might not know where to find the druid program. I think if pip detects this it’s supposed to print some warning like “the file /usr/share/Python38/scripts/druid is in a directory that’s not on your PATH”? That would tell you where the file actually is, which I’m not sure where exactly OSX puts it. If you have a message like this it’s showing you where the file is, you should just need to modify your PATH variable accordingly. If you have some output like this, pasting it might help figure out what to do and what sort of tidbit should be added to the scripting docs.