[En-Nut-Discussion] STM32L1xx series status

[Ulrich Prinz]

Hi Uwe!

Hmm... I guess your questions where answered, as I stated that the compile
went through perfectly.

The trap I ran into was simple and I started a discussion for it around 5
years ago...
I set up a project-l151 configuration and setup the system to use something
like
nutbld-l151-gcc
nutbld-l151-gcc/lib
and
nutapp-l151-gcc

Then I found some technical issues on the module I used to test so I
brought it to the hardware guys. To do some further tests with NutO/S I
pulled my STM32 NUCLEO board, but it is a L152.
So I created a new project-l152 config and switched to
nutbld-l152-gcc
nutbld-l152-gcc/lib
and
nutapp-l152-gcc

But I probably tested too many things in parallel and messed up uart.c in
nutapp-l152-gcc/uart/
Then the original module came back and I continued to write some lines of
testing code into the l151 (remember the 1 at the end!) but with loading
the project.conf the setup still keeps its settings to run in
*-l152-gcc
After I found out, that editing -l151 doesn't help if the compiler runs in
-l152... Everything went perfectly. I just had to fix two lines in some
nut.conf file to get UART3 for beeing debug output. I will push that after
returning from holidays.

Finally that is the thing I requested 5 years ago: Why can't we add an
option to save the project path in the configuration (even optionally)?
I see that a normal standard project delivered with the package of NutO/S
should work with every configuration, but users of NutO/S do not stay at
using only the projects delivered with the system. They build projects on
top of the system. And I will probably have three different STM32 CPUs in
my next projects, so I have to switch not only the application, but the
complete library path with every project setting.

Kind regards
Ulrich


2014-12-23 20:55 GMT+01:00 Uwe Bonnes <
bon at elektron.ikp.physik.tu-darmstadt.de>:

> Ulrich,
>
> did my mails get trough to you?
>
> I asked you several question, but  _none_  of these questions was replied
> with your spew of mails.
>
> The most important thing:
> - Give me hard facts, so I can reproduce.
>
> And simple things first:
>  Try to compile and run nut/app/uart/uart.c with a nut/conf/*l1*.conf file
>  with minimal changes.
>
> If that doesn't run, send we your changed .conf file.
>
> Bye
>
> --
> Uwe Bonnes                bon at elektron.ikp.physik.tu-darmstadt.de
>
> Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
> --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>