PS: I fixed the Pd pin number in the above table (was 34, it actually is 23)
Pepper: restart/reset/*loop* button
- Edited
giuliomoro Yes i had used 23 already, assumed a typo. Which of the three buttons do i need to hold? Reset, Power or Bela button? - if i hold the Bela button th unit dosn't reach any state that i can ssh into -
EDIT trying jumper wire
the rightmost button on the front panel: I understand that that is the one you have assigned to bela-cape-btn after editing the .service file?
giuliomoro Jumper wire helps. But "/root/Bela/core/PRU.cpp" contains no line for the stopButton. I went through some of the /include files but couldn't find that line either.
- Edited
giuliomoro and yes, the rightmost button on Pepper's front panel. If i could wish for sthg i would love to be able for this button only to fire "next patch" in loop mode, when i have pressd it for a minimum of a second. Just slipping this in while we're at it. Thank you for walking me through.
hmmm maybe you have an oldish version of the codebase. It looked like this before:
if(belaCapeButton.read() == 0){again, make it == 1 instead.
Actually now that I think of it you should probably update your Bela code anyhow, or the whole belaconfig stuff may not work.
giuliomoro You were right, it was "if(stopButton.read()..." - changed value to 1. Have to reattach to Pepper to see what it does, bare with me...
After the stopButton.read change in PRU.cpp IDE starts up, but fails to run, in single patch mode i get this:
Nov 03 17:17:22 bela stdbuf[969]: Button pressed, quitting
Nov 03 17:17:22 bela stdbuf[969]: make: warning: Clock skew detected. Your build may be incomplete.
Nov 03 17:17:22 bela stdbuf[969]: make: Leaving directory '/root/Bela'
Nov 03 17:17:23 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:17:23 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:17:23 bela systemd[1]: bela_startup.service: Start request repeated too quickly.
Nov 03 17:17:23 bela systemd[1]: Failed to start Run Bela at boot.
Nov 03 17:17:23 bela systemd[1]: bela_startup.service: Unit entered failed state.
Nov 03 17:17:23 bela systemd[1]: bela_startup.service: Failed with result 'start-limit-hit'.
Ay. i guess i will return everything to initial state now.
Bela version is v0.3.8b btw
Does it run when you run the project from the IDE?
giuliomoro No, the messages above came from the IDE. It also doesn't matter, if i choose single patch or loop mode. The essage "bela stdbuf[969]: Button pressed, quitting" appears regardless.
yeah but what if you start a program from the IDE? That's the first step we need to get to work before the rest falls into place.In particular, I would like to make sure that PRU.cpp got rebuilt after your changes. You could do rm /root/Bela/build/core/PRU.o before starting a project and that should force a rebuild of PRU.cpp.
I did start from the IDE, too. rm /root/Bela/build/core/PRU.o gives me a "no such file or directory"
and when you start the program from the IDE it should show that it rebuilds PRU.cpp, is that the case?
Okay IDE is single patch mode is doing something
Building PRU.cpp...
...done
Linking...
...done
Enabling Bela at startup in a loop...
project set to run on boot succesfully
Running several different patches then each say
Button pressed, quitting
...done
Enabling Bela at startup in a loop...
Bela stopped
project set to run on boot succesfully
All in IDE.
- Edited
giuliomoro No, none of the projects run (all PD). Upon running them they load and then quit saying
Button pressed, quitting
Bela stopped
EDIT: This also goes for the PD patches in the examples
ok, what is the content of /root/.bela/belaconfig at the moment?
- Edited
Also i have removed PRU.o again (rm /root/Bela/build/core/PRU.o) to force rebuild PRU.cpp, the rebuild happens, but at last
Button pressed, quitting
Bela stopped
appear again
ok, what is the content of /root/.bela/belaconfig at the moment?