Troubleshooting

This material has been superseded. Visit learn.bela.io for the maintained version.

At the moment, not much more than just a note of what we need to provide troubleshooting instructions for.

Speaker does not work

Check that your BeagleBone Black is powered with an external 5V power supply through the barrel cable.
Check that the mute-speaker command-line flag is set to 0 (e.g.: -M 0).

File changes not reflected in the program

Sometimes file changes may not be reflected in the program when you build and run it. This is probably due to the Makefile not recompiling that particular file. For this reason, when your changes to a file are not applied to the program, you probably also have suspiciously fast building times, as the file is not re-compiled, it is only (if at all) re-linked. Two are the most frequent causes for this:

Header files Changing the content of a header file (.h, .hpp, .hh) does not trigger a new build of the .c, .cc or .cpp file(s) that includes the header.
Solution: if you edited a header file, you will have to "touch" (as in: do and undo a change) all the files that include that header file in order for the change to be propagated.
This is a known issue and we are working towards fixing it. See here for more details https://github.com/BelaPlatform/Bela/issues/10
All files If you are editing a file that is not a header file and you are experiencing the above mentioned issues, then this is probably because something strange happened at some point with the date on your board.
Solution: clean your project. This can be done from the IDE or the Bela scripts.
See here for more details on how the date works on Bela.

No rule to make target

While compiling your project you get the error "No rule to make target". This may happen when you remove a source file from your project and the old object file is still in the build/ folder. Solution: clean your project. This can be done from the IDE or the Bela scripts.

IDE does not show up

If you open a browser tab to the IP address of your board and the IDE does not show up, then try the following:

check IP address is correct. This defaults to 192.168.7.2 but may be different for your configuration.
If the above does not work, then maybe the IDE is disabled or has crashed. Try first to reboot the board: remove the power for a few seconds and then re-apply it. Wait about 30 seconds and then try again to reach the IDE.
If the above does not work, then the IDE may have been disabled at boot. You will need to reach for the Bela scripts and use a terminal to browse to the scripts/ folder and run the following command:
$./ide.sh start Within 10 seconds, the IDE should be up and running at the board's IP address.
If the above does not work, then you may want to try to reset the board, updating it with the latest code. See here for details on how to do it.

When using `build_pd_heavy.sh` you get a warning from Python of the type

InsecurePlatformWarning: A true SSLContext object is not available.

This would be caused by the lack of some optional python packages. It can be fixed with

# pip install requests[security]

(see here for more info)

The command above may fail with

ImportError: cannot import name IncompleteRead

This is likely because your version of pip is too old (as it is the case in Ubuntu 14.04 LTS). To fix this you will have to remove the current version of pip and install a more up-to-date version. See here for more info.