-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mcuboot doesn't build with zephyr v2.1.0 #22814
Comments
MCUboot's master is only compatible with Zephyr's master. If you need backwards compatibility you need to use Zephyr's MCUboot repository at the revision that corresponds to the zephyr release. |
See this discussion on the MCUboot GitHub for more info: |
I am using the Zephyr's MCUboot repository<https://github.com/zephyrproject-rtos/mcuboot>, however there does not seem do be a way to determine the mcuboot revision that corresponds to the zephyr revision.
Zephyr release tags are:
zephyr-v2.1.0
zephyr-v2.0.0
zephyr-v1.14.1
zephyr-v1.13.0
zephyr-v1.12.0
zephyr-v1.11.0
And so on
MCUBoot release tags are:
v1.3.1
v1.3.0
v1.2.0
v1.1.0
v1.0.0
v0.9.0
and so on
What is the algorithm for matching? It would be best if this was handled by ‘west update’ just like all of the other modules from third parties.
Lawrence King
Principal Developer
+1(416)627-7302
From: Carles Cufí <notifications@github.com>
Sent: Friday, February 14, 2020 5:37 AM
To: zephyrproject-rtos/zephyr <zephyr@noreply.github.com>
Cc: Lawrence King <lawrence.king@irdeto.com>; Author <author@noreply.github.com>
Subject: Re: [zephyrproject-rtos/zephyr] mcuboot doesn't build with zephyr v2.1.0 (#22814)
MCUboot's master is only compatible with Zephyr's master. If you need backwards compatibility you need to use Zephyr's MCUboot repository<https://github.com/zephyrproject-rtos/mcuboot> at the revision that corresponds to the zephyr release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#22814?email_source=notifications&email_token=AOG3YIE37SUDUGFBKPWT5XDRCZX4PA5CNFSM4KU5HFA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELYMBII#issuecomment-586203297>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOG3YIANMK77OX7TZEDX33TRCZX4PANCNFSM4KU5HFAQ>.
|
@lawrence-king it's in zephyr's
but I now realize that when we released 2.1.0 we still did not have a zephyrproject-rots MCUboot repo and thus no entry in |
mcuboot is required to use the CONFIG_BOOTLOADER_MCUBOOT=y feature of Zephyr. Cloning mcuboot from either https://github.com/JuulLabs-OSS/mcuboot.git or https://github.com/zephyrproject-rtos/mcuboot.git ends up with something that won't compile.
west build ends up with the error:
To reproduce, run the following steps:
At this point the build error above appears.
Expected behavior
A clean compile
Impact
Cannot build mcuboot
Workaround
This is the cause of the compile error:
Screenshots or console output
Environment (please complete the following information):
GNUARMEMB_TOOLCHAIN_PATH=/usr
The text was updated successfully, but these errors were encountered: