And the latest build of our fork with this fix is here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.146-202607161052_arm64.deb

@RoyAzriel 1.6.4 release is tested on Starling 2 now, go ahead and use that from the link I emailed you.

Hello @royazriel , please take a look at our documentation, which has some testing tips : https://docs.modalai.com/voxl-open-vins-server/

@Eric-Katzfey thanks. before I did sdk reflash I found out the px4 params were somehow corrupted. I have tried to reproduce these values without success. what made it work is taking a similar drawn read the params usign px4-param show -a and writing the to the corrupted one.

@tom said in Latest SDK versions - How to access?: https://storage.googleapis.com/platform-beta-releases/voxl2/voxl2_SDK_1.6.4-beta8.tar.gz Thanks @tom !!!

Hi Kim, There are a couple changes required here that will make this work: 1. Rebuilding Kernel with SPI14 enabled You're going to have to rebuild and flash the kernel with QUP14 enabled as SPI. There is also a directional level shifter on GPIO67 that needs to be set to high in order for SPI on QUP 14 to work. I created this branch for you that should have the kernel changes that you need: feature/voxl2-mini-spi-qup14 (link) In order to actually build and flash the kernel please follow the instructions from our public docs on how to build the kernel https://docs.modalai.com/voxl2-kernel-build-guide/ When building the kernel, after syncing but before building, make sure to go to the cloned meta-voxl2-bsp directory and checkout the branch that I created (feature/voxl2-mini-spi-qup14). Also there is a chance you may need to build a kernel variant depending on your device so also make sure to check this document to see if you have a -2 device which would require building the kernel with the -v var02 flag https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2 2. Configuring Trustzone with Correct QUP I would recommend using the devcfg binary that comes from the `voxl2-mini_SDK_1.0.0.tar.gz. In order to flash devcfg you'll want to run the following command fastboot flash devcfg <path/to/voxl2-mini_SDK_1.0.0/devcfg>/devcfg.mbn You should flash the kernel and devcfg (Trustzone) during the same fastboot session to avoid running into any issues with the device booting. Let me know if you have any additional questions or run into any issues!

@Alex-Kushleyev Thank you so much for your response. It helped a lot.

@Alan_S The voxl-vtx repository is currently private, the source code for both voxl-vtx and voxl-vrx are contained within.

@Alex-Kushleyev Hi Alex, Thank you for the clarification. That makes sense regarding the accel parsing—agreed that a 4 LSB discrepancy on a 20-bit value is negligible compared to in-flight noise, but it’s good to see it will be corrected. Appreciate you taking the time to investigate and confirm. Igor

@ZuraNeb Perfect! Thank you!

@fhaltmayer , unfortunately, we do not have any updates at this time. It looks like we may never release Ubuntu 20.04 for VOXL2 because it is a LOT of work to switch to a new major Ubuntu release and test + maintain everything. Additionally, even Ubuntu 20.04 is already relatively old, so we are trying to focus our efforts on more forward-looking software development with larger impact. Alex

@bendraper Hello, I hope this quick clarification helps for warnings: CMake Policy warnings: OV internally (external dir in the repo) still uses boost and references an older cmake version -- it's a harmless warning for devs (as you are building from scratch) Yaml-cpp lib warnings: This is a third party dependency that gets compiled from scratch during the make/build process. We use C++ 17 but the library is based on an older C++ version; nevertheless, it compiles fine on C++ 17 with minor warnings. -- it's a harmless warning TrackOCL warning: ModalFlow is a core library written in C++ 17 that allows function call usage as done in TrackOCL, i.e., the narrowing conversion is harmless in this case. That being said, we are actively working on the dev branch, so all flight--impacting warnings are hopefully caught early. We currently have no flight-impacting warnings/bugs identified, but if you found one warning/bug that caught your attention, please feel free to share. All the best, ZBFT

@Andrew-Jong , we are able to reproduce the error that you are seeing. I believe that you may need to set up a virtual display in order to get this to work. You could try doing so using Weston compositor, which would normally run if the display was available. Please try it and let us know if you are able to get it to work (or not). You would need to create a config file /etc/xdg/weston/weston.ini and try running it manually like this : weston --idle-time=0 --config=/etc/xdg/weston/weston.ini a sample config file might look something like this: # configuration file for Weston [core] idle-time=0 repaint-window=15 [output] name=virtual-1 mode=on We have not tested this yet, but hopefully it's a good start. Alex

@Alex-Kushleyev Found the reason why it was skipping. In /px4-firmware/src/lib/parameters/CMakeLists.txt there is a line that skips all modules that match 'pwm_out'. I was able to disable that for PCA9685. Once I disabled the module.yaml file being skipped it worked. No need for the .c file (which makes sense, that is just the old way to do the .yaml)

@brandon You'll need to load SDK v1.6.x to get it.

@Samuel-Lehman If you have the original adapter for Boson+ which allows you to connect it to a USB port, then you can use the FLIR SDK (we use Boson Plus SDK 4.0). Unfortunately, M0153 board does not have J3 connector populated, which would allow you to connect a serial-to-usb adapter to it. We have several python scripts, which use the Boson SDK to help set up the Boson sensor without the GUI. query basic sensor info: https://storage.googleapis.com/modalai_public/temp/boson/boson_read.py set up sensor for 8bit MIPI mode, 60fps (option to set 30fps): https://storage.googleapis.com/modalai_public/temp/boson/boson_set_8bit.py You can put both of these scripts next to the BosonSDK directory and run them. Please check the USB port name inside the scripts. Once you get that configured, you can put M0153 back on boson. Regarding where to plug it in on Voxl2, please tell me what other cameras you plan to use with your Boson. Alex