• General

  • bela ide won't boot after plugging in bela mini

OK, it's on en17 but for some reason it's not picking up the address. Is there a program running on Bela that takes up a lot of CPU? You may have to kill that in order to get access to the IDE. See: https://learn.bela.io/using-bela/about-bela/troubleshooting-guide/#program-running-at-boot-and-board-not-showing-up

After you stopped the program (if any), something like sudo ipconfig set en17 dhcp should fix that. If that doesn't, then try sudo ifconfig en17 up 192.168.7.1. There is no need to run ide.sh as the IDE is already running on the board unless you disabled it via this script in the past.

    giuliomoro Would there be something running even if it's starting up from off state? I have not configured the bela to run a project from boot and to my knowledge I have not configured it to run other programs.

    I've tried all the things on that page except for grounding the clock lines. Using the bela button and runnnig that ssh -o StrictHostKeyChecking=no -o ConnectTimeout=1200 root@192.168.7.2 make -C Bela stop nostartup command both seem to successfully turn off the unit.

    I tried running those ifconfig and ipconfig commands from my local computer and they completed without error but the ide still does not load.

        nickcamillo . Using the bela button and runnnig that ssh -o StrictHostKeyChecking=no -o ConnectTimeout=1200 root@192.168.7.2 make -C Bela stop nostartup command both seem to successfully turn off the unit.

        yeah that was not the plan, but if you have no program running on boot, then there should be no need to run any of this. Is the LED on the BelaMini cape also blinking?

        Have you tried connecting to bela.local in the browser or ssh root@bela.local from a terminal?

            giuliomoro bela.local in the browser does not work but I am able to get in via ssh after a longer period of time than I am used to.

              I am able to run make -C ~/Bela/ PROJECT=looper-oleds run CL="-p16" from the unit via ssh and get my project to run successfully, I just can't access the ide.

              hmm when you are on the board run make -C /root/Bela idestartup idestart, wait a few seconds and try loading it again in the browser.

              also make sure ifconfig en17 on your computer gives you 192.168.7.1 , or use the ifconfig/ipconfig methods above to make it do so. Btw, what version of macos have you got?

              it appeared to run successfully:

              make -C /root/Bela idestartup idestart
make: Entering directory '/root/Bela'
Enabling the IDE at startup
Starting IDE...done
make: Leaving directory '/root/Bela'

              and ifconfig looks right to me?

              ifconfig en17
en17: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether be:1a:98:ae:69:50
	inet6 fe80::10d1:6558:4e5d:e84f%en17 prefixlen 64 secured scopeid 0x18
	inet 192.168.7.1 netmask 0xffffff00 broadcast 192.168.7.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active

              but still no dice. I'm running 13.0 (22A380)

              that all looks fine. Do a reboot, get on the board and run

              journalctl --boot -fu bela_ide -n 3000

              and see if that tells you something about what's wrong with the IDE.

              still doesn't load. Is port 80 right?

              journalctl --boot -fu bela_ide -n 3000

-- Logs begin at Thu 2016-11-03 17:16:43 UTC. --
Mar 17 00:21:21 bela systemd[1]: Started Bela IDE Launcher.
Mar 17 00:21:34 bela node[437]: starting IDE from /root/Bela/
Mar 17 00:21:35 bela node[437]: setting pwd timeout
Mar 17 00:21:35 bela node[437]: listening on port 80

              running out of ideas ...
              what do you get running curl 192.168.7.2 from you host?

                here's some new info, I just tried to git clone the c language server while ssh'd and it seems I no longer have access to the internet on the unit:

                git clone --depth=1 --recursive https://github.com/MaskRay/ccls
Cloning into 'ccls'...
fatal: unable to access 'https://github.com/MaskRay/ccls/': Could not resolve host: github.com

                this is what my /etc/network/interfaces file looks like:

                1 # This file describes the network interfaces available on your system
  2 # and how to activate them. For more information, see interfaces(5).
  3
  4 # USB RNDIS gadget (Windows / Linux compatible)
  5 auto usb0
  6 iface usb0 inet dhcp
  7
  8 # iface usb0 inet static
  9 #     address 192.168.6.2
 10 #     netmask 255.255.255.0
 11 #     network 192.168.6.0
 12
 13 #�[m+USB NCM gadget (macOS / Linux compatible)
 14 auto usb1
 15 iface usb1 inet dhcp
 16 # iface usb1 inet static
 17 #     address 192.168.7.2
 18 #     netmask 255.255.255.0
 19 #     network 192.168.7.0
 20
 21 # The loopback network interface
 22 auto lo
 23 iface lo inet loopback
 24
 25 # Ethernet
 26 allow-hotplug eth0
 27 iface eth0 inet dhcp
 28 # Example to keep MAC address between reboots
 29 #hwaddress ether DE:AD:BE:EF:CA:FE
 30
 31 # WiFi Example
 32 allow-hotplug wlan0
 33 iface wlan0 inet dhcp
 34 wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
 35 # The lines above should work if you have a wifi interface called wlan0.
 36 # To see the actual name of your interface, run
 37 #   ip a
 38 # and identify it among the ones listed then replace `wlan0` above with the name of your interface
 39 # To provide credentials to your network, run the following at the command line:
 40 #    wpa_passphrase YourNetworkName YourNetworkPassword >>/etc/wpa_supplicant/wpa_supplicant.conf
 41 # then:
 42 #     ifdown wlan0; ifup wlan0
 43 # where `wlan0` is the name of your interface as found above.
 44

                This was working before

                giuliomoro

                curl 192.168.7.2
curl: (7) Failed to connect to 192.168.7.2 port 80 after 75015 ms: Network is unreachable

                  I'm also seeing errors when I use some basic terminal commands:

                  ls

channel 16: open failed: administratively prohibited: open failed
channel 16: open failed: administratively prohibited: open failed

                    If you have network sharing enabled for the board, then 192.168.7.2 should no longer work and you shouldn't try to force it with ifconfig/ipconfig. Rather, see if you can re-enable internet sharing from the host.

                    nickcamillo I'm also seeing errors when I use some basic terminal commands:

                    ls

                    channel 16: open failed: administratively prohibited: open failed
                    channel 16: open failed: administratively

                    This I've never seen. Are you out of space?

                        giuliomoro I don't see why I would be. I've got a few megabytes of audio recorded and I've built the latest vim from source but that's about it. Does this seem reasonable?

                        df -H
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.6G  2.7G  710M  80% /
devtmpfs        256M     0  256M   0% /dev
tmpfs           256M     0  256M   0% /dev/shm
tmpfs           256M  9.7M  246M   4% /run
tmpfs           5.3M  4.1k  5.3M   1% /run/lock
tmpfs           256M     0  256M   0% /sys/fs/cgroup
/dev/mmcblk1p1   71M  4.3M   67M   7% /mnt/boot

                        As far as my mac is concerned, the bela has internet sharing enabled. I disabled and re-enabled it but I still can't git clone from ssh and the ide still wont load.

                          giuliomoro

                          ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether f4:b8:98:ae:69:4c brd ff:ff:ff:ff:ff:ff
3: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether be:1a:98:ae:69:4e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::bc1a:98ff:feae:694e/64 scope link
       valid_lft forever preferred_lft forever
4: usb1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether be:1a:98:ae:69:51 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::bc1a:98ff:feae:6951/64 scope link
       valid_lft forever preferred_lft forever

                            Hmm it doesn't have an IPv4 on usb1. On the board try:

                            echo > /var/lib/dhcp/dhclient.leases
dhclient usb1

                            possibly followed by a stop-sharing/start-sharing on the host.