CUBEMX: How to supress code generation in stm32f4xx_hal_msp.c

HAL_ADC_MspInit() and HAL_ADC_Init() isnt prepared for call directly, Is used from MX func and this can be disabled to call and you can write own, but your idea is closer to LL drivers...

Hi @andywild2​,

The HAL_ADC_MspInit function is created in the stm32f4xx_hal_msp.c file to configure the low-level hardware (GPIO, CLOCK) for ADC peripheral.

Actually what CubeMX assure is the generation of stm32f4xx_hal_msp.c file and not suppressing the code generated in it.

Otherwise, the Advanced Settings Tab in CubeMX interface gives the possibility of choosing not to generate code for some peripherals or middlewares: This automatic initialization code generation can be disabled per peripheral or middleware in the Generate code column:

When the Generate code checkbox is unchecked , void MX_ADC1_Init(void) function will not be generated in main.c file () (or adc.c file will not be generated if the option Generate peripheral initialization as a pair of '.c/.h files per peripheral is checked).

if the Do Not Generate Function Call checkbox is checked, STM32CubeMX does not generate the call to the corresponding MX_ADC1_Init . It is up to the user code to do it.

Hope this answers your question.if this this case, please click on the Select as Best button on my reply . This will help other members of the community find this solution more quickly.

Khouloud.

Hello Khouloud,

Thank you for your reply.

Im not talking about MX_ADC1_Init. It is easy to supress as you decribed.

But CubeMX is still generating HAL_ADC_MspInit which cannot be supressed.

But this generation takes control over _weak HAL_ADC_MspInit() via the linker afterwards. So I have never a chance to write my own HAL_ADC_MspInit().

This is the problem.

If CubeMX is clearly instructed by the user to generate no ADC code it should just follow this instruction and do note generate ADC-related code elsewhere.

Thank you very much

Andy

Hi Khouloud,

Let me explain in more detail, because I like the CUBEMX generally, maybe this helpes to improve it.

In my project many other peripherals are managed via CubeMX for example USB/Ethernet.

Therefore excluding the msp file like MM..1 suggested is no solution, because I need many parts of it.

I have the general task to manage a peripheral by my own without ANY interference of CubeMX.

ADC1 is just an example for a peripheral.

How to do this?

Solution1:

you do not tell CubeMX about ADC1

then the ADC-HAL-Files are not included (because the whole include process is controlled by CubeMX)

no good solution

Solution2:

You enable ADC1 in CubeMX and uncheck "Generate Code" in Advanced settings

Then CubeMX does the following:

• the global handle ADC_HandleTypeDef hadc1 is not created in main.c --> good
• the function call MX_ADC1_Init() is not created in main.c --> good
• but in stm32f4xx_hal_msp.c the low level HAL_ADC_MspInit() is still created --> not good

This wrong creation has the following consequence:

The generated function void HAL_ADC_MspInit(ADC_HandleTypeDef* hadc) REPLACES the original _WEAK definition within stm32f4xx_hal_adc.c!!

Your mentioned UserCode section within this generated function does not help either: You can fit in a return statement, so the function does not do anything.

But you CANNOT eliminate the function HAL_ADC_MspInit() itself with any of this UserCode action.

This function stays in stm32f4xx_hal_msp.c like a piece of stone! So the user is not free to use the HAL-Library for a peripherial under his control like he did years before CubeMX...

On the other side, life could be so easy:

This function which CubeMX generates (HAL_ADC_MspInit) is completely useless because

• nobody in the CubeMX context uses it
• CubeMX was so smart not to create a handle for the ADC. What is the sense for creating a function that has no resource to work with??

It would be a piece of cake for the developers of CubeMX to supress this generation as well.

I think it would be the desire of the developers of CubeMX to offer a clear situation for a user who needs a mixture of CubeMX controlled peripherals and self controlled peripherals:

--> For self controlled peripherals the only thing that CubeMX does is to make sure the appropriate HAL-Files are linked, nothing else!

That would be really great.

Maybe you can forward this suggestion to the appropriate place

Thanks for your help

Andy