Ds18 driver doesn't work on ESP32 - gpio_init slow

Development Drivers
#1

Hi,

I’m just getting started with RIOT-OS and picked up an ESP32-WROOM-32 board. I had a DS18b20 so I thought that would be a good first project. No such luck!

I’ve been playing around with this for a few days and have come to the conclusion that there is just a lot of latency when doing gpio_init() to switch from GPIO_OD to GPIO_IN. So much, in fact, that there is no way to write a “1” to the bus successfully.

In ds18_write_bit(), to write a 1, ds18_low() (open drain, pull low) is called, immediately followed by ds18_release() (set GPIO to input). This takes about 40us according to my oscilloscope. This needs to happen in 10us-15us.

Am I missing anything? I’ve followed through the gpio_init() calls and then end up in the ESP32 SDK.

Thanks, mh

1 Like
#2

@kfessel is familiar with protocol. I do believe that the new GPIO LL API may be helpful here, but I have to admit that I never even looked into the protocol.

GPIO LL is already supported by ESP and (in addition to having lower overhead) has defined semantics regarding Open-Drain, in that reading from open drain pins must not merely mirror the output state, but actually reflect the logic level on the pin. (E.g. I2C clock stretching is possible to implement in software with GPIO LL, while it is not with periph_gpio.)

#3

Also, the esp32 uses the esp-idf-api which may be why things are so slow (just a guess). Generally we don’t try to optimize the init as much as the writing and reading but I believe if you use a different vendor that doesn’t require external APIs (st or microchip) might be a quick way to get the speed required.

There is a cost for abstraction…