Mbed-os: Tracking issue for IAR 8 library updates

[deepikabhavnani]

Description

Each library in the following list must be re-compiled with IAR EWARM 8.32 to support the upcoming Mbed OS release 5.12.0 and onward.
Please make pull requests containing the updated libraries to the branch feature-iar8.

Below is the list of libraries for various targets in Mbed OS, and failures noticed:

### Green Tea build fails:

• [x] UBLOX_EVK_ODIN_W2 - Build fails
• [x] MTB_UBLOX_ODIN_W2 - Build fails
• [x] MBED_CONNECT_ODIN - Build fails

targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F439xI/TARGET_MODULE_UBLOX_ODIN_W2/sdk/TOOLCHAIN_IAR/libublox-odin-w2-driver.a
PR: https://github.com/ARMmbed/mbed-os/pull/9682

• [x] MTB_MXCHIP_EMW3166 - Build fails

  targets/TARGET_WICED/TOOLCHAIN_IAR/TARGET_MTB_MXCHIP_EMW3166/libwiced_drivers.a
  https://github.com/ARMmbed/mbed-os/pull/9847

• [x] MTB_ADV_WISE_1530 - Build fails

  targets/TARGET_WICED/TOOLCHAIN_IAR/TARGET_MTB_ADV_WISE_1530/libwiced_drivers.a
  https://github.com/ARMmbed/mbed-os/pull/9847

• [x] MTB_USI_WM_BN_BM_22

  targets/TARGET_WICED/TOOLCHAIN_IAR/TARGET_MTB_USI_WM_BN_BM_22/libwiced_drivers.a
  https://github.com/ARMmbed/mbed-os/pull/9847

• [x] CY8CKIT_062_WIFI_BT
• [x] CY8CMOD_062_4343W
• [x] CY8CKIT_062_4343W

• [x] CYW943012P6EVB_01
  wiced_drivers binaries - Track PR https://github.com/ARMmbed/mbed-os/pull/9867

• [ ] REALTEK_RTL8195AM - Failing in CI
  targets/TARGET_Realtek/TARGET_AMEBA/TARGET_MCU_RTL8195A/device/TOOLCHAIN_IAR/lib_peripheral_mbed_iar.a
  targets/TARGET_Realtek/TARGET_AMEBA/TARGET_MCU_RTL8195A/device/TOOLCHAIN_IAR/lib_wlan_mbed_iar.a

### Green tea build successful

• [X] ARM_BEETLE_SOC (Cordio is tested in CI? - Not part of green tea / examples)

  targets/TARGET_ARM_SSG/TARGET_BEETLE/TOOLCHAIN_IAR/libcordio.0.0.2.a
  targets/TARGET_ARM_SSG/TARGET_BEETLE/TOOLCHAIN_IAR/libcordio_platform.0.0.2.a

Target removed from 5.12 - https://github.com/ARMmbed/mbed-os/pull/9833

• [ ] MAX32610

  targets/TARGET_Maxim/TARGET_MAX32610/TOOLCHAIN_IAR/libexactLE.a

• [ ] MAX32620

  targets/TARGET_Maxim/TARGET_MAX32620/TOOLCHAIN_IAR/libexactLE.a

• [x] MAX32630

  targets/TARGET_Maxim/TARGET_MAX32630/TOOLCHAIN_IAR/libexactLE.a

• [x] UNO_91H

  targets/TARGET_RDA/TARGET_UNO_91H/lib/TOOLCHAIN_IAR/libhal.a

• [x] SL_RAIL

  targets/TARGET_Silicon_Labs/TARGET_SL_RAIL/efr32-rf-driver/rail/TARGET_EFR32_1/librail_efr32xg1_release.a
  targets/TARGET_Silicon_Labs/TARGET_SL_RAIL/efr32-rf-driver/rail/TARGET_EFR32_12/librail_efr32xg12_release.a

• Was fixed in https://github.com/ARMmbed/mbed-os/pull/6577#issuecomment-383151713

• [x] LPC54114 - No updated needed. Confirmed with @mmahadevan108
  targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_LPC54114/device/TARGET_LPC54114_M4/TOOLCHAIN_IAR/libpower.a

• [x] FF_LPC546XX - No updated needed

• [x] LPC546XX
• [x] MCU_LPC546XX - Build fails on master for GCC_ARM as well Not a public target
  targets/TARGET_NXP/TARGET_MCUXpresso_MCUS/TARGET_MCU_LPC546XX/device/TOOLCHAIN_IAR/lib_power.a

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

[cmonr]

@ARMmbed/team-ublox @ARMmbed/team-maximintegrated @ARMmbed/mbed-os-pan @ARMmbed/team-realtek @kyliuxing @ARMmbed/team-silabs @ARMmbed/team-nxp

Fyi.

@screamerbg @MarceloSalazar @ashok-rao Fyi as well. Feel free to add/tag anyone else that's misssing.

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-370

[deepikabhavnani]

Target_WICED was last updated by @ARMmbed/mbed-os-ipcore (https://github.com/ARMmbed/mbed-os/pull/8949).
Please have a look at IAR 8.x requirement and binary updates needed to support the same.

[mmahadevan108]

Build and test works with IAR 8.30 on LPCXpresso54114 and LPC54628 boards

[deepikabhavnani]

https://github.com/ARMmbed/mbed-os/pull/9524 - IAR is removed from supported_toolchain config option for targets failing green tea test to verify all IAR8.x specific changes.

[deepikabhavnani]

@SeppoTakalo - Do we have any update for wiced binaries compatible to IAR 8.x?
Binaries are needed for MTB_MXCHIP_EMW3166, MTB_ADV_WISE_1530, MTB_USI_WM_BN_BM_22 and all cypress targets

[SeppoTakalo]

@deepikabhavnani Please see https://jira.arm.com/browse/IOTCORE-1051

[JanneKiiskila]

I think with UBLOX ODIN also non-green-tea builds fail, client build fails, too.

03:58:57 Error[Li009]: runtime model conflict: Module
03:58:57           cb_main.o(libublox-odin-w2-driver.a) specifies that '__CPP_Language'
03:58:57           must be 'C++14', but module SPWFSA01.o has the value 'C++'
03:58:57 Warning[Lt009]: Inconsistent wchar_t size
03:58:57             SPWFSA01.o and 1277 other objects have wchar_t size 16 bits
03:58:57             cb_main.o(libublox-odin-w2-driver.a) and 120 other objects have
03:58:57                       wchar_t size 32 bits
03:58:57 [ERROR] Error[Li009]: runtime model conflict: Module
03:58:57           cb_main.o(libublox-odin-w2-driver.a) specifies that '__CPP_Language'
03:58:57           must be 'C++14', but module SPWFSA01.o has the value 'C++'
03:58:57 Warning[Lt009]: Inconsistent wchar_t size
03:58:57             SPWFSA01.o and 1277 other objects have wchar_t size 16 bits
03:58:57             cb_main.o(libublox-odin-w2-driver.a) and 120 other objects have
03:58:57                       wchar_t size 32 bits

@ARMmbed/team-ublox - can give it a look?

[SeppoTakalo]

REALTEK_RTL8195AM disabled from ALL builds.
Not just IAR.

[deepikabhavnani]

@ARMmbed/mbed-os-maintainers - I might have missed some updates (if any) in past few weeks, can we tag Maxim and Realtek partners or internal team to get some updates.

[cmonr]

@ARMmbed/team-renesas @ARMmbed/team-maximintegrated @bentcooke

[cydriftcloud]

The latest WICED library update with IAR 8 support for Cypress targets has been merged in PR #10289

[bulislaw]

@MarceloSalazar could you try reaching out to partners that didn't update their targets yet?

[0xc0170]

@MarceloSalazar could you try reaching out to partners that didn't update their targets yet?

@MarceloSalazar What's the status ?

[MarceloSalazar]

@0xc0170 we're now keeping track of issues for Realtek/Maxim targets separately.
We'll work with them separately.

I'd suggest we close this ticket.