# 0.96 Inch 4Pin White IIC I2C OLED Display For Arduino

**URL:** <https://forum.xod.io/t/0-96-inch-4pin-white-iic-i2c-oled-display-for-arduino/3004>\
**Category:** Hardware Interfacing Questions\
**Created:** [December 4, 2019, 12:06pm UTC](https://forum.xod.io/t/0-96-inch-4pin-white-iic-i2c-oled-display-for-arduino/3004 "2019-12-04T12:06:53Z")\
**Posts on this page:** 1\
**Showing post:** 50

<div class="post-metadata">

**Author:** ![nkrkv](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.xod.io/nkrkv/32/8_2.png) [@nkrkv](https://forum.xod.io/u/nkrkv)\
**Post date:** [December 9, 2019, 10:00am UTC](https://forum.xod.io/t/0-96-inch-4pin-white-iic-i2c-oled-display-for-arduino/3004/50 "2019-12-09T10:00:24Z")

</div>

Hi there! The problem is not with the @wayland library but indeed with XOD itself.

To be more precise, XOD uses the so-called “placement new” operator heavily which was not defined on some platforms. So it defines its own implementation. Recently official Arduino released “Arduino AVR Boards version **1.8.2** ” which carries the implementation natively. So, now you get the error of placement new defined multiple times:

```auto
... blah blah blah

new.cpp.o (symbol from plugin): In function `operator new(unsigned int)':
(.text+0x0): multiple definition of `operator new(unsigned int, void*)'

... blah blah blah

... report to XOD developers.

```

The issue was fixed recently with the release of XOD 0.32.1. Feel free to update to get rid of the error.

---

_[View the full topic](https://forum.xod.io/t/0-96-inch-4pin-white-iic-i2c-oled-display-for-arduino/3004)._