A lot of the details however will be of more general interest. This post describes how the I2C (Inter-Integrated Circuit, or 'Two-Wire') interface works, with particular reference to the Arduino Uno which is based on the ATmega328P microprocessor chip. This page can be quickly reached from the link: I’m not quite sure what to do or try next.A summary of everything shown below is available further down this page: Both libraries seem to be fairly simple users of the Mbed I2C object, so I’m at a loss for what might have changed between mbed-os 5.15 and 6.x.Īny insight, guidance, or general help is appreciated. Interestingly, the legacy OneWire library also seems to fail in the second single byte read in a polling loop as part of the 1-wire bus reset. MaximInterfaceDevices::DS2482_800 one_wire_master(i2c_wrapper, 0x30) įileHandle *mbed::mbed_override_console(int fd) while ((status & status_1WB) = status_1WB)

MaximInterfaceMbed::I2CMaster i2c_wrapper(i2c_bus) It’s slightly different than the 5.15 version because of BufferedSerial. This is the basic test program for mbed-os 6.x based on the MaximInterface example with the additional channel selection for the DS2482-800. However, when running in 6.0.0, 6.1.0, and 6.2.0 the bus reset fails with a “Nack Error”. MaximInterface with the API fixes works in 5.15.4 the same as the unmodified version. By simply removing the Uart masters and replacing the depricated waits with thread_sleep_for the library will compile in both 5.15.4 and all of the 6.x versions of mbed-os. However, it won’t immediately compile on mbed-os 6+ because of its use of Serial and wait_ms. The MaximInterface library works as-is when I tested it on 5.15.4, and will detect the 1-wire devices on their respective busses.

Looking up wire library