Sherlock

Forum Replies Created

Viewing 6 posts - 31 through 36 (of 36 total)
  • Author
    Posts
  • in reply to: Overview of project structure #27470
    Sherlock
    Participant

    Hi, OK that helps me actually, so the contents of Device-specific files folders are never intended to be manipulated by the developer.

    So there’s never a situation where I’d need to include some additional STM32 header in my source file and that include file would not already be present in the Device-specific files header section?

    Every include file I’d ever need to leverage any aspect of HAL should already be present in the Device-specific folders?

    Thanks

     

    in reply to: Can others get this to build? #27144
    Sherlock
    Participant

    This is resolved, it was caused by me assuming I could freely leverage the std periph library within a project initially created for HAL.

    in reply to: How to find required library source/header #27130
    Sherlock
    Participant

    OK understood, I have now posted this as a question on the STM forum site along with details of a public GitHub repo that contains the (unbuildable) project.

    https://community.st.com/s/group/0F90X000000AXsASAW/stm32-mcus

    Thanks.

     

    • This reply was modified 6 years, 5 months ago by Sherlock.
    in reply to: How to find required library source/header #27128
    Sherlock
    Participant

    But I though my purchase included support? I just paid for the Custom Edition last week!

    Thanks,

    Hugh

     

     

    in reply to: How to find required library source/header #27126
    Sherlock
    Participant

    But surely this is something you understand? what would you do to resolve this kind of issue?

    in reply to: Link errors for RCC_GetClocksFreq #27054
    Sherlock
    Participant

    Hi, OK I’ve done as you suggested and started discussing this on the STM32 site.

    However I wonder if I’m doing something wrong here.

    In order to call RCC_GetClocksFreq I searched the web for info to get the name of the .h file that declares this function.

    I found that it was in stm32f4xx_rcc.h and simply embedded the include for that into my source – but was that wrong?

    Should I add these files and their sources into the solution explorer?

    I can see that the project (as created when I created the new VisualGDB project) has solution explorer folders like Device-specific files and LL and so on, should I be adding files to the project by adding them to solution explorer?

    How would one typically go about adding a call to a function that’s not defined in any of the headers currently being included in my mainapp.c file?

    Is there any documentation about how to do these kinds of project tasks with VisualGDB?

    Thanks

     

     

     

     

    • This reply was modified 6 years, 5 months ago by Sherlock.
    • This reply was modified 6 years, 5 months ago by Sherlock.
    • This reply was modified 6 years, 5 months ago by Sherlock.
    • This reply was modified 6 years, 5 months ago by Sherlock.
Viewing 6 posts - 31 through 36 (of 36 total)