#1372

used this command and it seemed to work after:

sudo resize2fs /dev/mmcblk0p2

:wink:

#1373

There’s also supposed to be a step about resizing the partition?

See here for details:
https://elinux.org/RPi_Resize_Flash_Partitions
(Scroll down to bottom - last section)

#1374

FWIW - I did a few tests and this does work if done after the raspi-config resize.

so… I suggest this for the moment

Start with a fresh flash of SD card and then do the following from the command line (via SSH).

sudo raspi-config --expand-rootfs
sudo resize2fs /dev/mmcblk0p2

Ignore the warning to reboot after the --expand-rootfs command. The resize2fs will take a minute or two to run. Wait for it.

#1375

Question for the ones with experience:
Is a heat sink actually necessary for the rPi4 or will it be fine without?

#1376

Is there any ETA on when potentially the source files for the boards will be available? I would love to see how these sorts of boards are made to further my PCB knowledge .
I hope this does not come across as rude. Being thankful :slight_smile:

#1377

Hello,

I posting this here since it’s a Fates hardware related issue, please let me know if it belongs somewhere else.

So, I’m having trouble connecting to my Fates via tty, basically, as described here: Norns: help

is you get a bell, please tell us what OS and version you’re using (as this means your FTDI driver isn’t working)

I’m unable to connect and the command doesnt autocomplete when tabbing as described in the sentence, I bought a brand new cable, but that didn’t help, I also installed some FTDI drivers I found online and serialosc just in case, but nothing seems to be working, any tip would be appreciated.

I’m running MacOS High Sierra 10.13.6

#1378

i’ve been fine without, haven’t hit 70 degrees yet.

1 Like
#1379

Good to hear!
20 characters…

#1380

What about RAM? Is 1GB enough? Is 2 the minimum? Does 4 even make sense?

#1381

both fates and the shield do not support this functionality. you’ll need to ssh via wifi.

1 Like
#1382

As mentioned, the tty connection (over USB) thing is only on OG norns hardware. You should not need to mess with FTDI drivers at all.

Connection options for Fates:

FWIW - I’ve only tested using the UART once so I think it works, but your mileage may vary. :grin:.

#1383

Actually, the board files for Fates are not going to be released as open source. I don’t have time to go into detail here now. If you have questions please message me directly.

Your best bet is to examine the Monome Shield which has full source files available

1 Like
#1384

Hi @okyeron and @tehn that explains my troubles, I had the memory of connecting once but it was probably ssh.

thank you both for your answers :smile:

#1385

Great project! Thanks okyeron,

Question 1: Has anyone tried encoders with detent? Still 24ppm? (searched, couldn’t find any examples). If so, did it work well, and feel okay?

Question 2: Is there any simple solution for a larger display (for those who have troubles with the small screen). I want to set up a Fates for a friend who has vision challenges. External LCD, or some such?

Thanks!

#1386

I’ve never tried with detent encoders.

See here for making those work.

Not really anything simple. The board is pretty specifically wired for that Newhaven display. To replace it you’d need to find a similar but larger SPI display and manually rewire things. Then a bit of mucking about with linux settings, maybe drivers, etc. Messy.

You could try to use HDMI out from the pi, but I don’t know specific settings to make that work well. On a pi4 HDMI will take over the norns display output. So you could try starting there perhaps?

EDIT - you could also look at the “official Raspberry Pi 7” touch display" – it uses the direct display ribbon connector and leaves the GPIO pins free, so it could work. But youd still need to do some hacking to get the framebuffer to display in the right place.

#1387

My understanding that detent encoders will register multiple pulses (4?) per “click”, and this may make fine adjustments hard in some scripts.

#1388

No problem , thanks for letting me know :slight_smile:

#1389

So far so good, tends to stay around 67/68C

1 Like
#1390

Good. I’ll go ahead without a heat sink then.

#1391

So, hello again, I’m back on this connecting topic.

I managed to connect via wifi to my phone’s hotspot (useless) but not the regular wifi 4g network, ethernet cable works perfectly. My particular scenario is I have a very long (and tedious to type in) 33 character password for my network, so I wonder, is that an issue when saving/connecting to networks on the norns/fates/rpi?

On the other hand, if there is a way to add the network manually when logged in via ssh to a file (I tried wpa_supplicant without any luck) that would be ideal.

Otherwise worst case scenario I could update the password for my wifi and reconnect all the other devices at home by hand, in which case it would be good to know if there is any length/character limitation for the network name and password (I know strange characters didn’t work for my organelle).

cheers