sidprice

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 126 total)
  • Author
    Posts
  • in reply to: Custom Template Exception #13043
    sidprice
    Participant

    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.

    Thanks,

    Sid

    in reply to: Custom Template Exception #13033
    sidprice
    Participant

    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.

    Sid

     

    • This reply was modified 6 years, 5 months ago by sidprice.
    • This reply was modified 6 years, 5 months ago by sidprice.
    Attachments:
    You must be logged in to view attached files.
    in reply to: Custom Template Exception #13026
    sidprice
    Participant

    I added the secondary linker script to my reference project and got the following output:

    1>------ 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 declared
     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:86: warning: memory region `ram' not declared
     1> ------------------- 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 ==========

     

    • This reply was modified 6 years, 5 months ago by support. Reason: formatting
    in reply to: Custom Template Exception #13013
    sidprice
    Participant

    The secondary linker script is not found because it is not included in the custom template.

    Sid

    in reply to: Custom Template Exception #13010
    sidprice
    Participant

    I thought I had explained this …

    For example, I have a linker script file that is included by the main linker script. If I add this secondary script file to the project the build fails. If I exclude it from the project then the template GUI does not include in in the template

    The file I have trouble with is a secondary linker script. It is located in the project folder. It CAN NOT be added to the project or the build system complains. This file is included by the primary linker script.

    Sid

    in reply to: Custom Template Exception #13006
    sidprice
    Participant

    I would LOVE to use the template GUI in VGDB, however the GUI approach appears incomplete if there are files that are required by the project but that are NOT included in the project.

    For example, I have a linker script file that is included by the main linker script. If I add this secondary script file to the project the build fails. If I exclude it from the project then the template GUI does not include in in the template. Note that with VS2015 I do not see an option to “Exclude from build” only “Exclude from Project.”

    The only way I find to work around this is to have the secondary file as a part of the project, do the template export, create a new project from the template and then remove the file from the project. It would be so nice if the export GUI presented an interface to add additional files.

    Sid

    in reply to: Custom Template Exception #12995
    sidprice
    Participant

    I am more than comfortable “hacking” template files given the correct information.

    In reply to my question; Please can you confirm if the template allows for content in sub-folders … you wrote “You can add subfolders to the template file as long as you don’t move other files inside it”

    I did not move any files into the sub-folders I created that were a part of the VGDB template, I only added the files I needed.

    So, can sub-folders have content (including otehr sub-folders) inside them?

    Second point, the original template I tried was generated from a project that had all the files and sub-folders I needed in the template, however, the template did not have those sub-folders or files included. You then told me to add them manually, which I did.

    Please clarify what may or may not be added to the template, any file in the generated template being left where it is.

    Sid

    in reply to: Custom Template Exception #12986
    sidprice
    Participant

    Please can you confirm if the template allows for content in sub-folders. I need to have some files in my template that are not in the project root.

    Thanks,

    Sid

    in reply to: Custom Template Exception #12975
    sidprice
    Participant

    So I can’t have files in sub-folders in a template?

    Sid

    in reply to: Linker fails after update to gcc arm 7.2.0 #12973
    sidprice
    Participant

    I found how to update the toolchain and also an additional “,” in the linker opitons, now my project builds fine with the new toolchain. Many thanks.

    Sid

    in reply to: Linker fails after update to gcc arm 7.2.0 #12972
    sidprice
    Participant

    Thanks, does this mean I can update the toolchain? If so how do I get VGDB to do that,

    Sid

    in reply to: Custom Template Exception #12970
    sidprice
    Participant

    Thanks that fixed the exception, however I needed to add some extra files to the template and after I edited it to add those I get a new exception:

    VisualGDB version: 5.3.16.1925
    —————— System.Exception ——————
    System.Exception: Invalid project template file
    at VisualGDB.Backend.UserProjectTemplate.FromPackage(String fn)
    at VisualGDB.WPF.Wizards.Embedded.EmbeddedProjectTypePage.ControllerImpl.CommitPage(m commitMode)
    at v6.i_2(m a)
    at xc1.l1(Int32 a

    The edited template is attached,

    Sid

    Attachments:
    You must be logged in to view attached files.
    in reply to: Custom Template Exception #12966
    sidprice
    Participant

    Seems your server didn’t like my file, trying as a ZIP file.

    Sid

    Attachments:
    You must be logged in to view attached files.
    in reply to: Linker fails after update to gcc arm 7.2.0 #12964
    sidprice
    Participant

    Since I need to make progress on my project I switched back to the previous toolchain and my project now compiles.  More than a little worrying that there is some incompatibility between my solution and the new toolchain.

     

    even more concerning is that it seems almost impossible to debug the problem :{

    Sid

    in reply to: Linker fails after update to gcc arm 7.2.0 #12963
    sidprice
    Participant

    Just not getting anywhere with this. I have removed the options one-at-a-time and I still see the same error.

    Sid

Viewing 15 posts - 46 through 60 (of 126 total)