debuggin OutOfBox_FR4133 4 errors

Hi William!

Your compiler tells you that it doesn't know LCDMEMW / LCDBMEM which seem to be #defines somewhere in your code (or should be). Further these #defines seem to be arrays.

Maybe there is a missing #include in which these defines are made.

Just had a look at the source files for that board. These definitions are in the hal_LCD.h and refer to the msp430fr4133.h - which compiler do you use? Have you included all files into your program?

Dennis

My soft it is Code Composer Studio Version 6.0.1.00040 ok.

In hal_LCD.h y have         include msp430fr4133.h            ok .

Y include all files y see in the  zip demo  ok.

Y go to see msp430fr4133.h into for see is include LCDMEMW   and LCDBMEM . 

Y don now if we need to put in the tree  msp430fr4133.h or directly hal_LCD.h refer direct ok.

When  y debug y put direct referens  msp430fr4133 it is the ic we see in the launch pad kit ok  

y wait your reply and thank you for your help me im new few day im recive the kit and they work nice 

and second y put others demos and work nice and these kit  open a lot  of way for make nice proyect .

But y like to put one more time first demo come with launch pad ok . 

Y go to see the msp430fr4133.h what is into these file ok . 

We continues with these littly problem or you speak with Mr E Chen who resamble make these nice demo

clock wach and Temp Sensor ok.

And finaly y need to put in the tree olso msp430fr4133.h  ??? 

Ok y wait your reply and y like do you help me in these new kit nice kit because they have led display wow . 

In the future y go to buy other items y see in the ti shop ok .All for msp430fr series ok .

Hi William,

It seems that  hal_LCD.h is not included in main.c or StopWatchMode.c. Could you please check this?

Best Regards,
Darren Lu

hellow thank you for you reply me 

and               hal_LCD.h it is include in main.c     ok .

and    it is                                include StopWatchMode.h     ok.

We need to include StopWatchMode.c olso ?????? remember (c) not (h) yes i need to include a not header file ??

Into the file main.c ???????

We need to  talk with Mr E Chen who make these soft maybe yes !!.????.

Y like a lot of you help me in these nice software y make a lot of other sample and working nice .

But now when y like to put these nice soft demo y debug and y have these errors ok 

Y wait now your reply ok 

Main.c      line 306 ( in red color ) #20 identifier "lcdbmem" is undefined and speak  C/C++ problem  

// Use LCD Blink memory to pause/resume stopwatch at split time
LCDBMEMW[pos1/2] = LCDMEMW[pos1/2];
LCDBMEMW[pos2/2] = LCDMEMW[pos2/2];
LCDBMEMW[pos3/2] = LCDMEMW[pos3/2];
LCDBMEMW[pos4/2] = LCDMEMW[pos4/2];
LCDBMEMW[pos5/2] = LCDMEMW[pos5/2];
LCDBMEMW[pos6/2] = LCDMEMW[pos6/2];
LCDBMEMW[12/2] = LCDMEMW[12/2];

StopWachMode.c      line 196 (in red color )   #20 identifier "lcdbmem" is undefined and speak  C/C++ problem   

                                      line  201(in red color )   #20 identifier "lcdbmem" is undefined and speak  C/C++ problem

                                      line  206(in red color )   #20 identifier "lcdbmem" is undefined and speak  C/C++ problem

// Blink Stopwatch symbol
if ((*Centiseconds) == 0)
{
LCDMEM[12] |= 0x08;
LCDBMEM[12] |= 0x08;
}
if ((*Centiseconds) == 50)
{
LCDMEM[12] &= ~0x08;
LCDBMEM[12] &= ~0x08;
}

// Display the 2 colons
LCDMEM[7] |= 0x04;
LCDBMEM[7] |= 0x04;
LCDMEM[11] |= 0x04;
LCDBMEM[11] |= 0x04;
#endif

Ok do you see please the soft and you reply me what s the problem ok 

Y dont now if the soft have another release all these are  bugs  all that  ydont now ok ??.

When y put other demos y lost the first demos come with the launchpad development kit MSP430FR4133.

Y see these demo in yours web page a zip file OutOfBox_FR4133 and y download and y Build and y have these four 4 bugs ok . 

Y wait your reply  ok . The kit working nice with other demos and one littly proyect y make ok .

Y wait your reply ok and thank you for you help me ok 

Finaly y speak you,my soft it is: 

My soft it is Code Composer Studio Version 6.0.1.00040 ok.

 Maybe the OutOfBock sample come build with other Version ????

Y speak that because some soft when change the Version dont build and debug nice ok . 

It is that why im speak that for you ok .

And one more time y thank you  for your time  for help me ok 

William 

Y see the binary file into the zip files  and y load into the kit   OutOfBox_Fr4133  and charge nice and then they

 speak mi do you y like to upload a new firware for the MSP430fra133 launchpad developemnt kit and y put yes and then  hurra the soft working demos working fine and good ok..

They working fine and good the demo OutOfBox_Fr4133  temp sensor  and stop wach clock counter ok. 

But source file into the Code composer dont debug and of course dont relice nothing 

May be my Code Composer is free and dont have all the tools ??? it is that . 

Y need to buy full code composer for the source compile nice  y dont now . 

Y say the kit working nice binary code load nice and firware come las relice ok .

But what happening with the source mmmmmmmm??????

Ok y wait your reply ok 

And thank you for help me ok 

William 

For instance the binary file come into the zip y load into the kit and working nice and then olso they upgrade the firware of the kit  y have one more time the wach and temp sensor first demo they come with the kit 

MSP430FR4133Launchpad dvelopment kit . 

But source dont work fine ok . 

One guy from It employe help me . 

Y dont now it the problem is my Code Composer free maybe y have not all the options .

Maybe y  need to buy full Code Composer  ok y dont now 

Y say the kit working fine and y put other demos and littly proyect by me and working fine .

And y working with the Code Composer and the debug and relice nice the source code ok .

Y wait what happening . 

But y like do you help me and y like you say the source code working fine nice and good all .

But  y need to say whay dont build nice and y have these 4 herrors ok .

Thank you for instance ok 

we talk next week now holyday saturday tomorrow ok .

bybyyb

Hi William,

Could you please check the #define __MSP430_HEADER_VERSION__ in your msp430fr4133.h

You may need to install the latest msp430 related updates by going to:

Help -> Check for Updates -> install

After updates are finished, try a Rebuild Project and see if the problem persists. My msp430fr4133.h contains #define __MSP430_HEADER_VERSION__ 1153, and the project builds fine.

Best Regards,
E. Chen

Hellow Mr Chen thank you for your help me .

Now today im going to make what do you put in your replyñ  ok.

Y remember you binary file working nice and good into the kit ok.

Y go to check the #define-MSP430_HEADER_VERSION in my msp430fr4133.h pl 

and updates  ok . 

i go tu used the chip set for robotic sistem for help peoples . It is a nice proyect ok 

Not only these chip but a lot of chips and powers systems and pap motors ok .

Y like these chip y studie all about these chip y have all pdf do you put in the web page ok . 

And wait my next email for say if woriking nice your program 

Thank you for instance wait wait ok .

Hellow y check for udpates and y clik  install ok . 

but my relice about msp430fr4133.h  is #define __MSP430_HEADER_VERSION__ 1139 ok

Your relice is 1153 ok .

But nothing change  ok . 

what y need to make ? for resolve these littly problem .

Y MAKE 3 TIMES UDAPTES ONE INSTALL THE NEWS FILES . 

THE OTHER 2 TIMES NOTHng  FOR INSTALL ALL ARE instaled  OK .

WHAT Y NEED TO MAKE NOW ????

Y remember you my soft is:

Version: 6.0.1.00040   ok.

THESE IS WHAT IS INSTALED IN THE SOFT  ok   :

Analysis Suite 4.0.0.201407021231 com.ti.dvt2.analysis.suite.feature.group Texas Instruments
ARM Compiler Tools 5.1.8 com.ti.cgt.tms470.5.1.win32.feature.group Texas Instruments
Blackhawk Emulators 6.0.0.344 com.bh.ccstudio.emulation.win32.feature.group Texas Instruments
C/C++ Development Tools 8.2.1.201309180223 org.eclipse.cdt.feature.group Eclipse CDT
C/C++ GCC Cross Compiler Support 1.2.0.201309180223 org.eclipse.cdt.build.crossgcc.feature.group Eclipse CDT
C/C++ Memory View Enhancements 2.2.0.201309180223 org.eclipse.cdt.debug.ui.memory.feature.group Eclipse CDT
C/C++ Remote Launch 6.2.0.201309180223 org.eclipse.cdt.launch.remote.feature.group Eclipse CDT
C2000 Compiler v6.2 Help 6.2.0.201306250915 com.ti.cgt.c2000.6.2.help.feature.group Texas Instruments
C2000 Emulation Flash 1.0.0.2 com.ti.c2800.flash.feature.group Texas Instruments
C2800 Compiler Tools 6.2.9 com.ti.cgt.c2000.6.2.win32.feature.group Texas Instruments
CC13xx/CC26xx Device Support 1.12.0.00 com.ti.ccstudio.cc26xx.devicesupport.win32.feature.group Texas Instruments
CC2538 Device Support 1.30.10.00 com.ti.ccstudio.cc2538.devicesupport.win32.feature.group Texas Instruments
CC3200 Device Support 1.0.0.4 com.ti.ccstudio.cc3200.devicesupport.win32.feature.group Texas Instruments
CCS and SAT Common Components Feature 6.0.1.201406261800 com.ti.tools.common.feature.group Texas Instruments
CCS Documentation 6.0.0.20140715 com.ti.ccstudio.doc.win32.feature.group Texas Instruments
CCS Launcher 6.0.0.20140528 com.ti.ccstudio.launcher.win32.feature.group Texas Instruments
CCS Utilities 1.0.0.20140314 com.ti.ccstudio.utils.cli.win32.feature.group Texas Instruments
CCStudio p2 Tool Feature 6.0.0.201403261708 com.ti.ccstudio.p2tool.feature.group Texas Instruments
Chromium Browser Feature 6.0.1.201406261800 com.ti.chromium.browser.feature.group Texas Instruments
Code Composer Studio Base Components 6.0.0.00698 com.ti.ccstudio.base.feature.group Texas Instruments
Code Composer Studio IDE ARM Components 5.3.0.201406261800 com.ti.ccstudio.tms470.feature.group Texas Instruments
Code Composer Studio IDE C2000 Components 6.0.1.201406261800 com.ti.ccstudio.c2000.feature.group Texas Instruments
Code Composer Studio IDE Main Feature 6.0.1.201406261800 com.ti.ccstudio.idemain.feature.group Texas Instruments
Code Composer Studio IDE MSP430 Components 6.0.1.201406261800 com.ti.ccstudio.msp430.feature.group Texas Instruments
Code Composer Studio IDE Workflow 6.0.1.201406261800 com.ti.ccstudio.workflow.feature.group Texas Instruments
Compiler Tools On-line Documentation 1.1.4 com.ti.cgt.dmed.win32.feature.group Texas Instruments
Debug Server 6.0.0.698 com.ti.ccstudio.debugserver.win32.feature.group Texas Instruments
DebugServer Flash 6.0.0.759 com.ti.dsflash.win32.feature.group Texas Instruments
DVT - EnergyTrace 4.0.0.201407021231 com.ti.dvt.msp430.power.feature.group Texas Instruments
DVT - Graph Visualization 4.0.0.201407021231 com.ti.dvt2.graph.visualization.feature.group Texas Instruments
DVT - Profiler Analysis Manager 4.0.0.201407021231 com.ti.dvt2.profileanalysismanager.feature.group Texas Instruments
DVT - System Analyzer 4.0.0.201407021231 com.ti.dvt2.uia.feature.group Texas Instruments
DVT - Trace Control 4.0.0.201407021231 com.ti.dvt2.trace.control.feature.group Texas Instruments
Eclipse Git Team Provider 3.0.3.201309161630-r org.eclipse.egit.feature.group Eclipse EGit
Eclipse Help System 2.0.1.v20130911-1000 org.eclipse.help.feature.group Eclipse.org
Eclipse Platform 4.3.1.M20130911-1000 org.eclipse.platform.ide null
Equinox p2 Discovery 1.0.100.v20130502-0334 org.eclipse.equinox.p2.discovery.feature.feature.group Eclipse.org - Equinox
Equinox p2 Provisioning for IDEs. 2.2.0.v20130828-0031 org.eclipse.equinox.p2.user.ui.feature.group Eclipse.org - Equinox
GCC ARM Compiler Tools 4.7.2013.10 com.ti.gcc.arm.win32.feature.group Texas Instruments
Graphical Modeling Framework (GMF) Runtime 1.7.0.201306111432 org.eclipse.gmf.feature.group Eclipse Modeling Project
GUI Composer Backplane Feature 6.0.0.201406261800 com.ti.gc.backplane.feature.group Texas Instruments
GUI Composer Feature 6.0.0.201404071800 com.ti.gc.common.feature.group Texas Instruments
GUI Composer for CCS 1.0.0.201404071800 com.ti.ccstudio.gui.composer.ccs.feature.group Texas Instruments
GUI Composer Program Model Feature 6.0.0.201406261800 com.ti.gc.pm.feature.group Texas Instruments
Hercules Emulation 6.0.5 com.ti.ccstudio.hercules.win32.feature.group Texas Instruments
IDE - Debug Server Integration Feature 6.0.1.201406261800 com.ti.debug.server.feature.group Texas Instruments
Image Analyzer 4.0.0.201407021231 com.ti.dvt2.via.ccs.feature.group Texas Instruments
LWInstaller 6.0.1.00040 com.ti.ccstudio.installer.win32.feature.group Texas Instruments
Marketplace Client 1.2.1.I20130917-2019 org.eclipse.epp.mpc.feature.group Eclipse Packaging Project
MSP430 Compiler Tools 4.3.5 com.ti.cgt.msp430.4.3.win32.feature.group Texas Instruments
MSP430 DriverLib (IDE Client) 1.95.0.49 com.ti.mcu.msp430.driverlib.product.ui.feature.group Texas Instruments Inc.
MSP430 DriverLib (Target Content) 1.95.0.49 com.ti.mcu.msp430.driverlib.product_1.95.0.49.feature.group Texas Instruments Inc.
MSP430 Emulators 6.0.1.2 com.ti.ccstudio.msp430.emu.win32.feature.group Texas Instruments
MSP430 GCC Tools 4.9.1.20140707 com.ti.gcc.msp430.win32.feature.group Texas Instruments
MSP430_CGT_Help_Feature 4.3.0.201401241632 com.ti.cgt.msp430.4.3.help.feature.group null
MSP430ware (IDE Client) 1.95.0.32 com.ti.mcu.msp430ware.product.ui.feature.group Texas Instruments Inc.
MSP430ware (Target Content) 1.95.0.32 com.ti.mcu.msp430ware.product_1.95.0.32.feature.group Texas Instruments Inc.
MSP430Ware for Windows 1.95.0.32 com.ti.msp430.msp430ware.win32.feature.group Texas Instruments
MSVC 2012 Redistributable 11.0.61030 com.ti.ccstudio.installer.msvc.2012.win32.feature.group Texas Instruments
p2appf 6.0.1.201406261800 com.ti.ccstudio.p2appf.feature.group Texas Instruments
Remote System Explorer End-User Runtime 3.5.0.201309112143 org.eclipse.rse.feature.group Eclipse TM Project
ROV 4.0.0.201407021231 com.ti.dvt2.rov.feature.group Texas Instruments
RTSC/XDCtools (IDE Client) 3.30.3.47 org.eclipse.rtsc.xdctools.product.ui.feature.group Texas Instruments
RTSC/XDCtools (Target Runtime Support) 3.30.3.47 org.eclipse.rtsc.xdctools.product_3.30.3.47.feature.group Texas Instruments
RXTX End-User Runtime 2.1.7.4_v20071016-7B57e7UAXMAAqGAGf gnu.io.rxtx.feature.group RXTX.org
Spectrum Digital Emulators 5.2.0.12 com.sd.ccstudio.emulation.win32.feature.group Spectrum Digital
Stellaris Emulators 2.0.3.12770 com.ti.stellaris.setup.win32.feature.group Texas Instruments
Target Management Terminal 3.3.100.201308290741 org.eclipse.tm.terminal.sdk.feature.group Eclipse TM Project
TargetDB Default Props 6.0.0.20131206 com.ti.ccstudio.targetdb.props.default.win32.feature.group Texas Instruments
TI ARM Compiler 5.1 Help 5.1.0.201306281501 com.ti.cgt.arm.5.1.help.feature.group Texas Instruments
TI C2000 Device Support 4.1.3.0 com.ti.c2000.support.win32.feature.group Texas Instruments
TI Emulators 5.1.600.0 com.ti.emulation.pack.win32.feature.group Texas Instruments
TI Target Content 1.0.0.201407041100 com.ti.targetcontent.feature.group Texas Instruments
TI-RTOS for C2000 (IDE Client) 2.0.2.36 com.ti.rtsc.TIRTOSc2000.product.ui.feature.group Texas Instruments
TI-RTOS for C2000 (Target Content) 2.0.2.36 com.ti.rtsc.TIRTOSc2000.product_2.0.2.36.feature.group Texas Instruments
TI-RTOS for C2000 (Target Content) 2.0.2.36 com.ti.rtsc.TIRTOSc2000.product.feature.group Texas Instruments
Tiva C Series ARM MCUs 2.0.3.12770 com.ti.tiva_tm4c.setup.win32.feature.group Texas Instruments
Tiva/Stellaris ICDI Debug Probe 2.0.3.12770 com.ti.tiva_stellaris.setup.win32.feature.group Texas Instruments
Trace Analyzer 4.0.0.201407021231 com.ti.dvt2.trace.ccs.feature.group Texas Instruments

The other way is you put a link for download the new relice ok do you have a link for make that ??

Y remember you  one more time binary file working nice fine and good ok . 

Ok  y wait your reply ok 

And y thank for your time for help me ok ,

William 

Hi William,

The header version 1139 lacks the LCDBMEM definitions that version 1153 contains. it is the root cause of your build errors.

The newer header file should have been installed in the update:
MSP430 Emulators 6.0.1.2 com.ti.ccstudio.msp430.emu.win32.feature.group Texas Instruments

Please check the following file in your CCS installation:
pathToYourCCSInstallation\ccsv6\ccs_base\msp430\include\msp430fr4133.h and make sure it contains LCDBMEM

I've attached the latest header for you to verify: 7002.msp430fr4133.h

Also, make sure to do a Clean Project before building the project again.

Best Regards,
Eric Chen

Unfortunately, it is a quite common practice to split code that needs to be compiled in a whole into multiple files. In these cases, yes, the .c files need to be included into another .c file instead of being compiled individually. Well, it’s better than putting code into .h files. After all, #include just does that: including a text file of arbitrary content into the code file.
I don’t know whether it applies to your specific code.

OK y go to msp430fr4133.h  1133 version and nothing LCDBMEM ok  nothing (nada no hay nada ok ) 

In your       msp430fr4133.h   1153 y see  LCDBMEM ok.

Y make what do you speak me and y change  the old version for your new  version include file y dont now it is correct to make these change one for one ??? ok .

Y  debug and y have other diferents problems ok :

Description Resource Path Location Type
#69-D integer conversion resulted in a change of sign main.c /OutOfBox_FR4133 line 425 C/C++ Problem
unresolved symbol LCDBM0W_L, first referenced in ./StopWatchMode.obj OutOfBox_FR4133 C/C++ Problem
#145-D a value of type "volatile unsigned int *" cannot be used to initialize an entity of type "volatile int *" TempSensorMode.c /OutOfBox_FR4133 line 54 C/C++ Problem
unresolved symbol LCDM0W_L, first referenced in ./StopWatchMode.obj OutOfBox_FR4133 C/C++ Problem
#145-D a value of type "volatile unsigned int *" cannot be used to initialize an entity of type "volatile int *" TempSensorMode.c /OutOfBox_FR4133 line 53 C/C++ Problem
<a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a> unresolved symbols remain OutOfBox_FR4133 C/C++ Problem
#10010 errors encountered during linking; "OutOfBox_FR4133.out" not built OutOfBox_FR4133 C/C++

And now wath we need to make ??

Im sorry for expend your time ok but what happen with these demo ???

Ok y wait your reply ok 

And thank you for your bring your time ok .

Thank you for your help me y like to debug and relice the demo OutOfBox  binary working fine in my kit .

Y speak now with Mr Chen who working in Texas Instrument ok .

Y speak me about the new relice of mcp430fr4133.h  .

But now y have other diferent errors and warning . 

Y workink fine with my kit  and y lose the first demo when y make one littly proyect ok.

Y like to put the demo come with the board  Demo OutOfBox FR4133 y debug the source demo but dont 

working and y have herrors ok and warning ok.

Then y take the binary file and y load the binar file fromOutOfbox Fr4133 and working nice 

The demo working StopWach and Temp Sensor . 

Now y change in include path the new mcp430fr1133.h file and y have news errors and 3 warning ok 

When i debug and olso y update the CCS software ok .

Description Resource Path Location Type
#69-D integer conversion resulted in a change of sign main.c /OutOfBox_FR4133 line 425 C/C++ Problem
unresolved symbol LCDBM0W_L, first referenced in ./StopWatchMode.obj OutOfBox_FR4133 C/C++ Problem
#145-D a value of type "volatile unsigned int *" cannot be used to initialize an entity of type "volatile int *" TempSensorMode.c /OutOfBox_FR4133 line 54 C/C++ Problem
unresolved symbol LCDM0W_L, first referenced in ./StopWatchMode.obj OutOfBox_FR4133 C/C++ Problem
#145-D a value of type "volatile unsigned int *" cannot be used to initialize an entity of type "volatile int *" TempSensorMode.c /OutOfBox_FR4133 line 53 C/C++ Problem
<a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a> unresolved symbols remain OutOfBox_FR4133 C/C++ Problem
#10010 errors encountered during linking; "OutOfBox_FR4133.out" not built OutOfBox_FR4133 C/C++ Problem

Y like you take your time and you speak me about compile problems ok. 

Now y wait the next email from Mr Chen who maybe make the demo all files y see the name of Mr Chen . 

Y  like what do you speak me aobut the all problems in debug and relice these nice sofware . 

Im  very bad because y make other simple proyect and working nice not problems mmm!!!!.

And  y put other demos and working fine .

Wath happening y dont now y wait for see the next email from Mr Chen who working in Texas Instrument .

And you have idea about these problem ?????

Thank you for you expand your time for help me ok .

Willam  

Jens-Michael Gross said:

Of course it is much better to write code so that individual source files are compiled individually, and their interface is exchanged with header files.

One little note to ‘much better’.

In principle I agree with you, functions in separated source files can have their own properties; optimize, speed etc.

But ‘inline’ only works if the function can been seen in the same file, if you need inline (have seen this a couple of times on this forum) it’s not much better.

The to be ‘in lined’ functions might be in a separate file but must be included (#inlude “…”) in the main file and excluded from the project and will be not individual compiled, no own properties. 

Hi William,

Sorry, I was thinking that the MSP430 Emulators 6.0.1.2 was installed correctly on your computer based on the list of installed software you provided, and maybe the project wasn't picking up the updated include files. But it's apparent the new files did not get copied into your CCS.

The new errors you are seeing after replacing the msp430fr4133.h is caused by a mismatch between msp430fr4133.h and msp430fr4133.cmd, which are both part of the many files changed in this software update.

For a quick solution to the build error in this demo project, please back up the old files and copy/replace the following 3 files into this directory on your machine (be sure to remove the numbers preceding the file names):

pathToYourCCSInstallation\ccsv6\ccs_base\msp430\include\

• http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/166/0250.msp430fr4133.cmd
• 8713.msp430fr4133.h
• http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/166/2364.lnk_5F00_msp430fr4133.cmd

Note: This should be only be used as a workaround if the CCS MSP430 Emulators update fails to automatically replace these msp430 include files, since there are many other changes in this update. I would recommend reinstalling CCS and updates, making sure there aren't any install errors.

Best Regards,
Eric Chen

I’ve just had a discussion about inlining in a different thread.

Basically, if you write a function that should/could be inlined, you will write the function declaration and definition in a header file.
If you specify the ‘static’ storage class, each compilation unit that includes this header files will get its own instance of the function, in case the function can’t be inlined. If you mark it ‘extern’, none will.
Personally, I define all inline functions as extern inline (and add the __always_inline__ attribute for GCC), so the function is either inlined or I’ll get a linker error, which will then signal that inlining failed for some reason.
Example: my SPI module, provides functions for initializing SPI, sending or receiving block data using DMA, and for sending/receiving single bytes. Those last functions are declared and defined in the header file as extern inline, as calling them will cause significant overhead. However, if specified with a global flag, the functions are also declared as not extern in the SPI module C file, so in case I need it, this compilation unit will get instances of them. If the compiler supports separate sections for each function in a compilation unit, the global define can be removed - the linker will scrap these functions then when nobody requires them.

 One main reason for having separate compilation units instead of including all source code into one compiler run is the scope. Each compilation unit can have it own set of unit-global variables (declared static). This prevents collisions between different modules when there are variables of the same name but different usage in different code modules. If you join them all, you’ll either get unexplainable behavior or linker errors. (In C++, you could - and should - specify separate namespaces)