#7

Yeah, that’s what the physical installation looked like. Good to know that’s clear cut, but I suppose the image changes is what’s going to take most of the work.

#8

This was posted in response to early questions… Doesn’t look too hard.

2 Likes
#9

It seems like we’ll need to update the kernel to support the CM3+ https://github.com/raspberrypi/noobs/issues/529#issuecomment-464647944
Note this is just 1 report from a third party, but it’s the only relevant thing I’ve found so far.

Since there’s a whole lot that still needs to happen for the next norns update I don’t expect there will be a lot of time available to work on getting the CM3+ to work so it might take a bit of time till we know if/what will work.

4 Likes
#10

sure, flashing the image is not too hard. building the kernel is not too hard. fixing the kernel… we are not sure yet

4 Likes
#11

took me forever, but i did get my CM3+ running with the official 2.0 firmware, and it is truly awesome.

what i wonder is how do i know if norns is recognizing the full 32gb on the CM3+?

its saying DISK 1592 M…

image
24EBD13F-3166-41A9-B73B-8E54DA47321D.jpeg1242×2208 438 KB

1 Like
#12

you may need to do this ?

du -ch on shell can show current usage
df -h / show capacity

#13

i know you said you haven’t done this, but would this require a re-flashing?

#14

thats a negative overnout

5 Likes
#15

that worked wonderfully! thanks!!!

1 Like
#16

So for CM3+ing, I can just update to 2.0, as per the normal instructions and then do the expand disk thing?

I don’t need to wait until a posted disk image if I haven’t done any of the betas?

#18

You’ll need to flash something to the CM3+ first. Have you already done so?
Only the 190314 beta and the 2.0 images support the CM3+

#19

Nope, it’s a virgin CM3+, hence the question(s).

So I need to wait for the 2.0 image first?

#20

Yep. You absolutely need to do that, if you haven’t done it on the beta yet.

2 Likes
#21

@Rodrigo I just used one of the older images, from the beta thread, and updated as per usual after.

3 Likes
#22

Yeah, there’s nothing on a CM when it comes out of the factory so no way to run it :slight_smile:
The only way to get an OS on it is via rpiboot and an image.
So yeah, you’ll have to wait for the image. I assume @tehn will upload it soon.

Alternatively if you’re feeling adventurous you could start with the 190314 beta image and update from there.

4 Likes
#23

disk image will be uploaded tomorrow (sunday!)

8 Likes
#24

Hopefully my CM3+ will arrive shortly. Couple of questions:-
a) Is there a Windows (10) equivalent of https://github.com/monome/norns/wiki/img-flash-macos - in which case I’ll use that
b) But I do have an old MacBook with Mavericks that I can dig out - would that work - or just too old now?
This machine according to the blurb will take Yosemite / El Capitan but no later if that helps.

#25

see the official docs:

1 Like
#26

I’m attempting the CM3+ install right now.

Module is installed and Norns is in Disk Mode (light on the back is lit up white when in Disk Mode).

I ran the RPI Boot commands and my terminal screen says “Waiting for BCM2835/6/7”

But when I plug the Norns into my computer nothing seems to be happening.

Any thoughts?

Norns 2.0.0
#27

Are you using macOS, Windows, Linux? Are you using a prebuilt copy of rpiboot or did you compile it yourself?

I’ve found the process to occasionally be flakey on macOS. I’d recommend disconnecting norns + USB cable from your computer, killing rpiboot, double checking that the switch is all the way over in disk mode, and then:

  1. run rpiboot (norns disconnected)
  2. plug the USB cable into norns, then into your computer (trying a different USB port than you previously used)
  3. cross fingers

Some times it works for me the first time, other times I have to try 2-3 times. Eventually rpiboot will spit out something like the following:

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

(As seen in macOS instructions linked in the top post).

UPDATE: I should add that I have found the latest version of rpiboot (compiled from source) fairly reliable with macOS Mojave

3 Likes