MicroCART Issues:

This page is intended to detail some more general, repeatable issues that the MicroCART team has found in previous years. This forum serves as a way to navigate a solution to these previously found errors, as these are believed to come up again in the future to new MicroCART users or other researchers using our infrastructure.

Git Submodule Issues

Previously when trying to get some portions of the MicroCART infrastructure working, the .gitsubmodules file has had missing modules that prevents a user from being able to grab submodule dependencies for specific aspects of the repo. While our goal is to minimize the need of these artifacts for this very instance, it might be important to know how they work in the case the submodule infrastructure needs to be reimplemented and updated in the future.

First, it is good to familiarize yourself with the working of git submodules. Here is a link that describes the tool in some detail so users can understand how submodules get implemented: https://git-scm.com/book/en/v2/Git-Tools-Submodules

Our .gitmodules file (located at the top of the MicroCART repository is where we link the URLs to our submodules in use. As of now, we are using FreeRTOS, CMSIS, cmock, libdw1000, and unity. As long as long as they are all within the repository correctly, we should not have a need to touch these packages (located in ~/crazyflie-firmware-2021.06/vendor/).

The .gitmodules folder typically looks like this:

In the above example, we are only including submodules paths for the crazyflie_software directory. In our repo, in lots of cases, we also have a crazyflie_software_bigquad directory. This means that there would also need to be equivalent paths designated for the bigquad infrastructure as well.

If we go the ~/vendor/ directory in the bigquad and see that there is no content within the submodule artifact folders, then we will get a message similar to below about the issues of trying to build:

In order to fix this, we just need to add equivalent paths in the .gitmodules file meant for the crazylie_software_bigquad directory. By doing this, we will have proper links to the git submodule artifacts online and we should be able to resolve this issue.

Oracle VirtualBox- Virtualization Disabled within UEFI/BIOS Settings

This issue typically pertains to those trying to use VirtualBox on personal machines. In rare yet possible cases, when a PC goes through the process of a BIOS update, there is a possibility that it will reset or disable hypervisor virtualization settings, causing VirtualBox to throw errors when trying to boot up a VM.