Forum Replies Created
-
Posts
-
I uploaded a project where I selected the LED blink example provided by visualgdb, but the compiler selected at the beginning is the mentioned arm-none-eabi-gcc 4.8.3, and this fails to build. as described in the original post.
Oh I would, but there is no project, I don’t get through the project creation wizard. When I hit “next” after selecting the MCU, it does this toolchain check, which fails.
I meanwhle installed the newest arm-none-eabi gcc, 5.4, this now gives a different error in the toolchain check: command not found (or similar, I translated) and then shows the path to the gcc install folder as the “command” – but only up to the bin folder, not an executable, in the “importing specs” step:Tool arguments: -x c++ -dM -v -E – -ggdb -ffunction-sections -fno-exceptions -fno-rtti -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -DARM_MATH_CM4 -DSTM32L476RG -I.
Well I also tried the 4.9 version of the toolchain to no avail.
The ones you pointed to are the eabi ones, I am required to use none-eabi.
I have no detailed knowledge of how this works, but have read that the eabi one actually expects a OS (not just some minimal RTOS) being present ( like described here: https://community.arm.com/thread/8672 ), which now puzzles me, as that’s not quite the case on typical Cortex M projects, certainly not mine. Could you shed light on this with regards to the VisualGDB embedded default compiler choice?
Anyway, the none-eabi is what an existing system uses (based on cmake scripts), and I’m tasked to get that working with VisualGDB, I can’t just use any other compiler version. (actually there is different code output and behavior somewhere around the GCC 4.8 versions, concerning TLS variables, producing a difference of firmware works vs. doesn’t)By VFP setting you mean hard vs. soft float? There was a combobox(?) on the VisualGDB wizard page where I selected hard float, which is what the L4 has.
Could you specify what parts of the tool chain this could conflict with? I’m not super experienced with detailed embedded tool chain setup.As a side note, what information does the “get settings from makefile” (or similar) button on the wizard’s manual config page actually read? It did not seem to fill in any of the fields. Perhaps because the makefile is somewhat complex and has sub folders of subprojects with own makefiles?
