No barometer after BF update

[cold patio]

I have two identical FC that report themselves as FLASHHOBBYF405. One of them has the original stock firmware (4.4.2), another was reflashed with BF Configurator to the newer 4.4.3, then back to 4.4.2. Now the updated FC has no barometer available.
There is nothing connected to both FC, and barometer is DPS310. I am attaching CLI status and CLI dump output from both boards. The faulty firmware(?) reports I2C: 0, does not report BARO=DPS310, and both of them have I2C Errors: 0.
It seems that the factory firmware is not identical to the one built by Betaflight, and I would like to have both BF Configurator firmware and barometer together.

[valid spade]

Try this: https://hackmd.io/@nerdCopter/ByheaoLQh

[cold patio]

Thank you! USE_BARO_DPS310 define during the cloud build solved the issue with 4.4.2. Will try to submit the data as by the link. Is it possible that there are more than one variation of that board with different barometers?

[valid spade]

Yes, its possible. The manufaturer would know for sure

[cold patio]

So appears that USE_BARO_DPS310 should be added to the FLASHHOBBYF405 target. Do I need to gather the support data and comment somewhere, or this support forum post is sufficient?

[bleak briar]

If you can post a support ID for confirmation, I'll submit a PR to update the target

[hushed dagger]

love it when i see my own FAQ. i updated some verbiage and fixed the links.

all i need now is google Adsense, lmao

[finite vault]

Seems to be a clone?

https://www.flashhobby.com/f405-stack-flight-controller.html

Sent a message to flashhobby for confirmation.

[bleak briar]

On the product page:

[finite vault]

@bleak briar we have some confusion here: https://github.com/betaflight/unified-targets/issues/1235

[bleak briar]

Define includes SPI BARO for some reason, even though it's clearly SPI...

[bleak briar]

What is inconsistent here?

[cold patio]

So there are indeed both BMP280 and DPS310 versions of the same board...

[finite vault]

No GYRO / ACC showing up

[bleak briar]

Are they using an external baro here? It's weird this config has both I2C1 and I2C2 defines and the baro is on I2C2, while the current config and the OP here has a baro working on I2C1 and no I2C2 define

ok so just ran these through notepad++ and wow... It's like they are 2 completely different boards, gonna try manually changing and report back

What are they flashing? Is it a different FC?

[finite vault]

Need to further interrogate the user - if still around

[cold patio]

Anything I can help with? Support id will be ready in a few hours

[bleak briar]

Submitted a PR for this issue
https://github.com/betaflight/config/pull/341

[finite vault]

Can you do one for unified targets too

[bleak briar]

https://github.com/betaflight/unified-targets/pull/1263

[cold patio]

By the way, are the changes to the targets/configs effective immediately or rebuild of the hex file is required?

Thank you all for the support!

[finite vault]

Rebuild - might have to change options to not to get the cached version. It needs a cloud rebuild.