#1482

Wow, thank you so much for this detailed reply. Very helpful. <3

1 Like
#1484

Any midi controllers plugged into the USB ports?

#1486

Hi,

I finished a norns shield build tonight and an getting an error on startup.
Build consists of shield 190909 and a raspberry pi 3 b+

After the splash screen the display says “error: SUPERCOLLIDER FAIL”
Menu interface works, wifi connects, just no audio generation

I have tried two norns builds, 200216 and 201202.
I updated 200216 via wifi and also took a fresh copy of 201202 for github. All gave the error.

Other suggestions in the monome help was to retsrt sc in maiden - this was not possible as sc was not connected/connectable in maiden.

Other suggestions in threads here are hardware related - I’ll reflow the board tomorrow evening, but any suggestions of other things to try before reflowing the solder work?

Thanks

#1487

hi there- this was an issue i was having too as of late. strangely enough the 3 button hold gesture > power off seemed to work for me. i recommend perhaps digging around this topic a little bit.

if not aware, by 3 button gesture i mean hold down K1, K2, K3 simultaneously until it navigates you to the menu. (also called ‘vulcan death grip’)

#1488

Howdy! Sounds like hardware. Sometimes I will get a SC fail after an update, a SYSTEM->RESET usually fixes the issue.

If not, start here:

Check for bridged pins on the audio codec first. May be hard to see bridges if there is any flux hanging around so clean it with some high % iso alcohol. Proper light and magnification will make it easy.

Next, check that the crystal is seated properly and there is not too much solder. Sometimes the pads can bridge under the crystal if there is a big solder flow. If so, hit it with some solder wick.

Reflowing the Pi header pin by pin also can clear up issues. Put a tiny bit of pressure from your iron on each pin as you are going to ensure that the joint isn’t cold.

Good luck! Keep us posted :v:

1 Like
#1489

gave up trying to fix my norns shield encoder problem, just put together the spare board I had and plopped it on the same rpi as before. booted it up and am getting “SUPERCOLLIDER FAIL”. tried resetting and updating, but it persists. figured from this other thread maybe this is the problem:

was very nervous soldering that chip with it’s teeny lil legs so I used very little solder, does this probably mean I need to give it some love? just figured I’d ask here first, in case I’m misunderstanding what @tehn is saying…

#1490

Ya give it some love and try to get as close of a view as possible.

Clean it up with some alcohol and take your time. With a soft tweezer touch you can see if any of the pins wiggle a bit and might not be connected.

I would reflow what solder is already on there while applying a bit of top pressure to the pins before adding more solder.

1 Like
#1491

image
image3024×4032 1.62 MB

hmm not a wiggle on it, went over all the pins pushing down and added solder where i could… anything else here look suspect to anyone?

#1492

Next, check that the crystal is seated properly and there is not too much solder. Sometimes the pads can bridge under the crystal if there is a big solder flow. If so, hit it with some solder wick…

It was exactly this. One side of the crystal has big blobs of solder, the other side looked ok but was not making contact with the board.
I removed the crystal, even up the solder and reapplied.

Everything is working well now, thanks for the help

2 Likes
#1493

I had a similar issue, my supercollier fail was related tot eh crystal not being seated correctly. 2 of the 4 pads were soldered well (no wiggle) when I removed it to have a look it was clear only two were soldered

2 Likes
#1494

don’t forget to check the header to the pi as well.

1 Like
#1495

Hard to tell from picture but I would tune up the caps surrounding the codec and take a look at the crystal.

If you hit a brick wall, I am also in LA and would be happy to tune up the board for you. I can also take a look at the one with the encoder issue.

Shoot me a DM if that sounds good :v:

1 Like
#1496

I put together a Shield from scratch. I got all the smd parts down, soldered up the headers, plugged in & am getting nothing on the screen. I’m sure there’s something I’m missing.

So far, I’ve reflowed the all the headers and checked continuity between the screen and the RPI. All good there. I made sure the screen is getting the 3.3v and that’s okay.

Not sure if it helps diagnose, but when I plug in, the RPI’s red LED lights up, green blinks like it’s thinking about something, then settles down to small blinks while red stays lit.

EDIT - Plugged the HDMI into my TV and got the colored splash screen which means boot failure. Okay. I’m using a Samsung 32Gb SD. I’ll try reflashing it next.

#1497

This sounds normal.

Not necessarily. The HDMI output is disabled in the Shield kernel, so you’re not going to get console or anything on a plugged in monitor.

After you boot up, you can try to connect over SSH using Ethernet if you have a computer with that available. That will at least tell you if the system is running and you can run some command line tests like dmesg to see if the display is initializing, etc.

#1498

Not necessarily. The HDMI output is disabled in the Shield kernel, so you’re not going to get console or anything on a plugged in monitor.

Ah. Okay. Understood.

After you boot up, you can try to connect over SSH using Ethernet if you have a computer with that available. That will at least tell you if the system is running and you can run some command line tests like dmesg to see if the display is initializing, etc.

I can connect over SSH with an ethernet cable. I ran dmesg and got a LOT of lines of text. Is there something specific I should be looking for to know if the screen is initializing?

I’m seeing this error a lot: snd_soc_register_card() failed (-517) (although I see that’s my DAC…that wouldn’t keep the screen from working would it?)

#1499

dmesg | grep snd to look for soundcard/DAC related messages - like the one you posted.

working shield output

[ 0.960158] snd-rpi-monome soc:sound: ASoC: CPU DAI (null) not registered - will retry
[ 0.960178] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 1.244416] snd-rpi-monome soc:sound: cs4270-hifi <-> 3f203000.i2s mapping ok
[ 1.246024] #0: snd_rpi_monome

dmesg | grep fb can look for fb/framebuffer related messages.

Good fb messages copied here

[ 0.965735] fbtft_of_value: buswidth = 8
[ 0.965750] fbtft_of_value: debug = 3
[ 0.965761] fbtft_of_value: rotate = 180
[ 0.965773] fbtft_of_value: fps = 20
[ 0.965808] fb_ssd1322 spi0.0: fbtft_gamma_parse_str() str=
[ 0.965822] fb_ssd1322 spi0.0: 1 1 1 1 1 2 2 3 3 4 4 5 5 6 6
[ 0.965880] fb_ssd1322 spi0.0: fbtft_request_one_gpio: ‘reset-gpios’ = GPIO6
[ 0.965908] fb_ssd1322 spi0.0: fbtft_request_one_gpio: ‘dc-gpios’ = GPIO5
[ 0.965947] fb_ssd1322 spi0.0: fbtft_verify_gpios()
[ 0.965960] fb_ssd1322 spi0.0: init_display()
[ 0.965972] fb_ssd1322 spi0.0: fbtft_reset()
[ 1.107704] fb_ssd1322 spi0.0: Display update: 3579 kB/s, fps=0
[ 1.107720] fb_ssd1322 spi0.0: set_gamma()
[ 1.107865] graphics fb0: fb_ssd1322 frame buffer, 128x64, 16 KiB video memory, 8 KiB buffer memory, fps=20, spi0.0 at 16 MHz

not 100% sure if the DAC not working would affect the screen.

Make sure all your solder points for the display are good, along with all the pins on the RasPi header.

#1500

dmesg | grep snd gives me this:

[ 0.969631] snd-rpi-monome soc:sound: ASoC: CPU DAI (null) not registered - will retry
[ 0.969649] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 1.196790] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 1.196809] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 1.253423] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 1.253442] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 1.294918] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 1.294940] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 1.624409] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 1.624429] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.074186] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.074205] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.811793] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.811803] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.812035] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.812040] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.813983] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.813989] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.822160] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.822167] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.851280] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.851287] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.852577] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.852583] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.858631] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.858640] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 2.964267] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 2.964276] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 3.075392] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 3.075403] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 3.082606] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 3.082696] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 3.370732] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 3.370739] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)
[ 3.507636] snd-rpi-monome soc:sound: ASoC: CODEC DAI cs4270-hifi not registered - will retry
[ 3.507645] snd-rpi-monome soc:sound: snd_soc_register_card() failed (-517)

dmesg | grep fb looks like the good fb messages:

[ 0.974578] fbtft_of_value: buswidth = 8
[ 0.974592] fbtft_of_value: debug = 3
[ 0.974602] fbtft_of_value: rotate = 180
[ 0.974612] fbtft_of_value: fps = 20
[ 0.974643] fb_ssd1322 spi0.0: fbtft_gamma_parse_str() str=
[ 0.974655] fb_ssd1322 spi0.0: 1 1 1 1 1 2 2 3 3 4 4 5 5 6 6
[ 0.974703] fb_ssd1322 spi0.0: fbtft_request_one_gpio: ‘reset-gpios’ = GPIO6
[ 0.974727] fb_ssd1322 spi0.0: fbtft_request_one_gpio: ‘dc-gpios’ = GPIO5
[ 0.974761] fb_ssd1322 spi0.0: fbtft_verify_gpios()
[ 0.974773] fb_ssd1322 spi0.0: init_display()
[ 0.974784] fb_ssd1322 spi0.0: fbtft_reset()
[ 1.117683] fb_ssd1322 spi0.0: Display update: 3595 kB/s, fps=0
[ 1.117697] fb_ssd1322 spi0.0: set_gamma()
[ 1.117831] graphics fb0: fb_ssd1322 frame buffer, 128x64, 16 KiB video memory, 8 KiB buffer memory, fps=20, spi0.0 at 16 MHz

I went back over all the headers with a multimeter and then reflowed everything. I’ll check those again.

#1501

Is there a .cpl file available for the norns shield board for ordering smt assembled pcbs?

#1502

Generate it from eagle - it takes about 5 seconds… for a lot of the Chinese fabs eg jlcpcb you can even find scripts that generate the files in the correct format…

#1503

DAC working now. I have the same messages as what you posted.

I’ve reflowed all the headers and still got nothing on screen. I don’t know what I’m missing.

Would it matter if I opted for the white instead of the yellow screen?

One more thing - when I retested continuity between the GPIO and the header for the screen, everything checks out, except pin 18 (which isn’t on the schematic) is connected to ground. The data sheet says

Active LOW Shutdown control pin for boost converter
(pulled HIGH via on-board 15kΩ resistor)
Can be made a No Connect by removing resistor R1

Not entirely sure I understand that, but I’m wondering if it being connected to ground is the problem. Maybe?

EDIT - that was it. I pulled R1 from the screen pcb and I have a screen that works! Now the next bug to squish: Supercollider Fail.