Kubos FAQs and Troubleshooting Tips¶
- FAQs
- How do I contact y’all?
- How do I set up the Kubos SDK?
- How do I check if I’m using the latest version of the Kubos Vagrant image?
- How do I get the latest version of the Kubos Vagrant image?
- How do I check what version of the Kubos SDK I’m running?
- How do I update the Kubos SDK?
- How do I check what my project’s target is?
- How do I see the debug output of my board?
- How do I check what version of Kubos Linux I’m running?
- What’s the default Kubos Linux login?
- Troubleshooting
- Kubos SDK
- The
vagrant up
command just hangs - I’ve tried other steps here, but my Kubos Vagrant image is still behaving weirdly.
- I got some weird errors while running a Kubos CLI command (
kubos build
,kubos target
, etc) - “error: could not install target {target} at * for {target}”
- “error: No module.json file.”
- “error: failed to create link: [Errno 71] Protocol error”
- I can’t build my project. I keep getting “Permission denied” errors
- The
- Interacting with an OBC
- Kubos SDK
FAQs¶
How do I check if I’m using the latest version of the Kubos Vagrant image?¶
From your host machine, issue the vagrant box outdated
command.
How do I get the latest version of the Kubos Vagrant image?¶
From your host machine, issue the vagrant box update
command.
Warning
This will overwrite all files in your existing image
How do I update the Kubos SDK?¶
kubos update --all
How do I check what my project’s target is?¶
kubos target
How do I see the debug output of my board?¶
minicom kubos
How do I check what version of Kubos Linux I’m running?¶
Issue the uname -r
command on the target board to display the kernel information.
The Kubos Linux version will be the n.n.n number after “KubOS”.
uname -r
4.4.23-KubOS-1.0.0
What’s the default Kubos Linux login?¶
kubos/Kubos123
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 got some weird errors while running a Kubos CLI command (kubos build
, kubos target
, etc)¶
Run kubos update -a
to ensure that you’re using the latest version of the Kubos SDK
“error: could not install target {target} at * for {target}”¶
error: could not install target {target} at * for {target}
error: The targets registry does not provide a version of "{target}"
Run kubos link -a
to re-establish the required module links for your project
“error: No module.json file.”¶
error: No module.json file.
error: The current directory does not contain a valid module.
You are not currently in a valid Kubos project directory. Alternatively, your project’s module.json file has somehow gotten deleted.
“error: failed to create link: [Errno 71] Protocol error”¶
You’re trying to create a symlink on a Windows host machine, most likely by trying to initialize a Kubos project in a shared folder.
Windows does not support symlinks, so you cannot build Kubos projects within a shared folder on a Windows machine.
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 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.
I transferred a script, but it won’t run¶
kubos flash
preserves the file permissions of everything you transfer. Check that your file has the appropriate execute
permissions turned on.
Flash Troubleshooting¶
Flashing a file to the board can fail for various reasons. Sometimes simply reattempting the command can correct the problem.
If retrying doesn’t work, here is a list of some of the errors you might
see after running the kubos flash
command and the recovery actions
you can take:
“No compatible FTDI device found”¶
- 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
)
“Transfer Failed: Connection Failed”¶
The SDK was unable to connect to the Kubos Linux target
- 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
) - If this error occurs after the transfer process has started, then the SDK likely lost connection to the board. Verify that the board is still correctly connected and powered and try the flash command again.
“Transfer Failed: Invalid Password”¶
The SDK was unable to log into the Kubos Linux target. Verify that the password is
correctly defined in your config.json file by issuing the kubos config
command.
System appears to have hung¶
- If for some reason file transfer fails, it can take a couple minutes for the connection to time out and return control.
- If you’ve waited a couple minutes and the system still appears hung, please let us know so that we can open a bug report.
My flash failed for some other reason¶
It’s possible that the transfer timed out. Check the build/{target}/flash.log file in your project for more information about why the flash failed.
If you were trying to flash an upgrade file, simply re-enter the kubos flash
command to resume the transfer.