BME688 BSEC_E_CONFIG_VERSIONMISMATCH on BSEC2.4.0.0 and BSEC2.2.0.0

[Prop4et]

Hi all,

when trying to load the configuration file i get the BSEC_E_CONFIG_VERSIONMISMATCH. I tried with both BSEC_2.2.0.0 and with BSEC2.4.0.0 (changed header, .a and .config file between the two). I then checked the version of the sw with bsec_get_version() and it returns the proper one for each case.

I'm working on a raspberry pi pico with an external sd and sd reader. I tried reading another file beforhand and the read function works fine. After that i actually tried to compare whats inside the bsec_selectivity.config file to what's inside the bsec_selectivity.c (they are both arrays and they should be the same don't they?). I noticed that the length is the same (1974) but the heads and the tails differ (for the 2.4 version).
The .config head is

[182, 7, 0, 0, 0,0,4,2,...] 

while the .c file has

[0,0,4,2, ....] 

that are the next values for the .config file.

The tails are the opposite, the .config file one is 

[1, 0, 0, 0, 0]

while the .c file has

[1,0,0,0,0,233,74,0,0]

so basically the last four values aren't there for the .config file.

In conclusion if we take the .config file as a reference we can say that the .c file is shifted 4 positions to the left and has 4 values more at the end.
Why is that difference? Is there a chance that this is why i have the error? Because loading the .c file doesn't return an error but gives me the ok (0) code.

[Prop4et]

I made a mistake.
After that i tried to read the file with a longer buffer and it actually reads 1978 bytes, while the max blob size is 1974. The 1978 bytes file is the same as the one contained in the .c file, except for the head where it has 4 bytes more (so 4 more elements of type uint8_t). Why is that so?

[BSTRobin]

Hi Prop4et,

You should use config file and BSEC library under same bsec_2-2-0-0 package or bsec_2-4-0-0 package, don't cross use them.

[BSTRobin]

Hi Prop4et,

You should use config file and BSEC library under same bsec_2-2-0-0 package or bsec_2-4-0-0 package, don't cross use them.

[Prop4et]

Since the first one gave me the version mismsatch i changed the library version and therefore i changed the config file. It is still giving me the same error.
I also bought a dev kit and created a new algorithm and after that i exported the config file for the right version of the library that i am using. When calling the set_configuration i still get the version mismatch.
Tell me if i do something wrong during the loading procedure at this point:

f_read(&fil, serialized_settings, BSEC_MAX_PROPERTY_BLOB_SIZE*sizeof(uint8_t), &bread);

rslt_bsec = bsec_set_configuration(bsec_config_selectivity, n_serialized_settings_max, work_buffer, n_work_buffer);

after the f_read the number of bytes read is 2285, that is the dimension defined by the documentation, but if i analyze the file it is 4 bytes larger, meaning that i miss these 4 bytes by doing so

[BSTRobin]

Refer the solution in similar topic https://community.bosch-sensortec.com/t5/MEMS-sensors-forum/BSEC2-2-0-0-set-configuration-version-mi...

Firstly, it is better to refer release note in BME688 dev kit software package, for example the release note in BME688 dev kit software v2.0.6 mentioned BSEC library and BME AI-Stuio version requirement.