#687

Maybe it’s not actually powered off? If it’s still running you should be able to feel that by touching the CPU.

#688

I could do some HDMI-testing and see if it turns off.

Edit:
tried this, and by using SLEEP the raspberry seems to shut down properly(terminal goes black). The “sleep” text on the display is grey and stays that way until I plug the power adaptor in and out again. No one knows of a smoother way to handle power on/off on the pi?

Maybe something like this? https://www.raspberrypi.org/forums/viewtopic.php?t=188019

#689

I purchased a RasPi specific power supply with a switch so I could power cycle without replugging.

FWIW - I believe SLEEP is doing the equivalent of sudo shutdown now

At which point the system is down but everything (the display) still has power so the screen still shows the sleep text.

Plug in an hdmi monitor when you do sleep and you’ll see hat it’s doing.

1 Like
#690

Smart. But have anyone tried wiring a button to the reset pins on the pi?

#691

Not YET. But this might go in my next pcb revision :smile:

Edit - FYI

Note that the ground pin is no longer next to the RUN pin on 3B+ as it was on older RPi’s.

#692

I’ll see if I can implement this sometime this week, just need to source a button/switch.

#693

managed to make a power “reset” button.

connected soldered pin5 and ground to one side of an ON-ON switch and added the following to /boot/config.txt

dtoverlay=gpio-shutdown

works great as a way to wake my Norns after “sleeping”

#694

which pin5 do you mean? GPIO5 ? (or do you mean the RUN pin?)

#695

GPIO3, aka Pin5 :wink: (did some experiments with the run pin, and did not get the results I was hoping for, no restart triggered for some reason). Sorry about not using GPIO terms, sometimes I think of the pins numbered between 1-40, makes it easier to pinpoint connections by counting.

F73AB51B-7440-4CAE-AF02-F96E333BFC6B.tiff (3.3 MB)

#696

FWIW - I just found this Adafruit tutorial which mentions making a GPIO into a power button (using the built in buttons on the PiTFT hat).

#697

Yup. Tou should in theory be able to modify the gpio-shutdown overlay to use any GPIO. I just ended up using the predefined one since it was unused.

But, as far as I know this does not completely cut the power, it just reboots the software. More info:
https://www.stderr.nl/Blog/Hardware/RaspberryPi/PowerButton.html

#698

Does anyone know if the Pi stores some sort of boot log somewhere? I keep on having irregular issues where I need to unplug the power a couple of times to get it to boot properly when I’ve had it unplugged, and I would love to backtrack where the issue is coming from.

Edit:
So, I managed to get to view a failed boot on an external monitor, and there are a lot of “EXT4-fs error (device mmcblk0p2)“ errors. Did some googling and this might be because of a faulty SD-card. So I’m thinking I need to migrate to a new SD(unless anyone has any other ideas?).

Only thing that worries me is that when I made a norns 1xx image mirrored the SD card size in full, while my norns 2xx image is a lot smaller in size, only about the size of my boot partition. Nothing else.

#699

Hey everyone!
Does anybody tried to use norns with a ssd1306-OLED via I2C. The OLED I’m using does not have SPI-capability (only 4 pins), so I have to use I2C. The problem is, that I don’t know how to use a framebuffer device with I2C instead of SPI.

#700

It should not matter what protocol is being used.

2 things you need

  • i2c enabled in raspi-config
  • a fbtft driver for the ssd1306

I’m not sure if the default stretch kernel has the ssd1306 driver included or not.

1 Like
#701

I’m having some weird issues with buttons/encoders when I connect more stuff than my sound card to the pi, I lose control over 1 encoder if I have more stuff connected, and I get the following error in dmesg:

[    7.418031] pinctrl-bcm2835 3f200000.gpio: pin gpio19 already requested by 3f203000.i2s; cannot claim for soc:knob2
[    7.418042] pinctrl-bcm2835 3f200000.gpio: pin-19 (soc:knob2) status -22
[    7.418050] pinctrl-bcm2835 3f200000.gpio: could not request pin 19 (gpio19) from group gpio19  on device pinctrl-bcm2835
[    7.418055] rotary-encoder soc:knob2: Error applying setting, reverse things back
#702

might need some more details aside from “More Stuff” :stuck_out_tongue_winking_eye:

what’s connected and where?

From those errors it looks like you’ve duplicated a pin assignment.

1 Like
#703

Haha, sorry. Just “stuff” connected to the USB port(nanokontrol, Keystep and Grid)

Edit: Ended up moving some connectors around, as I could not identify why this was happening

The rip-proto overlay, is that something you really need when using a USB-soundcard? Isn’t this a driver for a WM8731 interface?

#704

anybody having problems with there RpiNorns not recognising HID Devices.(keyboard, mouse) not showing up in Devices HID. have no problem recognising midi and grid devices cant test arc as i dont have one? getting this from maiden REPL:-
stack traceback:

/home/we/norns/lua/core/vport.lua:13: in function ‘vport.get_unique_device_name’

/home/we/norns/lua/core/hid.lua:39: in function ‘core/hid.new’

/home/we/norns/lua/core/hid.lua:116: in function </home/we/norns/lua/core/hid.lua:115>

lua: /home/we/norns/lua/core/vport.lua:13: table index is nil

dmesg | grep -i usb shows the HID Devices but norns does not?

cheers :slightly_smiling_face:

#705

I’ll test later with a newer apple magic keyboard. Have you tested with multiple keyboards? And do they work in the Raspbian terminal directly(not ssh).

On a side note:

I’ve done quite a few compiles now with good results but for some reason different USB sound cards have reacted different on different compiles, I used to use an Audient iD4 with my previous compile, because my Scarlett 2i2 was getting noise/crackles on lower buffer rates. But now, with a day old new compile I am using my Scarlett 2i2 again, with a higher output and pretty much noise/crackle - less. Wish I had a good answer why it is like this, but I don’t. Thankfully it works.

#706

tried a usb keyboard, a bluetooth keyboard/ a mouse, an xbox controller. nothing shows up. yes they work at the console level. my usb launchpad is recognised as are my usb midi controllers?