[En-Nut-Discussion] STM32L1xx series status
ulrich.prinz at googlemail.com
Wed Dec 17 12:20:45 CET 2014
Nice to hear that there is work in progress. I would love to share some
ideas, we should probably do some hangout session or voicecall an then put
the results in here.
I design a new generation of home automation modules and current drawn is
what counts. So I will start designing on L1 but probably move to L0 as
soon as they are available in a case that matches our needs. 800uA compared
to 400uA is a matter for us.
I am trying to get the STM32L151UCY going and that fails for selection of
the right linker script. If you load the l1_discovery configuration there
is a script set and you can compile some of the demo apps. But I need to
change the chip and the clocks as the chip isn't 32k but 256k Flash and the
clock on our board and the new revisions of NUCLEOs is not 8MHz Xtal at HSE
but soemthing from internal MSI or HSI... Need to check that.
If you then click the linker script, the preset script disappeares and you
cannot select anything else. I am working with qnutconf under Ubuntu
I had the same problems with L152 and other boards. But I gave up testing
all of them. I'd focus a bit on the project and if everything runs fine,
I'll share the benefits with the other devices. I do have a lot of
different kits from ST so I can test a wide range of chips.
2014-12-17 0:54 GMT+01:00 Uwe Bonnes <
bon at elektron.ikp.physik.tu-darmstadt.de>:
> >>>>> "Ulrich" == Ulrich Prinz <ulrich.prinz at googlemail.com> writes:
> Ulrich> After long time no see, a big hello to you all... Nice to see,
> Ulrich> that there are still some old friends active in here.
> Ulrich> I checked out some pretts fresh master from sourceforge and I
> Ulrich> now at trying to get things back working on some STM32F4 and
> Ulrich> STM32L0 and L1 devices.
> Ulrich> Unfortunately there is a lot of incomplete code, missing .nut
> Ulrich> file content and bugs in finding the right linker script for
> Ulrich> STM32L1 device.
> Well, at least the standard configurations in nut/conf concerning L1
> compile. If not, please tell me.
> But bear with me, there are a _lot_ of STM32 devices with a _lot_ of
> and not so subtile differences. I have put a lot of effort to catch most
> difference, at least those I am aware of. Some code pathes may be missing,
> hopefully tagged with a FIXME or a compile time warning. External feedback
> has been low however and non existant on the L1.
> Ulrich> Before I start over and repair all these things, does anyone
> Ulrich> have already some fixes not merged?
> Otherwise, there are not many patches concering especially L1 hanging in my
> git tree. I will try to cherry-pick the sensible ones the next days.
> But DMA and RTC have some rework pending in my tree.
> Pin Setting and configuration needs a major haul-up. I would be glad to
> discuss my ideas with you.
> Ulrich> Is anyone using nutO/S with STM32L devices?
> I had some project with an L152VC for a battery powered device running some
> fast ADC and transfering data via an optical fiber. The device worked on
> high side of a 100 kV supply. However I didn't work on that project for
> time. Most of my other projects now are F3.
> Beside for another battery powered project I now target at the F411. Data
> should be
> looged to flash and read out via Nucleo ACM USB. If you look at F411 run
> sleep currents, it is at least as attractive as L1. Flash and Ram size and
> FPU are a plus with regard to the L1. Standby and Stop current may be a
> little worse, as is availability and small size/price devices. But
> Nucleo-F411 is
> available and cheap.Small size/price devices are not so important for
> our use cases.
> Ulrich> Would be nice to hear from you.
> Vice versa :-)
> Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
> Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
> --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
More information about the En-Nut-Discussion