LPC55xx SDK: Meaning of driver version number embedded in *.h files

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LPC55xx SDK: Meaning of driver version number embedded in *.h files

1,117件の閲覧回数
danielholala
Senior Contributor II

Hi there,

Just came across FSL_CLOCK_DRIVER_VERSION and figured that it does not always change when the driver code changes, see for example here:

Driver version stable and unfazed...

https://github.com/nxp-mcuxpresso/mcux-sdk/blame/main/devices/LPC5526/drivers/fsl_clock.h

although code changed....

https://github.com/nxp-mcuxpresso/mcux-sdk/blame/main/devices/LPC5526/drivers/fsl_clock.c#L851

 

So out of curiosity, what is the meaning and use of the *_DRIVER_VERSION defined in different drivers?

Thanks.
Daniel

 

 

0 件の賞賛
返信
2 返答(返信)

1,089件の閲覧回数
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @danielholala 

It seems this is related to  products series, for example,  the lpc556/2/1/0x series are (2,3,6).

LPC55s6x is (2,3,1). LPC546xx is (2,5,4). 

 

BR

Alice

 

0 件の賞賛
返信

1,076件の閲覧回数
danielholala
Senior Contributor II

Dear @Alice_Yang ,

I think that is not correct.

Files in Github easily refute your statement, e.g., from SDK 2.13.0 release:

LPC55S69 fsl_clock.hMAKE_VERSION(2, 3, 6)

LPC5528 fsl_clock.h: MAKE_VERSION(2, 3, 6)

LPC5528 fsl_power.h: MAKE_VERSION(1, 0, 0)

=> version is not related to product series

Further, compare with an older SDK 2.9.0 release for the same product and file:

LPC5528 fsl_clock.h: MAKE_VERSION(2, 3, 4)

=> Different SDK versions relate to different versions.

I assume that somebody forgot to bump up the version

 

 

0 件の賞賛
返信