November 19, 2017 at 20:49 #13019
This should normally be fixed by including the script in the template by adding it to the project before exporting it.
However previously you have mentioned that you cannot do this because the build system complains. Please provide us the details on any errors you encounter when you try to add the second script before exporting the template.November 20, 2017 at 16:08 #13026
I added the secondary linker script to my reference project and got the following output:C++1234567891>------ Build started: Project: STM32F4_libOpenCM3, Configuration: Debug VisualGDB ------1>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\link.targets(40,2): warning : Multiple linker script files included in the project. None of them will be used in linking. Please exclude mark the unnecessary ones as 'Excluded from build'1> Linking VisualGDB/Debug/STM32F4_libOpenCM3...1> c:/program files (x86)/gnu tools arm embedded/5.4 2016q3/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe:libopencm3_stm32f4.ld:43: warning: memory region `rom' not declared1> c:/program files (x86)/gnu tools arm embedded/5.4 2016q3/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe:libopencm3_stm32f4.ld:86: warning: memory region `ram' not declared1> ------------------- Memory utilization report -------------------1> Used FLASH: 0 bytes out of 512KB (0%) [-660]1> Used RAM: 0 bytes out of 128KB (0%)========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
November 21, 2017 at 21:36 #13031
- This reply was modified 2 weeks, 5 days ago by support. Reason: formatting
The warning message is actually legitimate: you have included multiple .ld files in your project, but didn’t specify via VisualGDB Project Properties which one is the main one. VisualGDB arbitrarily guesses the first one (and guesses it wrong).
Please specify the linker script explicitly via VisualGDB Project Properties or change the file type of the unused linker script to “Does not participate in build”:November 22, 2017 at 00:51 #13033
Thank you, this solved the build issue with the reference project and I was able to create a project using the generated template.
Please ignore the attached file, it was uploaded in error.
SidNovember 22, 2017 at 17:39 #13043
One small issue that could be improved upon.
Note in my last post I uploaded a screen shot. I did this because when I tried to make a project using my template I was told to select a tool chain, even though the wizard had selected the right one. The screen shot shows that.
I found that if I selected another toolchain then went back to the correct one the error went away, I did not realize this was the case so I changed my post to say it was working.
This morning I tried the wizard again and got the same effect, it was resolved using the procedure I just described.
Not a huge problem but one that may confuse others.
SidNovember 27, 2017 at 06:26 #13077
Sorry for the delayed reply. We have tried reproducing this with different toolchains and device settings, but could not get any similar behavior. Please ensure that you are using the latest VisualGDB 5.3R6. Please also feel free to share your template file with us. As it looks like a VisualGDB bug, we will be happy to fix it if we can reproduce the problem on our side.December 3, 2017 at 02:13 #13138
My turn to be slow responding. Attached is the custom template for your testing.
SidDecember 3, 2017 at 02:15 #13139
Once again your server rejected my file …December 3, 2017 at 06:10 #13141
Thanks, we have tried reproducing this with your template file, but unfortunately could not get anything similar. Most likely the problem is caused by some combination of installed/referenced toolchain versions. If this is too annoying, we can add extra diagnostic logging to the logic responsible for the toolchain selection, so it will explain what is causing this with your setup. Let us know if you would like to try it out.December 8, 2017 at 17:29 #13201
Thanks, it is annoying but not a show stopper. I would be happy to work with you to trace the issue if you would like,
You must be logged in to reply to this topic.