Kasper de Vries

> * Is the board natively supporting I2C? > * Is the same board working for example with any other technology? Including on a Raspberry Pi with .NET IoT for...

> Do you have a link on the datasheet of your custom board? I can try to help understanding the pin out. It's quite sensitive, I've been there in the...

> Then it's quite hard to help you more than what I already wrote :-( Sorry about that. The PN532 works for me on nano (at least last time I...

I tried writing a small program in both C and with nF that reads the version info to give better insight into my issue. ### In C The Program I...

It either doesnt reach the exception or it does work because the exception never gets hit.

@josesimoes @Ellerbach That comparison is not where the issue lies the I2C bus gets pulled low and the mcu locks up before we ever get to that comparison.

@Ellerbach I removed the comparison and it worked then, however there is an issue with the I2C device when an exception is thrown. This is an issue seemingly unrelated to...

and also: why does my bit of code work but the Iot.Device driver doesn't.

What I found when investigating the Pn532 driver code was that the read at: https://github.com/nanoframework/nanoFramework.IoT.Device/blob/0d1d97db4da3e306349724d369fd477fa4701055/devices/Pn532/Pn532.cs#L2067-L2070 keeps the clock low as shown:  Why this happens I do not know, however...

According to the build there are currently 699 public-facing things that need to be commented. I think it would be best if we minimize the interface as much as possible....