Group Actions
Engagement
  • Author Author: Digimorf
  • Date Created: Date Created
  • Views 393 views
  • Likes 7 likes
  • Comments 3 comments
Related
Recommended

ATCDC: Digimorf, Day 30, The project SEGA SG-1000 Emulator on PSoC62S4 Pioneer kit - part 7

Digimorf
ATCDC: Digimorf, Day 30, The project SEGA SG-1000 Emulator on PSoC62S4 Pioneer kit - part 7

WOW, almost one month passed since this challenge started and I must say that I like this PSoC62. But, like any other new adventure, there are many new things to learn, and the road to the "FINISH" line fills up with traffic lights. 

Now, it's about time to tidy up a bit the source code. Both cores need to access some common structures since I reserved a portion of SRAM as shared. The need is to create a common include folder for all those functions, macros, and definitions used by both cores.

As soon as the dual-core project is created the properties of the project and the make files are generated by the project creator, and in the project properties/build options, I see that the make file is not auto-generated. That makes sense, but what if I want to include my own external library? Usually, in Eclipse I have to add the folders/files to be included in the project within the "Tool settings":

image

But this tab only appears when the make file is auto-generated. OK, but if I enable the auto-generation the make files generated by the project creator are overwritten, and the compilation fails.

That said, I have to add includes and sources inside the make files, one by one, and add more when I write new ones inside my library. My question is if there is a smart way to include a folder with includes and sources in a dual-core project.

So now, I am stuck with creating my own library and adding it to my project somehow. Plan "B" is to replicate the same library in both projects, but of course, it's not elegant, moreover every time I modify something in the source code I have to update it in both projects.

I have the feeling that actually Eclipse is not really supported as it should be (like the problem of the cm0+ interrupts multiplexing in a dual-core project). Maybe is this a transition time from PSoC creator and Modustoolbox? I Don't know, but I think that the library manager should include an option for including a personal library in the mtb-shared project, and make it available for both cores.        

Anyway, there's always a way out.

  • ClarkJarvis-Infineon and jking,

    thank you for the precious help. I am sure this will be useful to all challengers!

  • Hi  

    I have been using Make and makefiles for a very long time. As you mentioned you have to add includes and sources inside the makefile. However here is an automated way to do this: the compiler will spit out the dependencies and you can then include these in your makefile, hence (once this is set up) you don't have to manually add dependencies every time you add a new .h file. Take a look here: https://www.gnu.org/software/make/manual/html_node/Automatic-Prerequisites.html 

    Hope this helps.

  • Digimorf,

    Regarding the additional include folders and shared folders across applications.

    ModusToolbox is designed to work with various IDEs or using just the command-line.  To ensure as much consistency and compatibility across these different development flows, ModusToolbox uses make files to inplement the build system.  It does not leverage (or sync with) the Eclipse IDE project settings panel.

    The Makefile that is included in your respective project folders is the location to specify additional source and/or include directories.

    You can refer specifically to section 4.6 and the table in section 4.9.2 of the ModusToolbox User Guide for specifics.

    A typically use case is for header files to be shared and source files to be unique to a particular core.  Are you needing to share source files as well?

    The Makefile SOURCE variable is setup to include individual source files, while the INCLUDES variable will accept folders.

    image

    image