Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
nucleo-32 STM32L432 woking example
#1
Hi All,

If somebody has a working simple EmBitz project for the
nucleo-32 STM32L432 and can share it?

Great thanks in advance,

vdaniel
Reply
#2
I am examining the startup_stml432xx.o with the objdump.exe. It is correct.
But when I examine the .elf file, I see instead the first (correct) command:

00000000 <Reset_Handler>:
   0:    f8df d034     ldr.w    sp, [pc, #52]    ; 38 <LoopForever+0x2>
 
in the .elf file:
0800018c <__do_global_dtors_aux>:

 800018c:    b510          push    {r4, lr}

I try both linker files STM32L432KC_FLASH.ld (Generated by STM32CubeMX V 4.20.0) and
the STM32L432KCUx_FLASH.ld from the STM32Cube_FW_L4_V1.7.0 Repository.
Result is the same.


I have attache the project.

Please, help me, to understand what is happening and how to get correct result.
Great thanks,

vdaniel


Attached Files
.zip   l.zip (Size: 873.69 KB / Downloads: 72)
Reply
#3
Dear Varuzhan,

I do not have at hand the nucleo board but maybe in the discussion one would be able to find the problem. Is the problem in USART which does not work?


To generate the full listing one can use the "-D" flag with objdump.exe instead of "-d". The "objdump.exe -D" gives the address of Reset_Handler at 0x8000004 (i.e. 08001ebd). Then one can see the following line at Reset_Handler part:

08001ebc <Reset_Handler>:
8001ebc:    f8df d034     ldr.w    sp, [pc, #52]    ; 8001ef4 <LoopForever+0x2>

Which is the same as the one seen in the startup_stml432xx.o (your previous post). Probably it is not the reset vector part in the ELF file which causes the problem.
When I use EmBitz 0.42 instead of 1.11 to build your project I get rather different ELF files. In my projects I use 0.42 because the code generated with 1.11 does not work for me (something wrong with the compiler).

One could probably try to use EmBitz 0.42 to build the project.
Please let me know if building with 0.42 does not help.


Sincerely,
Davit
Reply
#4
Dear David,

Thank you very much.  I tried with EmBitz 0.42.  The same.
Debugger does not "Run to main()" and hangs.  When I load the Release .hex using
the ST-LINK Utility it again does not work.

vdaniel
Reply
#5
Hi,

I'm busy with a STM32L432 Nucleo and I'm in the middle of the flashing routines. I hope to finish it this weekend, I was away for a couple of days.

It's such a mess with STmicro flashing between different devices, no consistency at all. A vendor like Silabs does a much better job.
Reply
#6
(03-10-2017, 05:28 PM)EmBitz Wrote: Hi,

I'm busy with a STM32L432 Nucleo and I'm in the middle of the flashing routines. I hope to finish it this weekend, I was away for a couple of days.

It's such a mess with STmicro flashing between different devices, no consistency at all. A vendor like Silabs does a much better job.

Dear Gerard,

As it was not completely clear from your post could you please comment whether one can run STM32L432 with EmBitz or one should first wait for your changes?

Thanks a lot in advance.
Reply
#7
Dear EmBitz,

Do you have any news about STM32L432?

Thank you,

vdaniel
Reply
#8
Hi EmBitz,

Do you have any news about STM32L432 working project?
More than a month ago you promised to solve the problem.
But it is not even in the tickets list.

Best regards,

vdaniel
Reply
#9
Dear EmBitz,

I am glad to see that you are back to forum.
Please, can you consider now to solve the problem with STM32L432?
Thank you very much,

vdaniel
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)