BT_HCI_OP_VS_READ_VERSION_INFO result seems incorrect?

[denis]

I'm using NCS 2.7.0 and NCS 2.9.0 to read the BT stack version information on an nRF5340.  See below for the results.

How should the fw_version, fw_revision, and fw_build be interpreted?  The numbers look quite large to be major, minor, patch.  I'm looking for something in that format.  Or an explanation of what is being returned that I can use to determine a BT stack version that can be compared to see if it is a new version.

NCS 2.7.0

status =0 '\000'

hw_platform =2

hw_variant =3

fw_variant =0 '\000'

fw_version =214 '?'

fw_revision =51162

fw_build =1926957230

NSC 2.9.0

hw_platform =2

hw_variant =3

fw_variant =0 '\000'

fw_version =45 '-'

fw_revision =41337

fw_build =3074452168

[Sigurd]

Hi!

The numbers looks correct. There is no major.minor.patch format to these fw_version, fw_revision , fw_build numbers. So you can't determine if the stack is newer or not by only comparing 2 sets with fw_revision,fw_revision, fw_build .

You need to look at the rev for the SDC, e.g. SDC for nRF53 NCS 2.9.0 here:

https://github.com/nrfconnect/sdk-nrfxlib/tree/v2.9.0/softdevice_controller/lib/nrf53/soft-float

For 2.9.0 it's 2d 79a1 c86a40b7 3cf674f90b22d3c480747282ba

hex 2d -> dec 45

hex A179 -> dec 41337 

hex B7406AC8 -> dec 3074452168

fw_version =45 '-'

fw_revision =41337

fw_build =3074452168

BR,

Sigurd

[denis]

So to summarize, the fw_version, fw_revision , fw_build numbers get turned into the git commit prefix.  Correct?

In the manifest.xml I see:

description: SoftDevice Controller
git_revision: 2d79a1c86a40b73cf674f90b22d3c480747282ba
ll_subversion_number: '0x206B'
ll_version_number: '0x0E'
timestamp: '2024-12-12T12:43:40Z'

Is there any way to get a soft device version number from the git repo?  And/or nRF Connect SDK version number?