NanostackRfPhyEfr32 driver does not build

[SeppoTakalo]

Description

• Type: Bug

NanostackRfPhyEfr32 references RAIL_IEEE802154_Init() function that is introduced in targets/TARGET_Silicon_Labs/TARGET_SL_RAIL/efr32-rf-driver/rail/ieee802154/rail_ieee802154.h header. However, no implementation of it exists in build tree.

This SL_RAIL label was enabled on following MCUs:

• EFR32MG1P132F256GM48
• EFR32MG1P233F256GM48
• EFR32MG12P332F1024GL125

Needs fix from Silicon Labs.

Update

Looks like those functions appear in binary libraries:

Binary file targets/TARGET_Silicon_Labs/TARGET_SL_RAIL/efr32-rf-driver/rail/TARGET_EFR32_12/librail_efr32xg12_release.a matches.

Binary file targets/TARGET_Silicon_Labs/TARGET_SL_RAIL/efr32-rf-driver/rail/TARGET_EFR32_1/librail_efr32xg1_release.a matches.

But as show, there are few problems:

• Enabling SL_RAIL does not automatically enable EFR32_1 or EFR32_12, so build remains broken for targets that enable SL_RAIL but not some of those.
• Binaries are provided, but only for unknown toolchain. .a is either GCC or IAR.

For fixing the issue:

• Binaries have to be provided for all 3 compilers: GCC, IAR and ARM.
• Clarification/fixing the flag dependencies between EFR32_1, EFR32_12 and SL_RAIL

[SeppoTakalo]

CC: @stevew817 @0xc0170

[0xc0170]

There's librail library in the tree, but the question is - what compiler was used to generate (from one earlier PR there was a mention gcc, also name indicates that)?

Our CI failed to link with ARMCC. Any binary lib should have all 3 compilers supported.

I can think of this and then labels - somehow the library is not being picked up.

Update: The Pr referenced above contains an update with some info why it started failing.

[stevew817]

Should be fixed by PR #6701