STM8 MCUs

Posted on May 30, 2012 at 10:24I'm having some problems with it. The problem is that randomly it starts to fail when you try to save any file (project, .c , . h files, etc). It happened to me 3 times already in the few days that i'm using it. One of the times one of the files was directly gone (deleted from disk) so i need to create it again (lucky that it was a .h file). I'm a bit scaried with it.In other hand i had problems debugging, and it is not intuitive. First thing would be nice to have a direct key to program and go to debug mode (actually it doesnt have a direct key). But the most confusing and annoying stuff is that Run button (F5) restarts the program from beggining even if you stopped previously on a breakpoint..., it is the first IDE where this happens (and i'm programming since 25+ years ago). I dont see the real difference between reset and run button... i had to ''discover'' the continue button. I feel this product as somet

Posted on June 04, 2012 at 10:52I am using the UART1_Printf example from the STM8S Standard Peripheral Library version 2.1 and I am having problems with the speed of the UART.  I am expecting to see 115200 baud but according to my logica analyser I am in fact seeing  53 baud (approx).To double check the LA value I have fed the output from an independent system running .NETMF and asked it to produce a similar signal.  The LA reports the right baud rate give or take a small deviation (i.e. 9615 baud).Is anyone else seeing similar problems or have a solution?Regards,Mark #uart-baud-rate

Posted on June 05, 2012 at 09:18Which of the Unique ID bytes actually get used? I'd like to use the unique ID of the microcontroller in a project to identify uC units on a comms bus. And as a product we would be using many of them. We have tried to avoid having to program IDs into them during production. I'd like to use the minimum number of bits in my application to ID the device. At the same time I'm trying to avoid having the same ID used twice. At the moment I'm using four bytes. If there's bits I'm reading from the Unique ID bits that never gets used, I'd like to be able to ignore them but the datasheet doesnt mention anything about parts of the ID that dont get used. I suspect that its a production-time process that gets applied to all chips and so for the chip we are using some bits may not get used. I notice that only the high byte of the x and y wafer coordinate bytes change between devices so I dism

Posted on May 29, 2012 at 18:04Hi. I'm coding my 3rd testing project on stm8, to be exact in 2 different mcus, 103 and 105. I'm using cosmic compiler, and i didnt have any problem with the previous 2 projects (because i didnt verify the size). The problem is that binary files generated by cosmic linker are oversized,... I expain it. Until now ( I have more than 25 years programming and 13 years in MCU's world) when you included functions and you didnt use them, the linker was able to remove them from final binary since they are not being used..., I say until now because cosmic compiler is not doing that. In my 3rd testing project i wanted to create the bigger array in flash (with const char noname[xxx];, where xxx is the size). What was my surprise when with a small code (about 10 lines my code, basically initializing ports and timers)  the bigger table size that I was able to crea

Posted on May 30, 2012 at 10:34 Hi, since i dont get a response in discovery forum, i will repaste here.I'm trying to set a pin to an alternate remapping pin, exactly i'm using TIM2 with PWM and i want channels in D2, D3 and D4. I have tried with this: #define OPT2 0x4803 FLASH_Unlock (FLASH_MEMTYPE_DATA); FLASH_ProgramOptionByte(OPT2, 0x02); FLASH_ProgramOptionByte(OPT2+1, 0xFD); FLASH_Lock (FLASH_MEMTYPE_DATA); with no luck, even I started to get problems with SWIM, it said that opt byte complement was different. Anyway using STVP I was able to remove that stuff. I was able to make it work by flashing my code and then chaning the opt byte with STVP.... Another problem is that after it works (0x02 in OPT2 register) if I read it I get the complemented value (0xFD), so i tried to read data memory positions 0x4801, 0x4802, 0x4804 and 0x4805 with no luck (none of them was 0x02). k=FLASH_ReadOptionByte(OPT

Posted on May 28, 2012 at 02:47I tried to use the firmware lib to program it ,but failed. FLASH_Unlock(FLASH_MEMTYPE_DATA);      for(i = 0; i < DataLeng; i=i+4)   {    FLASH_ProgramWord(StartAddr + i,(*(u32*)pBuf));    pBuf= pBuf+4;;    FLASH_WaitForLastOperation(FLASH_MEMTYPE_DATA);   } FLASH_Lock(FLASH_MEMTYPE_DATA); But when I use program_byte, it sucess. I just want to save time because I need to programe 23 byte at sequence address one time. Thanks! ChrisChen

Posted on June 01, 2012 at 13:18Hi, I'm trying to evaluate the use of the ''Flash Loader Demonstrator'' together with a STM8S105 (''STM8S_Discovery'' Eval Board). I attached a MAX232 board to communicate via RS232 (PC) with the UART2. All of this works fine on my own Communications routines. But when I try to use the Flash Loader, after setting the MCU in ''Boot Mode'', I always get error messages (like ''unrecognized device ... Please reset and try again''). My settings: 1) I used ''ST Visual Programmer'' to fix the Option Byte: ''BootLoader: Enabled''. I also read this ''tab'' with this STVP after, to confirm what I have done: it's OK, BootLoader keeps Enabled. 2) On Flash Loader: COM1, 115200, Parity:None, Echo: Echo Enabled, Timeout: 5s ...are these setting corrects for this device? ...(on UM0560 Manual I read STM8S-32K devices, UART2 settings for Boot Mode are like this, in ''reply'' mode ...) I suppose ''reply

Posted on May 29, 2012 at 09:18Hello sirI am using the STM8S103F2P6 microcontroller of the ST microelectronics and when I was studying the power supply section of the microcontroller there it is specified to connect an external capacitor with the value ranging in between the 470 to 3300 nf . the specifications for the external VCAP capacitor are as follows:Value   =    470  to    3300   nfESL   =    15  nH max.ESR        =     .3 ohm at 1 MHz.But I have connected the 1 uF value capacitor to the Vcap pin of the microcontroller , because I was not getting the microcontroller of that range .So   I want to know that is it ok , or it is going to effect my microcontroller in any way. I mean what will be the effect and how it will effect my whole circuit and the microcontroller.

Posted on May 30, 2012 at 10:27 Another problem, and it is the 4th that i found in few days. STM8 libraries doesnt support a project with multiples devices, I was able to fix it just including at the beginning of each .c file something like: (for exampleo for stm8s_uart1.c) #if defined(UART1) .... #endif So, if you have a generic project and you include the uart1 because one of the device use it, when you compile for another device you get an error in that library. #error-library-multi-cpu

Posted on August 29, 2011 at 15:26 Hi Everybody, I have some problem with my linker, and I don't know how to fix it. Can somebody help?? I'm new to this. Running Linker clnk -l''C:\Program Files (x86)\STMicroelectronics\STM8S_StdPeriph_Lib_V2.0.0\Libraries\STM8S_StdPeriph_Driver\src''  -o debug\stm8s103.sm8 -l''..\..\..\..\..\program files\cosmic\cxstm8_16k\lib'' -l''..\..\..\..\..\..\program files (x86)\cosmic\cxstm8_16k\lib'' -mdebug\stm8s103.map debug\stm8s103.lkf  &sharperror clnk debug\stm8s103.lkf:1 segment .text size overflow (1581)  The command: ''clnk -l''C:\Program Files (x86)\STMicroelectronics\STM8S_StdPeriph_Lib_V2.0.0\Libraries\STM8S_StdPeriph_Driver\src''  -o debug\stm8s103.sm8 -l''..\..\..\..\..\program files\cosmic\cxstm8_16k\lib'' -l''..\..\..\..\..\..\program files (x86)\cosmic\cxstm8_16k\lib'' -mdebug\stm8s103.map debug\s

Posted on May 20, 2012 at 09:43Hi, I have just received my discovery board and started to port my code over it but encountered the following problem : if I put a breakpoint at the entry point (first line of code of ''main'' function), I noticed that the breakpoint is hit more than once. Step by step works fine, but breakpoint + fail show this behavior. => So my only conclusion is that a RESET occurs when running. So I wrote the following little code to try to find out when and how it is reset : =============================================== #include ''stm8s.h'' void main(void) {     u16 cnt = 0;    // Counter          CLK_HSIPrescalerConfig(CLK_PRESCALER_HSIDIV1);     GPIO_DeInit(GPIOD);     GPIO_Init(GPIOD, GPIO_PIN_0, GPIO_MODE_OUT_PP_LOW_

Posted on April 22, 2010 at 18:37STM8L Internal temperature Sensor #stm8l-temperature-sensor

Posted on May 24, 2012 at 16:39 Hi again, i'm trying to set a pin to an alternate remapping pin, exactly i'm using TIM2 with PWM and i want channels in D2, D3 and D4. I have tried with this: #define OPT2 0x4803 FLASH_Unlock (FLASH_MEMTYPE_DATA); FLASH_ProgramOptionByte(OPT2, 0x02); FLASH_ProgramOptionByte(OPT2+1, 0xFD); FLASH_Lock (FLASH_MEMTYPE_DATA); with no luck, evenI started to get problems with SWIM, it said that opt byte complement was different. Anyway using STVPI was able to remove that stuff. I was able to make it work byflashing my code and then chaning the opt byte with STVP.... Another problem is that after it works (0x02 in OPT2 register) ifI read itI get the complemented value (0xFD), so i tried to read data memory positions 0x4801, 0x4802, 0x4804 and 0x4805 with no luck (none of them was 0x02). k=FLASH_ReadOptionByte(OPT2); I dont know what is wrong. Btw, afterI

Posted on May 23, 2012 at 16:11The linker is not case sensitive unless the -C flag is used on the command line Does anyone know how to pass this flag from within ST Visual Develop?  I can't just add -C as a user flag as STVD already passes -P and to the linker and the raisonance linker only accepts -CP not -P and -C as separate arguments.  How do I replace -P with -CP in STVD?  For example, can I stop STVD passing -P so I can add the -CP flag?If the linker is not case sensitive then the c source code needs to be written to avoid the linker seeing, for example, BOB and bob as the same symbol.  Which is giving me major code reuse problems. #stvd-raisonance-linker

Posted on May 18, 2012 at 14:22Hello, I need to built a capacitive proximity sensor with a range of at least 3''. What is the best sensor/controller that you advise me to use? I have been reading some things about STM8T143, but it's not easy to buy it. I need some samples to verify it's range and compatibility with our product. Is there any other sensor/controller from ST that is indicated to this task? Thank you all for your time!

Posted on January 09, 2012 at 10:54 Please help me about I use STM8S207 for HSI : I use UART3. I can be control it normally. with follow code --> UART3_DeInit(); UART3_Init((u32)9600, UART3_WORDLENGTH_8D, UART3_STOPBITS_1,UART3_PARITY_NO, UART3_MODE_TXRX_ENABLE); SerialPutChar('A'); And then I change to HSE. I can not control it such as I send 'A' char to PC but PC receive only garbage char not 'A' by I add this code --> CLK_ClockSwitchConfig2(CLK_SWITCHMODE_AUTO, CLK_SOURCE_HSE, DISABLE, CLK_CURRENTCLOCKSTATE_DISABLE);

Posted on May 10, 2012 at 14:25Hi,Im using STVD v 4.2.1 patch 2 on my STM8 project, the problem is when I want to compile, it gets stucked annoyingly for around 10 seconds then it starts to save first and compile the codings normally. I couldnt manage to get rid of this 10 seconds stucking period so far. This happens actually when STVD is trying to save the changes. If someone has any idea how to fix it or someone has had the same issue before..? Please, any help will be appreciated!Kadir. #stvd-slow-while-compiling

Posted on May 10, 2012 at 16:07bonjour ,je travaille à STM8S-discovery en utilisant STVD je reçois toujours cette erreur lorsque vous essayez de démarrer une version de débogage:Starting debug session...-> Emulator reset (usb://usb)...done.Opening application C:\Users\marwa\Desktop\ST\FWLib\project\STVD\Cosmic\Debug\stm8s105.elf...done.Source directories searched: c:\Users\marwa\Desktop\ST\FWLib\project\STVD\Cosmic\stm-lcd-clavier 1\proj4;c:\Users\marwa\Desktop\sTM-LCD-CLAVIER 1\proj4;$cdir;$cwdWarning: c:\Users\marwa\Desktop\ST\FWLib\project\STVD\Cosmic\stm-lcd-clavier 1\proj4: No such file or directory.Source directories searched: c:\Users\marwa\Desktop\ST\FWLib\project\STVD\Cosmic\stm-lcd-clavier 1\proj4;c:\Users\marwa\Desktop\sTM-LCD-CLAVIER 1\proj4;$cdir;$cwdWarning: c:\Users\marwa\Desktop\ST\FWLib\project\STVD\Cosmi

Posted on May 08, 2012 at 10:45Hello ST-Community, I'm searching for a special STM8S-firmware-helpfile. In this file all firmware-functions are listed with arguments etc.. I already downloaded this file a while ago. But I can't find it now. I hope someone knows what I'm talking about and can post a link or something. Regards, derLars

Posted on June 01, 2010 at 12:45Real Time OS on STM8S #rtos #osa #stm8

Posted on July 10, 2010 at 04:04error:swim prog error[42006]

Posted on April 09, 2012 at 20:16i want to create a new source file for interrupt but I don't know how to do? Could tou help me????? STM8S105C6

Posted on April 26, 2012 at 18:51Hi, I have just recently started developing with the STM8S003F3P TSSOP20 device. I have been working through a number of peripherals, which have gone fine, but have now run into a roadblock. I am using the STVD with Raisonance toolset. What I am trying to do is get 2 PWM signals on the pins 1 and pin 20, that is TIM2_1 and TIM2_2. I noticed right off the bat that when using the firmware libraries, the PWMs didnt come up, so i tried to do a few different implementations and none seem to be able to make the PWMs go. So after investigating the address values for the configurations (located at base address 0x5300) i noticed that CCMR1 and CCMR2 are not getting set at all. These are at location 0x5305 and 0x5306. Even when i set the values directly and step through, right after the instruction completes, the value at those addresses remain unchanged. I thought the chip might be faulty so i trie

Posted on April 25, 2012 at 10:19I think this is wrong:CONST uint8_t SYSDivFactor[5] = {1, 2, 4, 8, 16}; /*!< Holds the different Master clock Divider factors */It should be like this:CONST uint8_t SYSDivFactor[8] = {1, 2, 4, 8, 16, 32, 64, 128}; /*!< Holds the different Master clock Divider factors */Because of this:typedef enum {  CLK_SYSCLKDiv_1   = (uint8_t)0x00, /*!< System Clock Divider: 1 */  CLK_SYSCLKDiv_2   = (uint8_t)0x01, /*!< System Clock Divider: 2 */  CLK_SYSCLKDiv_4   = (uint8_t)0x02, /*!< System Clock Divider: 4 */  CLK_SYSCLKDiv_8   = (uint8_t)0x03, /*!< System Clock Divider: 8 */  CLK_SYSCLKDiv_16  = (uint8_t)0x04, /*!< System Clock Divider: 16 */  CLK_SYSCLKDiv_32  = (uint8_t)0x05, /*!< System Clock Divider: 32 */  CLK_SYSCLKDiv_64  =

Posted on April 24, 2012 at 10:20Dear everyone,When the updating stm8l make use of the swim , Everytime the EEPROM data was erased. I don't know this cause.The download tool is RFasher7. Of course was disable the Erase EEPROM option in this tool.