#137

Got it up and running with a fresh flash. Got the disk expanded. But can’t shake a Supercollider Fail… just reflash again?

#138

prob just reboot. But you could do a search on the norns help thread for other things to try for the supercollider fail error.

#139

rebooted about 10 times. reflashed 4 times, downloaded the image 2 times. tried updating both automatically, and manually. will have to slog through the help thread to see if there’s any other suggestions.

#140

One suggestion you’ll see a lot in that thread is to log in to your Norns using ssh or screen and try to run sclang. It will probably fail to start, but the output may provide a hint or two about what’s going wrong.

#141

here’s one starting place. Norns: help

As synthetivv suggested, this error is because sclang is not starting properly.

#142
not sure what any of this means..... 
compiling class library...
        Found 716 primitives.
        Compiling directory '/usr/share/SuperCollider/SCClassLibrary'
        Compiling directory '/usr/share/SuperCollider/Extensions'
        Compiling directory '/home/we/.local/share/SuperCollider/Extensions'
        Compiling directory '/home/we/norns/sc/core'
        Compiling directory '/home/we/norns/sc/engines'
        Compiling directory '/home/we/norns/sc/ugens'
        Compiling directory '/home/we/dust'
        numentries = 1049693 / 12504774 = 0.084
        4351 method selectors, 2874 classes
        method table size 7837404 bytes, big table size 50019096
        Number of Symbols 12509
        Byte Code Size 344904
        compiled 373 files in 1.09 seconds

Info: 4 methods are currently overwritten by extensions. To see which, execute:
MethodOverride.printAll

compile done
localhost : setting clientID to 0.
internal : setting clientID to 0.
Class tree inited in 1.1 seconds

-------------------------------------------------
 Crone startup

 OSC rx port: 57120
 OSC tx port: 8888
 server port: 57122
 server port: 9999
--------------------------------------------------



*** Welcome to SuperCollider 3.10.0. *** For help type ctrl-c ctrl-h (Emacs) or :SChelp (vim) or ctrl-U (sced/gedit).
Booting server 'localhost' on address 127.0.0.1:57110.
sc3> Found 0 LADSPA plugins
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Failed to connect to session bus for device reservation: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

Audio device hw:0 cannot be acquired...
Cannot initialize driver
To bypass device reservation via session bus, set JACK_NO_AUDIO_RESERVATION=1 prior to starting jackd.

JackServer::Open failed with -1
Failed to open server
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
could not initialize audio.
terminate called without an active exception
Server 'localhost' exited with exit code 0.
#143

looks like your soundcard is not working or jack isn’t running

did you try the old CM3?

#144

Hooooboy. Will try that shortly when I get home.

#145

Undid all the screws and rebooted it and now it works. Is there a chance something is under tension from the internal screws? Or is it just being weird?

Edit… Uh oh. Just put it back together and rebooted and got the error. Opened it back up and it’s fine again. Some screw is causing an issue. Maybe I should reflow the jacks before closing it back up?

#146

aha. i remember running into this a couple times.

try removing the screen ribbon cable, re-folding it so it’s very tight. is that doesn’t help, slip a small strip of paper between the CM3+ and the pcb under the socket.

the CM3+ is a little taller than the CM3, so something is too tight, pushing the CM3+ down into the board, on top of the codec. i suspect the ribbon cable. let me think of what else it might be— i need to disassemble a unit and inspect.

#147

I reseated everything and screwed it all back together and things seemed to shift less this time and it’s still working. So your scenario also is reassuring. Some more things to mess with if it happens again. Thanks everyone for the input. This was actually a lot easier than all the walk throughs seem to a none programmer.

1 Like
#148

Oh, interesting. CM3+ installation went smoothly for me, but my key 2 feels a little different/stiffer now. Still totally functional, but perhaps this explains things…

#149

you could try opening it up and reseating the screws— pay attention to the alignment of the keys.

1 Like
#150

Another successful CM3+ install thanks to these instructions!

1 Like
#151

EDIT : so i tried using another computer running macos 10.13.6 and it worked. the installation went smoothly. but then when i boot it, i get supercollider fail. tried to reset few times, but still no luck. switching back to the old CM3 and now i also got the supercollider error too. any suggestions?

hi, i want to ask some help. i was trying to upgrade my norns. was following the instruction by mutedial.
i’m stuck at step 3, build rpi step, after i did :

cd usbboot
make

i got an error, " clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [rpiboot] Error 1"

and then when i did sudo “sudo ./rpiboot” i got “command not found”
i’m on mac os 10.12.6, and not really familiar with Terminal. can anybody help?

thanks

46%20PM
46%20PM573×596 53.4 KB

#152

I’ve installed today a CM3+ following these instruction, running macos 10.13.6 and 200106 image. everything work fine.

2 Likes
#153

Dear all,

This is really doable. Especially considering the awesome tutorial.

Regarding the supercollider error. When I rebooted right after flashing I was not getting a supercollider error. It only occured after I enlarged the filesystem. A reset fixed it for now.

In order to prevent a potential short between the module and the parts on the pcb right below I would recommend some insulating material. I just used a small piece of paper. But that just might me being paranoid.

Side note: Enlarging the file system also works by sshing over wifi into the norns. No need to have it connected to the computer when performing this operation. In contrast to using the IP you may use the DNS name (norns.local in my case).

Best,
opty

#154

so…i just updated three norns to a CM3+ 32Gb.

a bit confused with what the easiest way to do this since every option is kinda thrown at you.

on a Mac…easiest procedure i found…

  • backup your norns
  • take apart norns
  • be sure and remove the buttons once open or you will hit the K1 when trying to reassemble and norns will try to boot up!
  • disconect battery (take note of the battery terminal before disconnecting)
  • pop in upgrade
    - download the norns image from GitHub norns-image
    (just click that green button that says CODE and unzip it so its a .img file)
    ((MOD EDIT: this is incorrect and will cause problems. you want to get the latest tested release from the releases page for that project).
  • download and install balenaEtcher
  • connect norns to the Mac like its a big thumb drive using the norns power connection port
  • switch norns to DISK
  • run balenaEtcher and wait for balenaEtcher to see the Compute Module
  • tell the Mac to IGNORE once it sees the drive
  • load the norns image from GitHub into balenaEtcher and click FLASH
  • once it’s done remove from the Mac
    (it should auto-eject after balenaEtcher is done flashing)
  • flip internal norns switch to RUN
  • reassemble norns
  • put norns back in it’s usual living space in your studio and connect power and WiFi nub
  • boot up norns and connect to your WiFi
  • use TERMINAL to SSH into norns and follow the instructions that i found on the norns Shield page:
    (you have to do this to get all that new extra storage)
Summary 
open a terminal on a computer connected to the same network as your shield
execute: ssh we@norns.local
password: sleep
execute: sudo raspi-config
navigate to Advanced and hit RETURN
select expand filesystem and hit RETURN
lots of activity will happen. when it's done, power down and reboot. if you get any errors, reboot again.
if you SSH back into norns and execute df -h, you'll see the newly expanded capacity.

i just copied and pasted all of those commands and everything worked fine.

  • it will ask to shut down norns in Terminal so do that and then go boot up norns again
  • run UPDATE on norns
  • then finally…go to CyberDuck and load all of your noiz and scripts back in!
  • reboot from SLEEP
  • go back into SYSTEM and re-connect all of your devices!
  • get back to making noiz
    :stuck_out_tongue:
6 Likes
#155

Hi there! I’m attempting to install the CM3+ module but I’m already stuck on creating the Norns image from the zip file: norns-image-master.zip. What’s the trick to this on a Mac? I’ve reviewed the guides from @mutedial and @SPIKE with no luck and I’m a bit confused.

#156

I had to unzip the file with a third party app. I used Keka. The Mac unarchiver produced a corrupt image. Also make sure you use the power connection port to connect to computer.