5 years, 5 months ago.

Xadow M0 does not compile with mbed above rev. 142

Using the Xadow M0 bilnky (https://os.mbed.com/teams/Seeed/code/xadow_m0_blinky/) and various revisions of Mbed:

  • 88: Works, 2.8kB flash - the first version that supports Xadow M0
  • 108: Works, 3.0kB flash
  • 118: Works, 3.0kB flash
  • 120: Works, 3.0kB flash
  • 121: Works, 3.0kB flash
  • 122: Works, 8.3kB flash
  • 123: Works, 8.2kB flash
  • 128: Works, 8.2kB flash
  • 136: Works, 8.2kB flash
  • 140: Works, 8.2kB flash
  • 141: Works, 8.3kB flash

Why does it become so bloated after rev. 122?

  • 142: and later, compile fails. The error:

Error: Library name 'platform' is not unique (defined in '/extras/mbed_4eea097334d6/TARGET_XADOW_M0/mbed_lib.json' and '/extras/mbed_4eea097334d6/TARGET_LPC11U35_501/mbed_lib.json')


Question relating to:

Xadow M0 is an mbed enabled development board with Xadow form factor. Xadow is a series of flexible electronic modules including sensors, displays and etc. Several Xadow modules can be …

Related issue on GitHub: https://github.com/ARMmbed/mbed-os/issues/5887

posted by P R 28 Nov 2018

1 Answer

5 years, 5 months ago.

The blinky program with latest mbed-src library can be compiled sucessfully, but with the latest mbed library, it fails.

It seems the transition from the mbed-src library to the mbed library has an issue with the Xadow M0 target.

At the moment, you may try to compile your program with other targets which have the same MCU with the Xadow M0, such as https://os.mbed.com/platforms/EA-LPC11U35/

or use the mbed-src library instead.

Thanks for the hint. Using mbed-src (rev. 635) does indeed work. And the resulting binary uses only 2.8kB flash. However mbed-src was deprecated in 2015 and superseded by mbed-dev. Which also works, but gives 8.4kB binaries. I am curious what does the "platform selection" change?

posted by P R 21 Dec 2017