Hi all,
I want to ask why the ltc4150 driver was removed( I will need to use it
and I would like to know if I should do any modifications on the existing
code for the ltc4150). Or is there any other new driver supported by RIOT
for coulomb counting or voltage meter?
Thank you in advance!
Best
Ok, the code removed is totaly useless or are there any parts that I can
use?(Just a question before I go over the datasheet of the ltc4150). I will
try to fix it as soon as possible, I dont know if there should also be a
PR, because with the ltc4150 device we can estimate the battery level of a
Hi Ilias,
On 02/20/2017 02:07 PM, Ilias Seitanidis wrote:
> I want to ask why the ltc4150 driver was removed( I will need to use it
> and I would like to know if I should do any modifications on the
> existing code for the ltc4150). Or is there any other new driver
> supported by RIOT for
Hi Anthony,
On 02/14/2017 03:56 PM, Anthony Merlino wrote:
> I am in the process of writing a radio driver for a device I'm working
> with. The device is highly configurable and I am trying to identify the
> best strategy for exposing some of the configuration to the user. For
> example, the
Hi everyone
While working with low-power modes on STM32L1, we found a bug (?) in gcc
with -Os optimization - somehow it "optimizes" rather simple
periph_clk_en(bus_t bus, uint32_t mask) function in
cpu/stm32_common/cpu_common.c, so using it right after waking up from STOP
mode results in Hard
Dear RIOTers,
for the next release, we've decided to shorten the merge window for
"high impact"-changes.
Previously, we've tried hard to finish up even complex changes (like the
just released SPI rework) in time for a release. That lead to code
touching many configurations but getting only two
