Hi Neo,
Looking at the configuration you provide, it's hard to tell exactly what is the
problem. How did you configure the clock for APB1 and APB2 in periph.conf ?
If you set them to use highest speed (32MHz for this MCU), then the
spi_divtable is wrong and you can reuse the values used for
Hello Alex, thank you for your answer. I configure APB1 and 2 to work at 8Mhz
because my attached device is slow. The values of the spi_divtable were new
calculated via the spi_divtable tool. I wanted just know if spi was tested with
the L073...
Regards, Neo
RIOT OS kernel developers schrieb:
Hey,
On 04/17/2017 04:47 PM, Jose Alamos wrote:
I noticed the 'make flash' recompiles everything before flashing. What's
the reason behind this?
Does it actually recompile?
The flash target in Makefile.include depends on the "all" target,
ensuring that the build is up-to-date. I guess at
Dear researching IOTlers,
please find below a call for papers for Special Issue in Elsevier Future
Generation Computer Systems Journal that might be interesting for some of you.
Apologies if you receive multiple copies of this announcement.
---
CALL FOR PAPERS
Special
Hi!
On Tue, Apr 18, 2017 at 10:12:13AM +0200, Kaspar Schleiser wrote:
> On 04/17/2017 04:47 PM, Jose Alamos wrote:
> > I noticed the 'make flash' recompiles everything before flashing. What's
> > the reason behind this?
>
> Does it actually recompile?
>
> The flash target in Makefile.include
Hey,
On 04/18/2017 10:15 AM, Oleg Hahm wrote:
I remember that (years ago) I thought that this would be a bad idea, but got
overruled.
Probably the newbie friendlyness is to be blamed...
Anyhow, I have a branch for on-hardware CI testing, where I've added
another flash target that doesn't
Dear fellow RIOT'ers,
I've just created the 2017.04 branch and tagged the first release
candidate [1], which means we're now in feature freeze.
Theres an issue for tracking the testing progress at [2]. Any help is
highly appreciated!
Best regards,
Kaspar
[1]
