When integrating the precompiled BMV080 SDK on a SAMD21-based system, RAM usage increases to ~94% of available SRAM.
Since the SDK is not source-available, I cannot reduce internal buffers or disable features.
My questions are:
Is there a minimal or sensor-only version of the BMV080 SDK with reduced SRAM usage?
Are there any configuration options to disable debug/logging, history buffers, or optional processing modules?
Any guidance on reducing RAM footprint or a recommended minimal configuration would be greatly appreciated.
SDK version: v11.2.0
Hardware: SparkFun SEN-26554
Chip ID (0x0079)
Can you possibly confirm whether this hardware revision is supported and whether a newer SDK build is available?
Dear Sensortec Team,
we use BMI270 for our mini drones in series production. From a recent batch however, a few drones (around 5%) show weird flight behavior. After inspecting the flight log, we figure out that the Z-axis gyro signal of the "faulty" drones has significant DC bias and higher noise content in comparison to the "healthy" drones, which led to deviations in yaw estimation.
We are aware that mechanical strain on the IMU can lead to abnormal gyro sensing. The layout of the PCB has been designed following this guideline "https://www.bosch-sensortec.com/media/boschsensortec/downloads/handling_soldering_mounting_instructions/bst-mis-hs000.pdf" (e.g. off-center of strain line, no vias under the chip). Also soldering process was configured according to it.
Any idea about what can be the reason? Is there any extra advice that we should pay attention to?
Please let me know if you need more context.
Thanks,
Min
Hi there,
We're a startup from Munich that built a platform for assembling AI solutions out of reusable building blocks, such as IO connector blocks, model inference blocks, rules, tracking or denoising algorithms, etc.
Once you train your model with AI studio, the next bottleneck becomes how to use it to build different applications. This is where we come in.
Anyone interested in collaboration to add connector blocks for your sensors and inference blocks to be able to assemble solutions fast?
Please reach out and share any technical contact we should talk to. Happy to organize a short call to showcase a live demo.
Thank you! -- Iki
Dear Team,
I have successfully built the sample SDK example from BHI360_SDK_1.1.18.2_rc7 and generated the firmware image.
I would like to understand the expected functionality of this firmware. Specifically, could you please clarify:
What is the intended purpose of this sample application?
What sensor features or algorithms are enabled in this build?
What output data should I expect after flashing this firmware onto a BHI360 Shuttle Board?
Are there any specific host commands or interfaces required to observe the expected output?
Is the output available through I2C, UART, or another communication interface?
For my setup, I am not using the Application Board. Instead, I am using a custom board and transferring the firmware to the BHI360 device over I2C. I would like to verify whether any additional configuration is required and what behaviour or output I should expect after the firmware is loaded.
Any documentation or guidance regarding the functionality of this sample firmware would be greatly appreciated.
Thank you for your support.
When integrating the precompiled BMV080 SDK on a SAMD21-based system, RAM usage increases to ~94% of available SRAM.
Since the SDK is not source-available, I cannot reduce internal buffers or disable features.
My questions are:
Is there a minimal or sensor-only version of the BMV080 SDK with reduced SRAM usage?
Are there any configuration options to disable debug/logging, history buffers, or optional processing modules?
Any guidance on reducing RAM footprint or a recommended minimal configuration would be greatly appreciated.
Dear Team,
I have successfully built the sample SDK example from BHI360_SDK_1.1.18.2_rc7 and generated the firmware image.
I would like to understand the expected functionality of this firmware. Specifically, could you please clarify:
What is the intended purpose of this sample application?
What sensor features or algorithms are enabled in this build?
What output data should I expect after flashing this firmware onto a BHI360 Shuttle Board?
Are there any specific host commands or interfaces required to observe the expected output?
Is the output available through I2C, UART, or another communication interface?
For my setup, I am not using the Application Board. Instead, I am using a custom board and transferring the firmware to the BHI360 device over I2C. I would like to verify whether any additional configuration is required and what behaviour or output I should expect after the firmware is loaded.
Any documentation or guidance regarding the functionality of this sample firmware would be greatly appreciated.
Thank you for your support.
Hello,
I recently ordered the Shuttleboard 3.0 and the Application Board 3.1, but I am unable to retrieve any data from the magnetometer or any other virtual sensor that depends on it (neither via COINES with the Sensor API nor via Development Desktop).
I was wondering if the issue could be that the installed magnetometer is a BMM350, while the firmware I am using is written for the BMM150. Some sources mention the BMM150, but the datasheet specifies a BMM350 magnetometer.
Could you please clarify which magnetometer is actually installed? If it is the BMM350, is there any firmware available for it? Alternatively, could there be another reason why it is not working at all?
Best regards
I am unable to engage the "Maximum FIFO" setting using Development Desktop 2.1, Development Board 3.1, BMI260 - get the following message: "Due to Communication slowness, unable to switch device initialization". I am only using accelerometer - is there anything I can do to use this setting? I seem to be able to use this setting when USB cable connected to Development board 3.1, but can't use it when connecting via Bluetooth
SDK version: v11.2.0
Hardware: SparkFun SEN-26554
Chip ID (0x0079)
Can you possibly confirm whether this hardware revision is supported and whether a newer SDK build is available?
