Hi all
I've raised an issue for my initial concept for the HIL testing of the
UART driver: https://github.com/RIOT-OS/RIOT/issues/8184.
I'm going to start on it immediately in order to go ahead with issue
https://github.com/RIOT-OS/RIOT/issues/7941. All comments and input
would be gratefully rece
Hi Peter,
I think definition/implementation of a I2C slave interface/drivers is
still wanted. But I found, that for the presented HIL use-case, a custom
pin-banging i2c slave mock-up implementation is better suited, as it
further allows us to intentionally trigger faulty bus behavior (not
rel
Hi
> thanks for you efforts! This is great and really useful work. IMO it is
> the right direction, even though I always hoped to find a way around
> implementing our own I2C slave device. That's why I wanted to take this
> opportunity to ask around for other experiences with I2C (slave) test
> de
Hi Hauke,
thanks for you efforts! This is great and really useful work. IMO it is
the right direction, even though I always hoped to find a way around
implementing our own I2C slave device. That's why I wanted to take this
opportunity to ask around for other experiences with I2C (slave) test
devic
Hi everyone,
in today's developer meeting the discussion passed by the topic of HIL
testing once again, this time in the context of the upcoming re-modeling
of the I2C interface. Some weeks ago I had an idea for a simple HIL
setup for automatically testing perihp/i2c drivers, and I promised to
