If you click on your Hard Drive icon on your desktop -> Users -> You will see a home folder icon (maybe your name) - that’s the root folder - click on that and put the file in there. There should also be a folder in there called “usbboot” which you need to have when you first connect from computer to norns

1 Like

yes! Thanks I did it! :slight_smile: now I need to expand the drive

Were any full package installation instructions posted on windows os for the CM3+?
I was able to download the image file and get through the rpi boot successfully but am not sure how to proceed…
Has anyone had success getting everything running from just windows?

following on from this post Norns: CM3+ installation and successfully tar / expanding the image file and completing adding home-brew and all the macros

I did the following as per below, but my Norns won’t boot after installing the img file

i installed the CM3+

i used tweezers to unscrew the bolts

run rpiboot

plug norns in to mac

a got a successful rpi boot like described :

Waiting for BCM2835/6/7
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7
Second stage boot server
File read: start.elf
Second stage boot server done

identify disk - done -

this was disk4 on my machine

copy img to disk

this took around 20 minutes and was successful judging by the messages

i flipped the switch back to run.
When i press button 1 to start, the light next to usb comes on but immediately goes out when i release the button - like no power, even when the power is connected back. With no power attached it does the same thing. It looks like its bricked although i can easily switch back to disc mode and get access again via rpiboot

i repeated the same procedure with identical results and Norns won’t boot up.

All i can think of is the img file is corrupted when expanded or my CM3+ is not working although it does read and does show that the file loaded up on there.

Any ideas? Pretty sure the CM3+ was installed good.
I am going to try redownloading the image file again.

Update - i downloaded the image file again and uncompressed it via tar and the terminal window. Still no go - I get the same results after transferring the img file

1 Like

I don’t have a better idea than trying again with a fresh download of the image. Maybe just get the compressed file and decompress it via terminal? Not sure it could make a difference but that is what worked for me.

1 Like

i redownloaded the image file again and uncompressed it via tar and the terminal window. I transferred the img file but still Norns won’t boot up. The power light comes on when I press and hold button 1 (with and without the battery/mains power), but the screen remains blank and the light goes off immediately after releasing the button. I am pretty sure the CM3+ is installed correctly and it does register (on my Mac) that the transfer of the img file was successful. It just won’t boot up after flipping the switch back to run.

i have just done the cm3+ upgrade, but using windows 7. The norns image was flashed successfully and able to boot up status. Have yet to check more in depth

For now, these are some observation made along the way.

  1. Rpiboot when installed, there’s a missing driver, bcm 2710 boot.
  2. With norns connnected to computer, check within device manager, there will be 2 driver needing updating, bcm 2710 is one, the other is bluetooth peripheral(have no idea bout this yet)
  3. Need to manually update the bcm2710 driver, more info here, https://www.raspberrypi.org/forums/viewtopic.php?t=180222
  4. Once bcm driver sort out (might need to try with different cable, different usb port etc), run rpiboot with norns connected, there will be pop up window with messages to indicate the process being successful or unable to detect device etc.
  5. With cm3+ recognised, the familiar, additional drive icon will appear and needing formatting.
  6. Formatting done, next will be flashing the norns image. Norns image file is in the Norn2.0 thread and flashing info over here, for windows, https://www.raspberrypi.org/documentation/installation/installing-images/windows.md

On the norn image file, i went thru several times with failed attempts after flashing(norns cant boot up) to realise on having to stripped the image file down (with 7zip on wndows) to .img format and not the tar or tgz state.

the uncompressed .img file is around 3.8gb + size, so flashing with win32 disk imager will take a while.

Above are what i have tried so far on windows and hope it be useful in some ways

3 Likes

Very helpful thanks - still waiting to receive my CM3+ 32gb. Have a suitable Win7 standing by.

This is interesting because I’ve been using tar and maybe that is my issue with mine not working. I will try to uncompress using a different method.

I had same issue when i’ve didnt unmount disk before writing image, dont forget to use sudo diskutil unmountDisk /dev/disk4

2 Likes

How long did flashing take for you? I think it should take around 20 minutes.

1 Like

Thanks, yes I did I unmount each time before writing - you can see in the photo in my previous post. I just followed these instructions

Yes it took a long time @20 minutes each time and each time the message showed it had transferred 100% of the img data

Which image are you downloading/using?

The picture says 190405.

1 Like

Yes 1900405 - the full image that Tehn posted for CM3+ , not the beta.

I thought it was maybe something to do with uncompressing it with the tar command.

I don’t know if this is related but I did upgrade my Mac to Mojave prior to doing alll this. I installed all the recommended files Homebrew etc.

Hi, it is weird as your set up sounds like mine. I am on 10.14.4 as well, I installed Homebrew, Wget and followed these instructions: https://github.com/monome/norns/wiki/img-flash-macos but downloaded the tgz file, after the download ran “tar xzvf 1900405.tgz” to get the image. I had some connectivity issues during rpiboot and had to hit the reset button to get further and reconnect. Apart from that every step you describe and what I can see from your screen is actually the same process as mine… maybe @tehn has an idea. Fingers crossed.

1 Like

@mlogger try switching back to your original CM3, boot it up. make sure that works. give the RUN/BOOT switch a good jiggle back and forth to make sure the contacts are working (random guess here).

1 Like

I switched back to the original CM3 and it boots fine and Norns works. Switched back to the CM3+ again and its not booting. The RUN/BOOT switch is fine and stable - the light goes on and off as normal when you switch between RUN/BOOT (no flickering or anything looking unstable). Maybe my CM3+ is bad? It does read and register everything as uploaded in RPIboot on my Mac though. It reads that CM3+ disk. I am still wondering whether something is wrong with expanding that IMG file or downloading of the original tgz. Before uncompressed the .tgz file is 1.17 GB. After tar in the terminal it is 3.91 GB.

I also uncompressed with Archive Utility one time with the same GB numbers reported. I transferred this image file but still no boot up.

I had success using ‘etcher’ to burn the image. I believe that it is available on windows/Mac/Linux.
I had to restart and switch between run and disc a few times before everything booted.
Also I used a previous image file and then went through the normal update process once the image was running and Norns was able to boot.
I can try and recount my steps if it would be helpful. I am on windows 10 btw.

1 Like