Is there anyone who is working ON MicroC for ARM?

[shubh1196]

hello there,
I'm working on Click Air Quality 5 sensor with stm32f030r8 discovery board, as this sensor is providing the example code with its library for MicroC for Arm, after making up with a complete environment I'm getting an error while compilation, for #include __hal_stm32.c file can't be open.
I'm attaching the image for the error, any help will be appreciated.

Thanks
Shubhanshu

 

[be80be]

Ian Rogers

But your error is it can't find the file
Probable cause is one it's not there or it's owner is not you
or 2 you got all this somewhere else and they had it on there D: drive and you have it on your C: drive.

 

[Ian Rogers]

I must admit, that code does look like you dragged it from the internet...

Check the folder for the offending file.. When a file is included with "" then its looking for the build directory..

 

[Mickster]

Looks like it comes from here:

Air quality 5 click | MikroElektronika

Air quality 5 click is a triple MOS sensor on a single Click board™ of different gases. MIKROE-3056 Texas Instruments ADS1015 SGX Sensortech MiCS-6814

www.mikroe.com

Check here for MikroC for ARM package:

LibStock - Air quality 5 click

Air quality 5 click is a triple MOS sensor on a single Click board, which can detect gas pollution for a number of different gases. The onboard sensor is specially designed to detect the pollution from automobile exhausts as well as the gas pollution fro

libstock.mikroe.com

 

[shubh1196]

Ian Rogers

But your error is it can't find the file
Probable cause is one it's not there or it's owner is not you
or 2 you got all this somewhere else and they had it on there D: drive and you have it on your C: drive.

Thanks for your reply, but as in MicroC pro for ARM site explains that it doesn't require external header file to be included it automatically includes from library manager, just we need to select the particular library in library manager.

 

[Ian Rogers]

Thanks for your reply, but as in MicroC pro for ARM site explains that it doesn't require external header file to be included it automatically includes from library manager, just we need to select the particular library in library manager.

That is for "In Built" libraries Clearly the __HAL_STM32.C file needs to be in the build directory... And it isn't.. This is a board definition file and code and will be so you can use that chip.. Once you get a copy, you'll need time.c and the type def c file as well...

 

[shubh1196]

So how can I access that __HAL_STM32.c file, when I tried to include actual stm32 hal library file the function matching was not there.
If you have that file please add it or provide the oink from where I can it.

 

[Ian Rogers]

The stm32f03r08 isn't in the supported list.. I would imagine that's why the extra files will be needed...

All STM32 HAL libraries - STM32F4 Discovery

In this section, I will write all libraries based on HAL drivers from ST. If you see this first time, make sure you read this post first about how structure of my libs looks like! License All my softwares are published under MIT license. This means that you are allow to modify, share and use my...

stm32f4-discovery.net

Here you will find everything for that board.. BUT! Before you do, check the system libraries to make sure mikroc hasn't included them.. Also check libstock as those libraries integrate better with mikroc..

 

[shubh1196]

I've already checked that, if you see the provided code, in __airq5_hal.h it's trying to call __hal_i2c.c which is not there in the stm32i2c library and if I add the file function calls are also not matching with the STM provided libraries.
So, this will again create the problem.

 

[Ian Rogers]

Looking on GTIHUB you have a different library..

did you download this one? https://libstock.mikroe.com/projects/download/2404/10250/1528808650_air_quality_5_cl_mikroc_arm.mpkg

There is one without the HAL.. Can you use the one in the link?

 

[jayanthd]

I can help you with your problem. I use mikroC PRO ARM for my projects.

Zip and post your complete project and mention which Click example you are using. Provide the mikroE links for the Click modules that you are using.