Starting STM8 Microcontrollers
|
|
Some Useful Tips
When using a new compiler, I evaluate some certain things. For instance, how do I include my own written library files, interrupt management, what conventions I must follow and what dos and don’ts must be observed.
Creation & Addition of libraries
At some point in working with any microcontroller, you’ll need two basic libraries more than anything else. These are LCD and delay libraries. LCDs are great tools for quickly projecting or presenting data apart from debugging a code with a debugger. Similarly, time-wasting delay loops help us slow down things at our liking. Humans are not as fast as machines. Delays can be avoided in many novel ways but delays keep things simple and so are necessities in some areas.
The Standard Peripheral Library only provides libraries for hardware peripherals and surely not for anything else. It is also practically impossible to provide library for all hardware on available on the planet. Thus, whenever when we will be needing new hardware integrations with STM8s, we will have to code and tag our libraries with our projects. So how can we do so?
Earlier in this article I discussed about alphanumeric LCDs and delays. If you check the datasheet of such LCDs, you’ll find initialization sequences in some while in others you may also find ready-made codes. These sequences are needed to be translated in code just like what we do with I2C or SPI-based devices. Shown below is such an example:
Creating new libraries is simple. Just need to follow the following steps:
- There should be a header file and a source file for every new module. For example, h and lcd.c.
- Every header file should start with the inclusion of h header file (#include “stm8s.h”). This header is needed because it allows the access to the internal hardware modules available in a STM8 micro. For example, we will need access to GPIOs to develop our LCD library.
- A good practice is that the header files only contain function prototypes, definitions, constants, enumerations and global variables.
- The corresponding source file must only include its header file in beginning.
- The source file should contain the body of codes for all functions declared in the header file.
- When one library is dependent on the functions of another’s, the one that will be required in the new library must be included first. For example, we will need delay library in coding the LCD library because there are delay_ms functions in some parts of the library and so delay library should be included first. This should be the systematic order:
#include “stm8s_delay.h”
#include “lcd.h”
You can include these files at the bottom part of the stm8s_conf.h header file complying with right precedence as shown below:
Alternatively, you can add them after the first line #include “stm8s.h” in your main source code.
Peripheral Clock Configurations
In most codes revealed so far, I made clock configurations every time. The reasons behind so are
- Selection of right clock source.
- Adjustment of peripheral and system clocks as per requirement. Again, it is mainly intended to balance off both power consumption and overall performance.
- Disabling any unused hardware. This reduces power consumption and help us avoid certain hardware conflicts.
void clock_setup(void)
{
CLK_DeInit();
CLK_HSECmd(DISABLE);
CLK_LSICmd(ENABLE);
while(CLK_GetFlagStatus(CLK_FLAG_LSIRDY) == FALSE);
CLK_HSICmd(ENABLE);
while(CLK_GetFlagStatus(CLK_FLAG_HSIRDY) == FALSE);
CLK_ClockSwitchCmd(ENABLE);
CLK_HSIPrescalerConfig(CLK_PRESCALER_HSIDIV1);
CLK_SYSCLKConfig(CLK_PRESCALER_CPUDIV1);
CLK_ClockSwitchConfig(CLK_SWITCHMODE_AUTO, CLK_SOURCE_HSI,
DISABLE, CLK_CURRENTCLOCKSTATE_ENABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_SPI, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_I2C, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_ADC, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_AWU, ENABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_UART1, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_TIMER1, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_TIMER2, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_TIMER4, DISABLE);
}
The following lines select clock sources:
CLK_DeInit();
CLK_HSECmd(DISABLE);
CLK_LSICmd(ENABLE);
while(CLK_GetFlagStatus(CLK_FLAG_LSIRDY) == FALSE);
CLK_HSICmd(ENABLE);
while(CLK_GetFlagStatus(CLK_FLAG_HSIRDY) == FALSE);
What these lines do are enabling/disabling clock sources and wait for the sources to stabilize.
Then the following lines select clock prescalers and switching:
CLK_ClockSwitchCmd(ENABLE);
CLK_HSIPrescalerConfig(CLK_PRESCALER_HSIDIV1);
CLK_SYSCLKConfig(CLK_PRESCALER_CPUDIV1);
CLK_ClockSwitchConfig(CLK_SWITCHMODE_AUTO, CLK_SOURCE_HSI,
DISABLE, CLK_CURRENTCLOCKSTATE_ENABLE);
Finally, the last segment enables/disables peripheral clocks:
CLK_PeripheralClockConfig(CLK_PERIPHERAL_SPI, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_I2C, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_ADC, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_AWU, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_UART1, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_TIMER1, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_TIMER2, DISABLE);
CLK_PeripheralClockConfig(CLK_PERIPHERAL_TIMER4, DISABLE);
This segment is very important and should always be rechecked. Different chips have different internal hardware peripheral and so this segment will be different. For instance, STM8S105 has no UART1 module but it has UART2 instead. Research which hardware are available in your target micro and then code this segment. I ended up with several wasted hours of finding trouble in various cases only to find that I didn’t enable the required hardware.
Configuring Similar Stuffs Quickly
Sometimes you may end up doing the same stuff over and over again while you could have done it simply with one or two lines of code. For example, in the LCD library, the GPIOs that connect with the LCD share the same configurations. All are fast push-pull outputs.
GPIO_Init(LCD_PORT, LCD_RS, GPIO_MODE_OUT_PP_HIGH_FAST);
GPIO_Init(LCD_PORT, LCD_EN, GPIO_MODE_OUT_PP_HIGH_FAST);
GPIO_Init(LCD_PORT, LCD_DB4, GPIO_MODE_OUT_PP_HIGH_FAST);
GPIO_Init(LCD_PORT, LCD_DB5, GPIO_MODE_OUT_PP_HIGH_FAST);
GPIO_Init(LCD_PORT, LCD_DB6, GPIO_MODE_OUT_PP_HIGH_FAST);
GPIO_Init(LCD_PORT, LCD_DB7, GPIO_MODE_OUT_PP_HIGH_FAST);
This can be done in a more simplistic manner with just one line of code:
GPIO_Init(LCD_PORT, ((GPIO_Pin_TypeDef)(LCD_RS | LCD_EN | LCD_DB4 | LCD_DB5
| LCD_DB6 | LCD_DB7)), GPIO_MODE_OUT_PP_HIGH_FAST);
As you can see it is just a bunch of logical OR operation. The same method is applicable for other peripherals that share the same initialization function.
Some Stuffs About Cosmic C and SPL
- Functions, variables and definitions in Cosmic C are case sensitive.
- Functions with no arguments must not have empty argument areas. For example, you cannot write:
void setup ();
You should write it as:
void setup (void);
- Definitions and constants can be declared as with any C compiler.
- Wherever there are flags, you need to be careful. You should check and clear flags even if it is cleared by hardware. For instance, when reading ADC, the ADC End-Of-Conversion (EOC) flag is automatically cleared but still in the code you should check and clear it. ADC1_ClearFlag(ADC1_FLAG_EOC); Flags are so important that unless you check and clear them appropriately, you may not get the right result from your code. Personally, I didn’t care much until I got myself into trouble.
- You can mix assembly codes with your C code to enhance performance and optimization. However, you need to have sound knowledge of the assembly instructions. This is a rare requirement. The delay library, for instance, uses no operation assembly instruction to achieve delays. This is written as shown:
_asm ("nop");
- Empty loops are ignored by the compiler as a part of code optimization.
- Long ago, Atmel (now Microchip) published a document regarding ways to efficiently optimize C coding. This document holds true for most microcontrollers. For example, in that document it is stated that a decrementing do-while loop is much more faster and code efficient than an incrementing do-while You can apply the methods presented there and other similar tricks with STM8 microcontrollers too. The document can be found here:
http://www.atmel.com/images/doc8453.pdf - Though I don’t feel it as a necessity and don’t recommend it, you can avoid using the SPL and still code by raw register level access. For example, you can blink a LED with the following code:
#include "stm8s.h" void main (void) { GPIOD->DDR |= 0x01; GPIOD->CR1 |= 0x01;for(;;){GPIOD->ODR ^= (1 << 0);delay_ms(100);};}
- Don’t mess with configuration (fuse) bits unless needed. Most of the times you will never have to deal with them. AFRs are used when remapping is needed or to enable special GPIO functionality. These will be of most importance.
- Bitwise and logic operations are useful. Not only they are fast, they just deal with the designated bits only. SPL has support for such operations but it is still better to know them. Here are some common operations:
#define bit_set(reg, bit_val) reg |= (1 << bit_val)
//For setting a bit of a register
#define bit_clr(reg, bit_val) reg &= (~(1 << bit_val))
//For clearing a bit of a register
#define bit_tgl(reg, bit_val) reg ^= (1 << bit_val)
//For toggling a bit of a register
#define get_bit(reg, bit_val) (reg & (1 << bit_val))
//For extracting the bit state of a register
#define get_reg(reg, msk) (reg & msk)
//For extracting the states of masked bits of a register
Unlocking a Locked STM8 Chip
If you have accidentally locked a STM8 chip by setting the Readout Protection configuration bit and no longer able to use it, you can unlock it easily.
When you lock a chip, the programmer interface will give you a warning notification. If you retry to reprogram/erase a locked chip you’ll get an error like this:
No matter what you do, you won’t be able to use it.
To unlock, go to the light programmer interface of STVD and check the Unlock Device checkbox as shown below:
Also select Erase before Programming radio button because it is highly likely that your target chip is not empty. Now once you retry to reprogram, it will get unlocked.
Mastering C Language
You need not to be a C whiz to work with microcontrollers but certain things will surely help you to resolve some critical problems with simple codes. You must check supported data types whenever you begin working in a new development environment and should always use unsigned-signed designations to avoid unnecessary mistakes. Likewise, variable size is also important. Pointer, structures, unions and arrays are helpful features of C-language. You must learn how to use and apply them successfully. Without these you can still work but things will look really dirty. When coding for a new work, you must try to settle what you wish from your system and how should it behave. There should be an organized workflow and thereby your code will automatically be formulated in a state-of-machine algorithm or as a real-time system. You must try to avoid delays and loops wherever possible. Try to avoid polling and use interrupt-based systems. This will make your device behave in real-time with zero latency. However, you must be careful in handling interrupts because interrupts within interrupts will cause your system to crash miserably. Functions make things modular and thus easy to modify or debug. Repeated tasks should be placed in functions. A blinking LED code may look simple and stupid but sometimes very useful for testing stuffs. Some basic knowledge on mathematics and algorithms are also requirements for becoming a good embedded-system specialist.
Epilogue
In the end, I would like to share that my tiny raw-level knowledge and experiences with STM32s (http://embedded-lab.com/blog/stm32-tutorials/) earlier paid off handsomely. Due to that I was able to compiler this article decently and quickly. Personally, I feel that whosoever knows STM8 micros well will master STM32s and vice-versa because except the cores all hardware in both architectures are not just similar but same sometimes. This is for the first time I have admired STM’s SPL. My experiences with STM32 SPL was not well as so I decided to go on my own. However, this time things were different. Things were joyful and less difficult.
I would like to thank a few people who influenced me in composing this article:
- Firstly, my friends and acquaintances. I wanted to help them out and that drove me to dig things deep.
- Ben Ryves (benryves.com/tutorials/stm8s-discovery/).
Though his methods are different than mine, his article guided me a lot in the beginning. It is perhaps the most popular site for tutorials on STM8s and well organized. He used STM8S105 Discovery.
- Mark Stevens (http://blog.mark-stevens.co.uk)
His tutorials on STM8 are not based on SPL. He showed stuffs with raw-level register access and with IAR compiler. Still his blog is informative.
- http://www.emcu.it/. This Italian site was helpful in getting some early info.
- STMicroelectronics team for releasing the STM8CubeMX during my writeup.
- Cosmic team for freeing up their C compiler.
I spent nearly three months straight putting together all these things and at present, I must say that I have great expectations from STM8 microcontrollers.
A sequel of this post can be found here.
Happy coding.
Author: Shawon M. Shahryiar
https://www.facebook.com/groups/microarena
https://www.facebook.com/MicroArena 24.04.2017
JLCPCB: Prototype 10 PCBs for $2 (2-layer,100*100mm) |
|
|
Pingback: آموزش میکروکنترلر STM8 قسمت دهم: Beeper - سیسوگ - Sisoog
Pingback: آموزش میکروکنترلر STM8 قسمت نهم: وقفه خارجی (EXTI) - سیسوگ - Sisoog
Pingback: آموزش میکروکنترلر STM8 قسمت هشتم : کلاک سیستم (CLK) - سیسوگ - Sisoog
Pingback: آموزش میکروکنترلر STM8 قسمت هفتم: LED چشمکزن - سیسوگ - Sisoog
Pingback: آموزش میکروکنترلر STM8: چگونه برنامه خود را روی STM8 آپلود کنیم؟ - سیسوگ - Sisoog
Pingback: قسمت پنجم: آماده سازی ابزارهای نرمافزاری برای STM8 - سیسوگ - Sisoog
Pingback: آموزش میکروکنترلر STM8 قسمت چهارم: STM8CubeMX - سیسوگ - Sisoog
Pingback: آموزش میکروکنترلر STM8 قسمت سوم: کامپایلر و پروگرامر - سیسوگ - Sisoog
Pingback: قسمت دوم:معرفی بردهای Discovery میکروکنترلر STM8 - سیسوگ - Sisoog
Pingback: میکروکنترلر STM8 چیست و از کجا آمده است؟ - سیسوگ - Sisoog
Hi SHAWON SHAHRYIAR,
I have been working through your articles and trying to understand as much as possible. I am currently looking at the AWU,
I have brought in the project, compiled and built with no errors.
However when running the program the CPU goes into the halt mode, and never Auto wakes up!
Is there some more work that has to be done in the interrupt side of things? Does the project need the ITC.c and ITC.h files and some adjustments in there?
Could I also have the delay.c and delay .h files please.
Andy.
By the way, I am using the STM8SVL Discovery with the 003K processor on it also so all hardware is identical.
No, nothing needs to be done in the interrupt “itc” files but you need to add some lines in the “it” interrupt files:
in the “it” header file add the following line:
@far @interrupt void AWU_trigger_IRQHandler(void);and in the “it” source file add the following lines:
void AWU_trigger_IRQHandler(void){
AWU_GetFlagStatus();
}
Change the interrupt vector file as shown below:
#include "stm8s_it.h"typedef void @far (*interrupt_handler_t)(void);
struct interrupt_vector {
unsigned char interrupt_instruction;
interrupt_handler_t interrupt_handler;
};
//@far @interrupt void NonHandledInterrupt (void)
//{
/* in order to detect unexpected events during development,
it is recommended to set a breakpoint on the following instruction
*/
// return;
//}
extern void _stext(); /* startup routine */
struct interrupt_vector const _vectab[] = {
{0x82, (interrupt_handler_t)_stext}, /* reset */
{0x82, NonHandledInterrupt}, /* trap */
{0x82, NonHandledInterrupt}, /* irq0 */
{0x82, AWU_trigger_IRQHandler}, /* irq1 */
{0x82, NonHandledInterrupt}, /* irq2 */
{0x82, NonHandledInterrupt}, /* irq3 */
{0x82, NonHandledInterrupt}, /* irq4 */
{0x82, NonHandledInterrupt}, /* irq5 */
{0x82, NonHandledInterrupt}, /* irq6 */
{0x82, NonHandledInterrupt}, /* irq7 */
{0x82, NonHandledInterrupt}, /* irq8 */
{0x82, NonHandledInterrupt}, /* irq9 */
{0x82, NonHandledInterrupt}, /* irq10 */
{0x82, NonHandledInterrupt}, /* irq11 */
{0x82, NonHandledInterrupt}, /* irq12 */
{0x82, NonHandledInterrupt}, /* irq13 */
{0x82, NonHandledInterrupt}, /* irq14 */
{0x82, NonHandledInterrupt}, /* irq15 */
{0x82, NonHandledInterrupt}, /* irq16 */
{0x82, NonHandledInterrupt}, /* irq17 */
{0x82, NonHandledInterrupt}, /* irq18 */
{0x82, NonHandledInterrupt}, /* irq19 */
{0x82, NonHandledInterrupt}, /* irq20 */
{0x82, NonHandledInterrupt}, /* irq21 */
{0x82, NonHandledInterrupt}, /* irq22 */
{0x82, NonHandledInterrupt}, /* irq23 */
{0x82, NonHandledInterrupt}, /* irq24 */
{0x82, NonHandledInterrupt}, /* irq25 */
{0x82, NonHandledInterrupt}, /* irq26 */
{0x82, NonHandledInterrupt}, /* irq27 */
{0x82, NonHandledInterrupt}, /* irq28 */
{0x82, NonHandledInterrupt}, /* irq29 */
};
Sorry for the trouble…. I probably forgot to state these in the code and explanation segments…. Will be updating the post…. Thanks for this catch….
Hey,
Grateful for the tutorial! Nice work.
I tried this section of your tutorial and got 33 errors after building:
it was due to commenting of :
@far @interrupt_handler_t void NonHandledInterrupt (void)
{
return;
}
because these were used in the interrupt vector struct again. I uncommented those lines and got one error:
“unknown space: interrupt_handler_t”
what should i do now?
please help me!
Thanks alot.
You are getting this error for which interrupt example?
Hi
Thank you for the post,
I ve used your code for another sensor and noticed that in the i2c read routine you’ve forgot to send a stop to release the clock line. Modification is as follows
..
Regards
unsigned int BH1750_read_word(void)
{
unsigned long value = 0x0000;
unsigned char num_of_bytes = 0x02;
unsigned char bytes[2] = {0x00, 0x00};
while(I2C_GetFlagStatus(I2C_FLAG_BUSBUSY));
I2C_GenerateSTART(ENABLE);
while(!I2C_CheckEvent(I2C_EVENT_MASTER_MODE_SELECT));
I2C_Send7bitAddress(BH1750_addr, I2C_DIRECTION_RX);
while(!I2C_CheckEvent(I2C_EVENT_MASTER_RECEIVER_MODE_SELECTED));
while(num_of_bytes)
{
if(I2C_CheckEvent(I2C_EVENT_MASTER_BYTE_RECEIVED))
{
if(num_of_bytes == 0)
{
I2C_AcknowledgeConfig(I2C_ACK_NONE);
I2C_GenerateSTOP(ENABLE);
}
bytes[(num_of_bytes – 1)] = I2C_ReceiveData();
num_of_bytes–;
}
};
/// the following line should be added
I2C_GenerateSTOP(ENABLE);
….
}
Noted with thanks….
I reviews the code and found that I added the I2C stop command here:
if(num_of_bytes == 0)
{
I2C_AcknowledgeConfig(I2C_ACK_NONE);
I2C_GenerateSTOP(ENABLE);
}
So there is no need to add stop command after the loop….
Hi
You are right, it was due to my modification.
Anyway I just wanted to thank you for the postings.
Regards
Hello Sir,
I am trying to compile the code of led blink. It gives me error like this
Compiling main.c…
cxstm8 -i”..\..\..\..\users\rajes\documents\sisai technologies\software\stm8s lib\stm8s_stdperiph_lib\stm8s_stdperiph_lib\libraries\stm8s_stdperiph_driver\inc” -i”..\..\..\..\users\rajes\documents\sisai technologies\software\stm8s lib\stm8s_stdperiph_lib\stm8s_stdperiph_lib\project\stm8s_stdperiph_examples\adc2\adc2_continuousconversion” +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\Hstm8″ -clDebug\ -coDebug\ main.c
#error cpstm8 ..\..\..\..\users\rajes\documents\sisai technologies\software\stm8s lib\stm8s_stdperiph_lib\stm8s_stdperiph_lib\libraries\stm8s_stdperiph_driver\inc\stm8s_uart1.h:106(13) missing enumeration member
#error cpstm8 ..\..\..\..\users\rajes\documents\sisai technologies\software\stm8s lib\stm8s_stdperiph_lib\stm8s_stdperiph_lib\libraries\stm8s_stdperiph_driver\inc\stm8s_uart1.h:113(13) missing enumeration member
main.c:
The command: “cxstm8 -i”..\..\..\..\users\rajes\documents\sisai technologies\software\stm8s lib\stm8s_stdperiph_lib\stm8s_stdperiph_lib\libraries\stm8s_stdperiph_driver\inc” -i”..\..\..\..\users\rajes\documents\sisai technologies\software\stm8s lib\stm8s_stdperiph_lib\stm8s_stdperiph_lib\project\stm8s_stdperiph_examples\adc2\adc2_continuousconversion” +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\Hstm8″ -clDebug\ -coDebug\ main.c ” has failed, the returned value is: 1
exit code=1.
Can you help me?
Why are you adding ADC2 header and source files? Are you not using STM8S003?
stm8s_conf.h this file i am added from ADC2
Add only the hardware files that your target chips supports…. For example, you cannot add ADC2 for STM8S003…. This is so as STM8S003 doesn’t have these hardware blocks…. Likewise if you are using STM8S207, you cannot add UART2 files for the same reason…. If you don’t add required files then you will get errors…. You’ll also get errors if you add files that are not applicable for your target MCU….
Hi
I am using stm8s003f3 pin out board and with this code I am just testing output at micro controller pin 2 i.e. TX
I am testing this using an oscilloscope.
but not able to get any output
Can you please help?
Thanks
Did you recompile the code for your target chip?
Yes I did.
But Not getting expected output
Apart from the scope is there anything else connected with this pin? It should work as I have shown…. Can you try with a different board?
hi
nothing else is connected to that pin. yes I did try another board. but the results are same.
TX pin is just going HIGH.
hi
In STVD , STM8S003F3 MCU is not available but I am using this same so from the MCU selection list I have selected STM8S003F3P.
So does it make any difference??
no it doesn’t….
Hi Shawon
Any advice on how to code the Program to get the STM8s talking to the max31855?
This is causing me some problems.
JP
Hello
I have followed the code as per the explanation.
but I’m getting garbage values on serial port.
Can you suggest any debugging steps??
Thanks in advanced.
PS: Great tutorial. It’s helping me a lot.
1. Check wiring for loose connections….
2. Use a stable and noise-free power source like a battery-bank to power up the board…. Noise from PC port may cause unwanted issues….
3. Use CP2102 or FT232-based USB-TTL converter…. Don’t use PL2303-based ones because most are clones or fakes….
4. Use a short USB cable….
5. Use external pull-up resistors for both TX and RX pins….
6. Try with another board if these don’t solve the issue…. It should not behave as you are saying because the code has no issues….
Serial receiving program is not working
It should be unless something else is connected to the receive pin…. Please tell me about your hardware setup….
Hello sir
Do you tell me how generate pwm in pin no. B5 & B5
in Stm8 board
Which STM8 chip? Because different chips have different pin mapping and sometimes there are alternative pins for such purposes…. Check with STM8CubeMX if that pin is available for that purpose….
i have done code for multi channel adc but its not working ????
when i use single channel adc its working properly…………
Which channels are you using?
Hello guys
here i’m again for ask your help. I wrote a very easy program but when i try to send to stm8 the light programmer give me this error :
Programming…
PROGRAM MEMORY:
>Erase not feasible
>Programming
Error: Device not recognized !
some idea ?
Thank you
Sergio
Unlock it first with light programmer…. It seems you locked it probably….
First thank you so much for this wonderful tutorial, i’m new with STM8 i follow all you steps but i still have a problem and here i’m please can you help me this is the error message.
Thank you
Sergio
———– Project test_prov – STM8 Cosmic – Configuration Debug ————-
Compiling main.c…
cxstm8 -i..\..\en.stsw-stm8069\stm8s_stdperiph_lib\project\stm8s_stdperiph_template -igpio -iinc +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\FSE_Compilers\CXSTM8\Hstm8″ -clDebug\ -coDebug\ main.c
#error cpstm8 gpio\inc\stm8s.h:74 “Please select first the target STM8S/A device used in your application (in stm8s.h file)”
main.c:
The command: “cxstm8 -i..\..\en.stsw-stm8069\stm8s_stdperiph_lib\project\stm8s_stdperiph_template -igpio -iinc +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\FSE_Compilers\CXSTM8\Hstm8″ -clDebug\ -coDebug\ main.c ” has failed, the returned value is: 1
exit code=1.
test_prov.elf – 2 error(s), 0 warning(s)
It seems that you didn’t select the chip family or category….
Yes it’s true really i don’t know why i find another stm8s.h inside External Dependencies folder maybe i make some mistake in the beginning.
Tank you
Sergio
Hi Shawon ,
Excellent article on stms8.
within 3 days i was able to understand STMS8 very clearly.
can you send me delay library files please.
i tried to create my own without any success.
warm regards
Firstly thanks…. All library files and materials can be found here https://libstock.mikroe.com/projects/view/2056/stm8-microcontroller-tutorials
Please search for stm8s_delay.c and stm8s_delay.h in projects like TFT display demo, OLED demo, LCD libraries, etc….
hi sir now also getting problem in compilation time …..’
so plz can u send me the soft copy of software wat properly working at u…??
my emain id…
imran.vectorindia@gmail.com
I’m using the same software you are using – the latest one out there…. and so someone sending it has no meaning…. I suggest that you uninstall it and give it fresh retry, following all the steps carefully…. No one can help you with licensing issue unless to do it correctly….
hi geting poroblem while click on programmer ten my softare automatically close tab
The latest version of STVD has this issue…. I’m also facing this issue and so are many other like us…. Hope STM fixes this issue fast…. For now use STVD for coding and STVP for flashing….
thanks sir
hi sir…
i getting problem for license configured……………. at compile time getting error like that…………. plz help out
#error cpstm8 C:\Program Files (x86)\COSMIC\FSE_Compilers\CXSTM8\HSTM8\mods0.h:1 FlexLM Cannot find license file.
main.c:
The command: “cxstm8 -iinc +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\FSE_Compilers\Hstm8″ -clDebug\ -coDebug\ main.c ” has failed, the returned value is: 1
exit code=1.
alpha_lcd.elf – 3 error(s), 0 warning(s)
Did you follow the procedure as I showed?
YES SIR
helo…we hav stm8svl discovery..i need embedded c program for the glowing of led,connecting ir receiver and also powersupply…for connecting these things i need code can u please guide me
Thanks for this article..
I am looking for microsd card interface with STM8s discovery board. can you please provide the tutorial for microsd card?
It is on my plan but not possible recently….
In relation to disabling unused peripheral clocks as suggested by you:
I found the following list of peripherals in the STM8S105 Discovery Board: Advanced control timer (TIM1), General-purpose timers (TIM2 and TIM3), Basic timer (TIM4), SPI, I2C, UART2, Window WDG, Independent WDG, ADC1,
AWU timer, Beeper.
Is this all?
I could not find the clock peripheral configuration function for Window WDG, Independent WDG, Beeper in the Standard Peripheral Library.
Is it not required?
P.S. I am new to MCU programming with a little experience on Arduino. So please forgive me if the question is foolish.
1. STM8S003K3 Discovery – the one I use for the blog is different from STM8S105…. They have different peripherals and so there will be differences in peripheral clocks…. Please check the device datasheet/STM8CubeMX for available hardware….
2. WWDG and IWDG are set in option bytes and they don’t use peripheral/CPU clock…. Their oscillator is separate…. Due to these they don’t have clock configurations like other peripherals….
P.S: No question is a noob question…. every question is allowed no matter how silly it may look….
Thank You
Hi please someone tel me where can i find stm8s_delay.h and stm8s_delay.c
Thanks
Check the inc and src folders….
There is not . Could you send me please if you have it.
Aminassadi.og@gmail.com
mail sent….
please, send me too the library delay
Hi , please someone tel me . Where can i find stm8s_delay.h and stm8s_delay.c
Thanks ..
i am using stms003f3p6 controller..i have done as u told exactly but tim1 input capture is not displaying any value …according to your article it should display 10…i dont have any errors everything is fine…pulse on tim2 is ok ..it is coming as u said…but capture not working..please help me …thank you…
In STM8S003F3P6, TIM1 input capture CH1 is located in PC6 instead of PC1. Did you check this out?
i changed that too..but no response tim2- 50hz as u said..but tim1 ch1 pc6 not capturing …still 000000 on lcd..
Send me your full code so that I can check and debug it….
Hi Sir,
i have just follwed your instruction provied in yout tutorial in main.c
#include “stm8s.h”
main()
{
while (1);
}
This error comes, can you please check why this error come, i am new and learn the controller programming.
main.c:
The command: “cxstm8 -i”d:\other datasheet\new folder\lib\stm8s_stdperiph_lib\libraries\stm8s_stdperiph_driver\inc” +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\FSE_Compilers\CXSTM8\Hstm8″ -clDebug\ -coDebug\ main.c ” has failed, the returned value is: 1
exit code=1.
main.o – 2 error(s), 0 warning(s)
Thanks,
Perhaps you should recheck according to this video: https://www.youtube.com/watch?v=sqCuSVjevrY
Hi there, i solve the previous ADC problem. Anyway, u make some good tutorial on stm8 chips. Nice work
What was causing that issue? How did you solve it?
because i put all these
ADC_DeInit(ADC1);
ADC_SamplingTimeConfig(ADC1, ADC_Group_SlowChannels, ADC_SamplingTime_4Cycles);
ADC_SchmittTriggerConfig(ADC1, ADC_Channel_7, DISABLE);
ADC_ChannelCmd(ADC1, ADC_Channel_7, ENABLE);
ADC_Init(ADC1, ADC_ConversionMode_Continuous, ADC_Resolution_12Bit, ADC_Prescaler_1);
ADC_Cmd(ADC1, ENABLE);
ADC_ExternalTrigConfig(ADC1, ADC_ExtEventSelection_None, ADC_ExtTRGSensitivity_All);
in ‘while(1)’. It keeps looping.
Once i put it before ‘while (1)’, it becomes normal.
lol, sorry im noob
Hi there, thanks for sharing. I learn alot thru your example, but I have encounter a problem with adc. Im currently using stm8l151k4t6. I wanna use the pin D7 as to read the voltage from my battery and monitor it (display on LCD). Can u please check where it goes wrong on my code?
ADC_DeInit(ADC1);
ADC_SamplingTimeConfig(ADC1, ADC_Group_SlowChannels, ADC_SamplingTime_4Cycles);
ADC_SchmittTriggerConfig(ADC1, ADC_Channel_7, DISABLE);
ADC_ChannelCmd(ADC1, ADC_Channel_7, ENABLE);
ADC_Init(ADC1, ADC_ConversionMode_Continuous, ADC_Resolution_12Bit, ADC_Prescaler_1);
ADC_Cmd(ADC1, ENABLE);
ADC_ExternalTrigConfig(ADC1, ADC_ExtEventSelection_None, ADC_ExtTRGSensitivity_All);
ADC_SoftwareStartConv(ADC1);
while(!ADC_GetFlagStatus(ADC1, ADC_FLAG_EOC));
battery = ADC_GetConversionValue(ADC1);
The adc library is here. Really appreciate your help
http://www.codelooker.com/codea/21515470915STM8L15xrefrencecode/stm8l15x_adc.c.html
What error or issue are you encountering?
Thanks.
LOL my bad, i did not mentioned what error. Basically the lcd is still displaying 4095 which is (2^12)-1, no matter what my voltage is at. I think the pin d7 is not read by the microcontroller
That’s because you are not clearing ADC conversion complete flag after reading the ADC data….
actually i did. U mean this line ?
ADC_ClearFlag(ADC1, ADC_FLAG_EOC);
It is still the same. I not really sure why. Can ADC1 works with several input ?
Did you enable the clock for the ADC module?
CLK_PeripheralClockConfig(CLK_PERIPHERAL_ADC1, ENABLE);
yes I did enable the clock for the ADC module too. Basically i noticed that the pin is like not read by the microC. It just display the bits that I set. when I put 8 bit, it shows 255, 10 bits it show 1023 and so on.
hi shawon great tutorials it would be nice too if you covered the coide compiler for arm it’s a good free compiler
I have plans to cover STM32 with STM32 System Workbench and STM32CubeMX….
hi shawon thanks for your response and support it turns out that my problem was a license issue I stupidly thought i use one license on multiple pc’s I used the license for a particular computer for mine that’s why I’ve been having compilation issues you have to use the license file stm8 sends you that is generated by your own pc else it won’t compile it’ll jus kip throwing you errors
It seems that you didn’t follow my instructions completely…. I found some issues:
1. You have included header and source files of ADC2, CAN, UART2, etc which are unavailable in STM8S103…. Add only files for the peripherals available in your target MCU…. Exclude the rest….
2. You have not included stm8s_delay header and source files…. Either disable it from stm8s_conf.h header file if you are not going to use it or add both the header and the source files for it in your project….
Resolve these and you are good to go….
Thanks….
I haven’t compiled any of the examples yet I just tried to compile the main source file just for test purpose n it just keeps showing me the same errors
yes the comic compiler was installed properly i even received a license file from my mail with the instructions to copy the license file to the license folder in the install directory if you fail to do this it will keep popping up for you to put in the license file. iincluded all the source files and header files as instructed i am working with the cheap stm8s103f i uncommented the stm8s103f in the stm8.h header file as you instructed and just to compile the main file it just throws me errors
Send me your project files and folder…. Let me see what’s going on….
no I just followed your instructions I just compiled it after setup i did not write any code yet just compiled the default main file
Need more details….
1. The version of STVD and Cosmic
2. Which example is giving this issue?
3. The chip you are using if it other than STM8S003
4. Have you tried to compile something else other than my examples?
5. Are the paths to libraries and other folders properly added?
6. Is the Cosmic compiler registered properly?
it throws this line The command: “cxstm8 -iinc +debug -pxp -no -l +mods0 -pp -i”C:\Program Files (x86)\COSMIC\FSE_Compilers\Hstm8″ -clDebug\ -coDebug\ main.c ” has failed, the returned value is: 1
exit code=1.
It is because you are making a simple silly mistake like a missing argument or semicolon somewhere in your code….
hi I’m having compilation issues when I compile it just throws me error about comic compiler located in the program file ialso excluded unwanted header files but my problems still weren’t solved
hi thanks for the tutorials but i am having compiler error issues even when I remove unnecessary header files it say comic compiler error
Hi. What does the error state?
I am new to STM8S003k3 Discovery board.I have done UART communication using STM standard peripheral library example. Now I want to define any other GPIO pin for UART communication. Is it possible to use d0 and d1 pin for the UART communication? If yes, then please let me know how?
It is possible to use any GPIO for UART communication using software UART. You’ll need to take care of character timings on your own using a timer.
thank you very much for this article!
Thank you for your time and effort.
Good job bro
Thank you for this exceptionally comprehensive article, much appreciated
Rando!
You are welcome….