Zephyr 3.2 module updates overview

[fabiobaltieri]

Umbrella issue for tracking requests for updating various modules before Zephyr 3.2, listing all modules and an overview of the status compared to the correseponding upstream. Checkbox tick for modules where don't need extra work for 3.2 (up to date or no plan/need for an update for this release).

• canopennode
  • last updated somewhere in 2020
  • upstream at https://github.com/CANopenNode/CANopenNode
  • currently tracking https://github.com/CANopenNode/CANopenNode/commits/v1.3-master
• chre
• cmsis
  • at 5.8.0, 5.9.0 avilable
  • https://github.com/ARM-software/CMSIS_5/releases
  • Update to CMSIS 5.9.0 #45279
• edtt
• fatfs
• fff (@yperess)
  • checked out at 2019, upstream has recent commits
  • https://github.com/meekrosoft/fff
• hal_altera (@nashif)
  • link in the README not working, references quartus v17.0, 21.1.1 is available
  • https://www.intel.com/content/www/us/en/collections/products/fpga/software/downloads.html?s=Newest
• hal_atmel (@nandojve)
  • Don`t track ASF or any version from it because only have register definitions.
  • Additions and updates came as packs from http://packs.download.atmel.com
  • Fixes are allowed directly using PR (last patch Ago/22) - recommended way
  • Status: stable since 2.7.0 LTS
• hal_espressif (@sylvioalves @glaubermaroto @uLipe)
  • on 4.3, 4.4 available
  • https://github.com/espressif/esp-idf
  • soc: esp32: updates to sync with v4.4.1 hal_espressif #49682
• hal_gigadevice
• hal_infineon
• hal_microchip
  • upstream seems stale https://github.com/MicrochipTech/Peripheral-mec1701
• hal_nordic
• hal_nuvoton (@ssekar15)
  • never been updated, upstream has recent commits
  • https://github.com/OpenNuvoton/M480BSP
  • MAINTAINERS: update maintainers for hal_nuvoton #49809 (maintainer update)
• hal_nxp
• hal_openisa
  • upstream is stale https://github.com/open-isa-rv32m1/rv32m1_sdk_riscv
• hal_quicklogic (@kowalewskijan)
  • upstream has recent commits
  • https://github.com/QuickLogic-Corp/qorc-sdk/commits/master/HAL/src
• hal_rpi_pico (@yonsch)
  • at 1.3.0, 1.4.0 just released
  • https://github.com/raspberrypi/pico-sdk/commits/master
• hal_silabs (@yonsch @mnkp @chrta)
  • at 3.1.0 (?), 4.1.0 available
  • https://github.com/SiliconLabs/gecko_sdk
• hal_st
• hal_stm32
• hal_telink
• hal_ti (@cfriedt @gmarull)
  • at simplelink 4.40.04.04, # out of date, simplelink 6.20.00.29 available
  • https://www.ti.com/tool/SIMPLELINK-CC13XX-CC26XX-SDK#downloads
• hal_xtensa (@dcpleung)
  • upstream at https://github.com/foss-xtensa/xtensa-hal
• libmetal
• liblc3
• littlefs (no maintaner)
  • at v2.4, v2.5 available
  • https://github.com/littlefs-project/littlefs
  • update littlefs module to v2.5 littlefs#12 and Update littlefs module #49770
• loramac-node
• lvgl (@brgl)
  • at v8.2.0, v8.3.1 is available
  • https://github.com/lvgl/lvgl
• lz4 (@Navin-Sankar)
  • local repo is somewhere around 1.9.3, v1.9.4 available
  • https://github.com/lz4/lz4
• mbedtls (@d3zd3z @ceolin)
  • at v3.1.0, v3.2.1 available
  • https://github.com/Mbed-TLS/mbedtls
• mcuboot
• mipi-sys-t
• nanopb
• net-tools
  • no upstream
• nrf_hw_models
• open-amp
• openthread
• picolibc
• segger (@nordic-krch)
  • at v3.30, v3.32 available
  • https://www.segger.com/downloads/systemview/
  • no update for 3.2 (checked with the maintainer on discord)
• sof
• tflite-micro (@laurenmurphyx64)
  • out of date, stuck somewhere in 2021
  • https://github.com/tensorflow/tflite-micro
• tinycbor
  • deprecated
• tinycrypt
  • upstream last commit in 2019
  • https://github.com/intel/tinycrypt
• TraceRecorderSource (@tleksell-pe)
  • at 4.6.3, 4.6.6 available
  • https://github.com/percepio/TraceRecorderSource
• trusted-firmware-m
• tf-m-tests
• psa-arch-tests (@microbuilder)
  • mostly updated, few new upstream commits
  • https://github.com/ARM-software/psa-arch-tests/commits/main
• uoscore-uedhoc (@rlubos)
  • no need to update for 3.2
• zcbor
• zscilib
  • no upstream

[henrikbrixandersen]

• canopennode
  • last updated somewhere in 2020
  • upstream at https://github.com/CANopenNode/CANopenNode

We are tracking upstream v1.3-master (https://github.com/CANopenNode/CANopenNode/commits/v1.3-master) and as such we are up-to-date (except a couple of commits which breaks the upstream API).

[stephanosio]

[ ] cmsis

• at 5.8.0, 5.9.0 avilable
• https://github.com/ARM-software/CMSIS_5/releases

There is already an issue open for this:
#45279

Unfortunately, it does not look like it will be done for 3.2.

[fabiobaltieri]

@yperess @nashif @nandojve @sylvioalves @glaubermaroto @uLipe @MulinChao @ChiHuaL @WealianLiao @kowalewskijan @yonsch @yonsch @mnkp @chrta @cfriedt @gmarull @dcpleung @brgl @Navin-Sankar @d3zd3z @ceolin @nordic-krch @laurenmurphyx64 @tleksell-pe @microbuilder @rlubos

Hi! If you are listed here you are a maintainer for a Zephyr module that has updates available upstream. The merge window closes on September 9th, does your module needs an update? Feel free to tick the corresponding item, add a comment, open an issue, a PR or whatever suits.

Thanks!

[yperess]

@fabiobaltieri fff's commit is just a restructure of the directory and CI, there's another on the way which I hope to merge shortly. That last one will actually change the header and I'll pull both at the same time.

[chrta]

• hal_silabs (@yonsch @mnkp @chrta)
  at 3.1.0 (?), 4.1.0 available
  https://github.com/SiliconLabs/gecko_sdk

I do not plan to update the sdk. The version information (that the currently used version is 3.1.0) is correct. See also #43139

[nandojve]

Hi @fabiobaltieri ,

hal_atmel (@nandojve)
current version unclear, latest v3.52.0

hal_atmel did not track ASF versions. The hal_atmel only have registers files and are added/updated based on http://packs.download.atmel.com. I think there won`t be any new activity for v3.2.

hal_gigadevice is usually tracked by @gmarull and me and I believe there is no pending things till moment.

[dcpleung]

upstream of hal_xtensa is https://github.com/foss-xtensa/xtensa-hal, which has no update.

[sylvioalves]

@fabiobaltieri, hal_espressif will be updated to v4.4.1 with this PR: #49682

[ChiHuaL]

• hal_nuvoton (@MulinChao @ChiHuaL @WealianLiao)
  never been updated, upstream has recent commits
  https://github.com/OpenNuvoton/M480BSP

Actually, We (@MulinChao and @ChiHuaL) are not maintainers for the HAL.
We maintain Nuvoton EC series chip (NPCX series) and put everything in the Zephyr repository based on the disscussion here. We didn't use the hal for EC chip.

The Hal part is used for general MCU chips (Numicro) in Nuvoton.
The hal maintainer should be @ssekar15.

[ssekar15]

hal_nuvoton (@MulinChao @ChiHuaL @WealianLiao)
never been updated, upstream has recent commits
https://github.com/OpenNuvoton/M480BSP

@fabiobaltieri
I will do it

[cfriedt]

There is no rush to update hal_ti right now. I am in discussion with 2 candidates (TI employees) who may be better as maintainers.

[yonsch]

No need to update hal_rpi_pico for now

[microbuilder]

psa-arch-tests in Zephyr is tightly-coupled to the version of TF-M being used, so we won't pull upstream updates in until we also update TF-M, which will be post 3.2. Marked as done.