Abhishek Malik

Seeing some very weird things on Firmata: >>> i2c.readReg(0x07) 2L >>> i2c.readReg(0x07) 2L >>> i2c.readReg(0x07) 0L >>> i2c.readReg(0x07) 1L >>> i2c.readReg(0x07) 1L >>> i2c.readReg(0x07) 0L >>> i2c.readReg(0x07) 1L >>> i2c.readReg(0x07)...

Using mraa_i2c_read_bytes_data() call somehow seems to do the trick for me and gives me the expected values. Tried changing the delay and other things in the firmata implementation in mraa...

patched the driver : f37236fa01469050714f89f839a1fac51a824096

@JuergenReppSIT we're seeing this on a 32 bit container "ubuntu-20.04.arm32v7"

load test will pass once #3112 is updated and merged.

@williamcroberts @idesai does "make distcheck" [here](https://github.com/tpm2-software/tpm2-tools/blob/0f11c70f70fe846cef8fe7fed93a66f205fd0e9b/.ci/docker.run#L58) force the documentation to be generated? I was expecting the build to not generate documentation if pandoc isn't present, however, the build errors out...

> Yes distcheck requires pandoc as it's a dist sub-command and to make the distribution tarball you need pandoc. I'm removing pandoc from the build in order to speed it...

The build is now failing due to integration tests [here](https://github.com/malikabhi05/tpm2-tools/blob/1b940000536268059e46dd82e5d3e80f840a1481/.ci/docker.run#L95). I keep on seeing the error `Could not start simulator at port`. Do the integration tests have to be run...