Moving to 2.6.0 from 2.3.0 problem with VERSION

RE: Moving to 2.6.0 from 2.3.0 problem with VERSION

Hieu — Thu, 30 May 2024 20:23:49 GMT

Hi Brian,

Application version management using the VERSION file was introduced in NCS v2.6.0. To my experience, you do not need to include the file via CMakeLists.txt like that. The build system is setup to automatically detect and take in the file.

Also, VERSION is not a Kconfig file, so when you include it into CONF_FILE like you showed, the build system will try to interpret it as a Kconfig file and caused the "ignoring malformed line" warnings.
Your mention of those warnings in your opening post makes sense now.

[quote user="finkbr"]

CONFIG_MCUBOOT_IMAGE_VERSION="1.0.21+1"

and that no longer works and i am now sing the VERSION file.

[/quote]

If you want to use Kconfig, technically it still works. The NCS specific Kconfig is just removed in to unify the versioning solution with Zephyr's, and the Kconfig you should use is now CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION instead.

But VERSION file is the preferred way.

[quote user="finkbr"]Am I to assume that MCUBOOT will automatically pick up the version file and use the version it contains?[/quote]

I inadvertently answered it first already, but yes.

[quote user="finkbr"]If so, Thank you and you can close this ticket, otherwise, what should I do for MCUBOOT versioning.[/quote]

Alright. Good to know everything is clear now. I will close the ticket then 🙂

Hieu

RE: Moving to 2.6.0 from 2.3.0 problem with VERSION

finkbr — Thu, 30 May 2024 19:31:32 GMT

Hi, I did, ive done it before, the website is saying an error occurred and wont let me.

I built peripheral sample and the basic build works, when i add the versioning it gives the same error. HOWEVER:

I have a section in the CMakeLists.txt file

# Define configuration files.
list(APPEND CONF_FILE
  ${CMAKE_CURRENT_SOURCE_DIR}/conf/prj.conf
  ${CMAKE_CURRENT_SOURCE_DIR}/conf/prj-${BUILD_TYPE}.conf
  #${CMAKE_CURRENT_SOURCE_DIR}/conf/version.conf
  #${CMAKE_CURRENT_SOURCE_DIR}/VERSION
)

That appends all the the conf files together. With the old versioning method this was fine. Now its not. After commenting out the append for VERSION it now compiles. Now the last question which is what brought me to this new way of doing things. We used to use

CONFIG_MCUBOOT_IMAGE_VERSION="1.0.21+1"

and that no longer works and i am now sing the VERSION file. Am I to assume that MCUBOOT will automatically pick up the version file and use the version it contains? If so, Thank you and you can close this ticket, otherwise, what should I do for MCUBOOT versioning.

Brian

RE: Moving to 2.6.0 from 2.3.0 problem with VERSION

Hieu — Thu, 30 May 2024 19:25:22 GMT

Hi Brian,

For adding code, please try to use the Insert > Code menu option.

For files, usually I just drag a file and drop into the edit box. But you could try using the Insert > Image/video/file menu option too.

Please do check if Peripheral UART work.

RE: Moving to 2.6.0 from 2.3.0 problem with VERSION

finkbr — Thu, 30 May 2024 16:54:04 GMT

Hi Hieu,

Yes I am on the correct toolchain version 2.6.0, sdk 2.6.0. There are spaces before and after the '=' sign. I deleted the build directories, no change. the only invisible characters in the file are the carriage return and line feed produced by the \n in the cmake file.

I will work on building the Peripheral UART.

I cant seem to attach any code or anything right now, the website is telling me there is an error wen i try to upload a file or insert code to this reply.

RE: Moving to 2.6.0 from 2.3.0 problem with VERSION

Hieu — Thu, 30 May 2024 13:32:45 GMT

Hi Brian,

The correct way is with a space character before and after the equal sign.

Could you please try to remove the build directory completely and build again from the beginning?

Please also:
- Check if you are on the correct toolchain version.
- Check if there are any invisible invalid character in the VERSION file.
- Try building the Peripheral UART sample with your current setup, to see if the same issue happened.

If none of that works, could you please share the full build log with less of the file path redacted? I would like to see the relative path of the files within the project, at least.

Hieu