^^ crow help: general (connectivity, device q's, ecosystem)

jlmitch5 · 2020-05-20T02:53:24.625Z

actually I just did it myself.

so ls -l outputs this:

-rw-r--r--@ 1 jmitchell staff 170 May 19 14:07 osx_linux-download_userscript.command

that stuff on the left is the permissions…it doesn’t have execute permission.

run chmod +x osx_linux-download_userscript.command

and that will fix it, you can then run the script like you tried

./osx_linux-download_userscript.command

mlogger · 2020-05-20T02:58:12.986Z

ok thanks - that’s gets me in

I have more issues now as its not seeing crow

Deducing device DFU version from functional descriptor length
dfu-util: No DFU capable USB device available
dfu-util 0.9
dfu-util: Could not open file blank.bin for reading: No such file or directory

I will try to force the boot loader again

jlmitch5 · 2020-05-20T03:01:51.781Z

hmm, yea try forcing the bootloader turning the case power off and back on and maybe unplug/plug back the usb cable on your computer. whenever crow has not been reachable that and the erase_userscript command has got me back to a working state

mlogger · 2020-05-20T03:09:05.334Z

ok i forced the boot loader again and got more luck

Opening DFU capable USB device…
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0 …
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Limiting upload to end of memory segment, 65536 bytes
Upload [=========================] 100% 65536 bytes
Upload done.
dfu-util 0.9

only one issue is this - not sure if its important or not :

dfu-util: Could not open file blank.bin for reading: No such file or directory

jlmitch5 · 2020-05-20T03:10:46.049Z

Hmm not sure on that one. After a power cycle does crow respond like normal?

mlogger · 2020-05-20T03:17:48.567Z

no, when i start druid it says crow disconnected.
I think now i maybe have to install the firmware again?
I will try that as a file was generated for @Galapagoose here userscript.bin.zip (2.1 KB)

jlmitch5 · 2020-05-20T03:21:24.567Z

o hmm I don’t think I had to reflash the firmware again, basically after i did the erase_userscript (the one that comes in this release…not the special one), after removing the short on the i2c pins, booting the synth back up (and maybe plugging/unplugging the cable) druid showed “crow connected” again. could be that this special one is different and does need a firmware flash?

about to head to bed, good luck on figuring it out!

mlogger · 2020-05-20T03:22:53.804Z

thanks for your help, much appreciated
I will reflash it, i can’t see it doing any harm.

jlmitch5 · 2020-05-20T03:23:44.922Z

no worries, really excited to hear what you’re making with your monome system!

mlogger · 2020-05-20T03:48:42.587Z

mlogger:

I will reflash it, i can’t see it doing any harm.

@Galapagoose - The issue i got from your script was this error.

dfu-util: Could not open file blank.bin for reading: No such file or directory.
It generated the bin here ^^ crow help: general (connectivity, device q's, ecosystem) - #452 by mlogger
Also i was still getting a “crow disconnected” in Druid so decided to reflash.
v1.03 uploads ok (had to force the boot loader again) but it won’t reset to runtime

Download done.
File downloaded successfully
dfu-util: can’t detach
Resetting USB to switch back to runtime mode
At this point, nothing happens.
I reboot my case, open Druid and i still get a “crow disconnected”

csboling · 2020-05-20T05:42:35.581Z

Sounds like this is saying it couldn’t find blank.bin in the folder where you ran the script, you may need to be in the same directory as the blank.bin file. This file is included in the crow firmware release bundles and is literally just 16 bytes of zeros to overwrite metadata about the script’s length / the state of user script flash, here you go: blank.bin (16 Bytes).

You can open your userscript.bin file downloaded from the module in most text editors, there is some extra binary stuff at the beginning and end but otherwise the contents of the file is crow’s lua script from flash. This looks like a pretty complicated script so it’s hard to say where exactly it’s crashing. Not sure what firmware version you’ve now flashed to but the development builds have some fixes for some of the most common crash scenarios (infinite loops, stack overflow, out of memory). You can find the development builds that completed successfully from this github feed.

mlogger · 2020-05-20T11:53:20.686Z

Thanks, I’m on the v1.03 https://github.com/monome/crow/releases but still get a “crow disconnected” in Druid were previously v1.03 was working fine before the crash. That v1.03 had the blank.bin in the folder. So the only error I got from that v1.03 error was dfu-util: can’t detach after loading the firmware. I think I will try some of the development builds to see if I can get it to work. Thanks for the link, I wasn’t aware of those.

Galapagoose · 2020-05-20T14:51:34.827Z

Apologies for not giving much context here. The erase_userscript.command file needs to be run in bootloader mode – it is the same as flashing the firmware, except it is flashing some data (a few zeroes to disable the uploaded userscript).

The process is:

Force the bootloader by bridging the ground + middle pin of the i2c connection. keep these pins bridged.
Restart your modular system. Crow should now be in bootloader mode.
Run osx_linux-erase_userscript.command from the v1.0.3 firmware update folder.
You should see:

Download done.
File downloaded successfully
dfu-util: can’t detach
Resetting USB to switch back to runtime mode

Remove the jumper on the i2c connection.

Now crow should appear in druid with <crow connected>. If it still doesn’t, try restarting your computer. If there’s still trouble, we can try erasing everything on chip except the bootloader. Let me know.

Thanks for uploading the userscript.bin file! I’m going to flash it to my crow and see if I get the same crash. Apologies for having the permissions wrong & not explaining that it needs to be run from the firmware folder.

Frogstar · 2020-05-20T17:20:02.660Z

Had to update my mac os to run the sweet new Logic sampler and it changed my terminal shell. Now calling druid gives me a zsh: command not found error. I can still run druid by clicking the finder file. I think its a path issue but I can’t figure out how to fix it.

– please ignore. I sorted it by doing this in terminal. I’m feeling very grown up!

path+=(’/home/david/pear/bin’)
export PATH

mlogger · 2020-05-21T03:01:01.280Z

OK this has worked
Couple of key things i did differently than before, was the bridging.
Previously I bridged while powering up, to get to bootloader, then unbridged before loading up the dfu. It’s not clear in the docs how long to hold the bridge for (i was assuming just for boot up), but is very clear in your instructions.
So this time i used a real pin bridge jumper and only removed after the dfu had finished uploading.
After loading up and unbridging i was still getting a “crow disconnected”

Galapagoose:

If it still doesn’t, try restarting your computer.

I had to restart the computer and finally got a “crow connected”
Thanks for you help and also to @csboling and @jlmitch5

chailight · 2020-05-28T14:21:04.176Z

I’ve had a crow in a 7U 84HP case with a DIY power supply and had no issues with it.

Moved the majority of my rack into an Amalgamod 7U 102HP case with an Elby powered busboard (ED126 & ED123)

elby-designs.com

ed126-guide.pdf

1929.42 KB

https://www.elby-designs.com/webtek/power/busboards/ed123/ed123-guide.pdf

The PSU is a 4MS Power Brick 90. (15V, 90W, approx 4.6A)

Everything else in the case works fine, but the crow does not seem to function. I first noticed the issue when druid showed a status of “crow disconnected”.

I thought I might not have plugged in the power ribbon correctly. I tried reseating the cable, no change. Tried several over outlets on the distribution board, no change. Tried taking several power hungry modules out of the case, no change.

The crow still works fine in the other case, so there’s no issue there. I set the crow to running First, and put it back in the new case to see if it would run there, even if it wouldn’t talk to druid.

Noticed that it was putting out 10V on all outputs.

Seems that there is something strange in the way the unit is being powered in the new case,

The old case has 5V supply, but the Elby does not. But crow does not need 5V right, so that shouldn’t be an issue.

Is it the timing of the power up, perhaps an issue during powerup with other modules being hungry?

If anyone else has seen something like this or has suggestions I should try, I’m all ears. I’ve double checked the polarity of the power cables during connection, so I’m confident it’s not that,

Very keen for crow to live next Just Friends and also take input from a 16n, so any suggestion is welcome.

Thanks in advance.

Galapagoose · 2020-05-28T15:55:14.736Z

The outputs sending 10V indicates that the microcontroller is not starting up. This is most likely a power issue. Do you have a multimeter? If so there are 2 test points on the bottom of the crow PCB that should read +3.3V and +3.1V.

I’m guessing it has something to do with some kind of soft-start condition confusing the microcontroller…

chailight · 2020-05-29T01:06:05.728Z

thanks @Galapagoose - I’ll aim to do a voltage test on the crow as you suggest. Elby has a module power delay component that sits in line with the power cable for an individual module - can delay power by up to 10 secs - may help in terms of separating the crow from the rest of the modules startup sequence.

(also thanks to the mods for relocating my question to the correct thread - much appreciated).

dmon · 2020-05-31T15:24:38.363Z

I might have encountered a bug in the crow.connected() function with norns. It always returns false, even when crow is connected (and even outputing stuff). Can anybody verify this?
Cheers

csboling · 2020-05-31T15:58:12.442Z

Indeed, looks like a typo in this lua function. One-character patch submitted here.