Kubos FAQs and Troubleshooting Tips¶

We keep the KubOS repo locked to specific Rust version. When this version changes you will need to update your local Rust version. You can do so by looking at the Rust version that KubOS is locked to (found here) and using that version number in the following commands.

Updating the native Rust toolchain:

$ rustup toolchain install 1.xx.y-x86_64-unknown-linux-gnu

Updating the Rust cross compiler targets:

$ rustup target add armv5te-unknown-linux-gnueabi --toolchain 1.xx.y
$ rustup target add arm-unknown-linux-gnueabihf --toolchain 1.xx.y

Troubleshooting ¶

Kubos SDK ¶

The `vagrant up` command just hangs ¶

If you’re using Windows 7 SP1, make sure you are using the correct version of Windows PowerShell.

I’ve tried other steps here, but my Kubos Vagrant image is still behaving weirdly.¶

Try logging out and restarting the VM using the vagrant reload command.

I can’t build my project. I keep getting “Permission denied” errors ¶

If you copied your project from another location, it’s possible that the files are set up with root permissions only. Change the project file permissions to allow the local vagrant user to have access.

sudo chown vagrant:vagrant . -R

Interacting with an OBC ¶

Can’t Connect via Serial Debug ¶

If the SDK was unable to connect to the Kubos Linux target using minicom kubos:

Check that the Kubos Linux target is turned on and connected to your computer
Check that no other Vagrant images are running. Only one VM can have control of the USB, so it may be that another instance currently has control of the device. You can shutdown a Vagrant image with the command vagrant halt
Verify that the USB is showing up within the Vagrant environment with the lsusb command. You should see an FTDI device
Verify that the USB has been mapped to a linux device. Issue the command ls /dev. You should see a /dev/ttyUSB* device. If you don’t, try rebooting your Vagrant image (vagrant halt, vagrant up)

Can’t Connect via SSH ¶

Log in to the board via the debug UART and verify the IP address matches what is expected with ipaddr.

For more information, check out our documentation about ethernet connections.

System Won’t Boot into Linux ¶

If the system goes through the full recovery process and the bootcount is still exceeded, it will present the U-Boot CLI instead of attempting to boot into Kubos Linux again.

If this occurs, follow the instructions for resetting the boot environment.

Note: This is a case which normal users should never encounter, but becomes more likely when initially testing custom Kubos Linux builds.

The OBC is Booting from the eMMC Instead of the microSD when Upgrading ¶

If you see errors, or the OBC seems to be booting from the eMMC instead of the microSD, make sure your microSD is being read correctly by running ls mcc 0:1 at the U-Boot prompt. You should see the boot partition files listed (kernel, {board}.dtb, etc). If you are presented with errors, check that the microSD card is seated properly in the SD card slot.

I transferred a script, but it won’t run ¶

scp does not preserve file modes by default, however scp -p should preserve the execute bit. Check that your file has the appropriate execute permissions turned on.