Date
1 - 4 of 4
[meta-zephyr][PATCH] zephyr-sdk: upgrade 0.14.2 -> 0.15.1
|
Naveen Saini
https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.15.1
Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- .../zephyr-sdk/{zephyr-sdk_0.14.2.bb => zephyr-sdk_0.15.1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta-zephyr-core/recipes-devtools/zephyr-sdk/{zephyr-sdk_0.14.2.bb => zephyr-sdk_0.15.1.bb} (83%) diff --git a/meta-zephyr-core/recipes-devtools/zephyr-sdk/zephyr-sdk_0.14.2.bb b/meta-zephyr-core/recipes-devtools/zephyr-sdk/zephyr-sdk_0.15.1.bb similarity index 83% rename from meta-zephyr-core/recipes-devtools/zephyr-sdk/zephyr-sdk_0.14.2.bb rename to meta-zephyr-core/recipes-devtools/zephyr-sdk/zephyr-sdk_0.15.1.bb index c893652..f5a9466 100644 --- a/meta-zephyr-core/recipes-devtools/zephyr-sdk/zephyr-sdk_0.14.2.bb +++ b/meta-zephyr-core/recipes-devtools/zephyr-sdk/zephyr-sdk_0.15.1.bb @@ -14,8 +14,8 @@ SDK_ARCHIVE = "zephyr-sdk-${PV}_linux-${BUILD_ARCH}.tar.gz" SDK_NAME = "${BUILD_ARCH}" SRC_URI = "https://github.com/zephyrproject-rtos/sdk-ng/releases/download/v${PV}/${SDK_ARCHIVE};subdir=${S};name=${SDK_NAME}" -SRC_URI[x86_64.sha256sum] = "2ff0e4d79bffe1468247a3e1958aa9183a0252225ab721cf1c37188bd4b649a2" -SRC_URI[aarch64.sha256sum] = "cbb616a50e940388ea737788d48dcea3624a85bb3ee04d9aae105496a21ae75e" +SRC_URI[x86_64.sha256sum] = "0a7406045102197b9edc759b242499941814a1c6df29dd9fbd479ad50eb0fba9" +SRC_URI[aarch64.sha256sum] = "d2c5de994376a287e8bf12e5776ab8f5105eafa14826608df085142fd01b7f84" do_configure[noexec] = "1" do_compile[noexec] = "1" -- 2.25.1 |
|
|
|
Jon Mason
I added this and rebased it to be before the update to v3.2.0. The
toggle quoted message
Show quoted text
issues with the versioning are now gone, but the following issues remain: "BUILD_ASSERT(IS_ENABLED(_RETARGETABLE_LOCKING), "Retargetable locking must be enabled");" for zephyr-coap-client https://gitlab.com/jonmason00/meta-zephyr/-/jobs/3231258971 zephyr-coap-server https://gitlab.com/jonmason00/meta-zephyr/-/jobs/3231258983 https://gitlab.com/jonmason00/meta-zephyr/-/jobs/3231258987 zephyr-openthread-echo-client https://gitlab.com/jonmason00/meta-zephyr/-/jobs/3231258972 "region `SRAM' overflowed by 1104 bytes" for zephyr-philosophers https://gitlab.com/jonmason00/meta-zephyr/-/jobs/3231259005 https://gitlab.com/jonmason00/meta-zephyr/-/jobs/3231259002 Thanks, Jon On Wed, Oct 26, 2022 at 01:29:45PM +0800, Naveen Saini wrote:
https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.15.1 |
|
|
|
Naveen Saini
Hi Mason
toggle quoted message
Show quoted text
-----Original Message-----[Naveen] I already sent patch to fix this issue. [Naveen] As per my understanding available ram for qemu-cortex-m0 is only 16K, not sufficient for sample philosophers. So I think you should remove it for qemu-cortex-m0 machine. From build logs: SRAM (wx) : ORIGIN = 0x20000000, LENGTH = (16 * 1K) And also listed in yaml too https://github.com/zephyrproject-rtos/zephyr/blob/v3.2-branch/boards/arm/qemu_cortex_m0/qemu_cortex_m0.yaml#L10 I case see many tests and samples are being filter out based on 'min_ram' https://github.com/zephyrproject-rtos/zephyr/blob/v3.2-branch/samples/net/sockets/http_client/sample.yaml#L3
|
|
|
|
Jon Mason
On Thu, Nov 10, 2022 at 09:19:54AM +0000, Saini, Naveen Kumar wrote:
Hi MasonI had one as well.-----Original Message-----[Naveen] I already sent patch to fix this issue. https://gitlab.com/jonmason00/meta-zephyr/-/commit/68a50789d28af04c0df8b46bb4d27a87e8d98cb3 Sorry for not sending it out. I was occupied almost all of last week. I like your patch better :) [Naveen] Sure, I can do a patch shortly that will remove this from qemu_cortex_m0. This would leave the only outstanding issue the new poll test failure on qemu_cortex_a9 (yocto toolchain only). I think it's okay to let this fail while a solution is being found. Thanks, Jon
|
|
|