STM8 MCUs

Hi, I want to use external clock 16 MHz.So I implemented the following code.CLK_ClockSwitchConfig(CLK_SWITCHMODE_AUTO, CLK_SOURCE_HSE, DISABLE, CLK_CURRENTCLOCKSTATE_ENABLE);It was confirmed that 16MHz oscillated when programmed from STVD.However, when the same firmware is programmed from STVP, 16MHz does not oscillate.Why?Regards, Gotoda​

Hello everybody,how can I count which pin triggers an interrupt, but not multiple times? I have written the following ISR. INTERRUPT_HANDLER(EXTI_PORTB_IRQHandler, 4) { data = (uint8_t)GPIOB->IDR& 0xF; if((GPIO_PIN_0 & data )== GPIO_PIN_0) { counter_Pin0++; } if((GPIO_PIN_1 & data )== GPIO_PIN_1) { counter_Pin1++; } }I first store the first four bits from GPIOB port in data and then I mask the bit form the pin. But as you can see in the picture, it is also counted when Pin 1 triggers an interrupt. The sensors have a small delay to each other, but are LOW for a certain time. I actually have 4 sensors, each of which are sometimes LOW at the same time, but trigger an interrupt at different times. Then I do not count 4 interrupts at Pin0 but 11 for example.

Sir,I am working on STM8S003F3P Controller which is interacting with LoRa SX1276 HPD Module. I have the experience of working on SPI and have enough knowledge to configure it. I am able to write the data to SX1276 (I will tell you how). But, while Reading the data from SX1276, SPI_DR register is always acting as follows.If configured as input (Pulled up or High Impedance state), it is read as 0xFFIf configured as Output, it is read as 0x00 or 0xFFProcedure to read the data is as followsSend the address first (MSB for Read or Write and 7 bit Register addresses of SX1276)After successful transmission, Send data to be written or dummy to read the data in address sent in step 1.I have checked the waveforms for 3 to 5 registers using CRO and data is read accurately. but while keeping the controller in debug mode, unable to read the data in SPI_DR Register.Tests Performed:

I've got a new STEVAL-ISA164V1 Board.The problem looks like this:When connecting with the ST SMED Configurator there is a warning:The chip on my board is double checked a STNRG388A (well that's what is printed on the chip)I can connect and it looks like i could load a model from an Example - but nothing happens on the outputs.So i tried to load the lasted FW with the console tool, but this also does not work - i tried several times

How can I fix the super long delay and weird ACK glitch with I2C on STM8S?I'm having some troubles with I2C communications between a raspberry pi and STM8S. The STM8S is a slave transmitter and I2C is running at 100 KHz. It works much the time, but I get a bad reading about 5% of the time. It seems to be due to way rpi implements clock stretching, and what seems like an excessive delay after being addressed.In this case the logic analyzer is showing what I expected the rpi to read, but it received 0x90E1 instead of 0x10E1. It seems to be due to the super stretched and compressed clock, and the unexpected high signal during during the ACK after being addressed.I have the STM8S running

I am writing from an esp32 I2C master to a stm8s103f mcu. My scope shows the esp is sending a clean read addr byte onto the scl/sda pins (PB4/PB5). But the stm8 is not running my interrupt routine. I have a gpio pin that should toggle when the interrupt happens. I have tested this debug pin elsewhere in my code. Also the stm8 is not responding with an ACK.Here is my init code. I would be very grateful if anyone can give a hint as to what stupid thing I'm doing (I've never met a smart bug yet, always stupid). void initI2c(void) { // set I2C (IRQ19) software interrupt priority to 2 (next to lowest) ITC->ISPR5 = (ITC->ISPR5 & ~0xc0) | 0x00; // 0b00 => level 2 I2C->CR1 &= ~I2C_CR1_PE; // start with peripheral off (PE = 0)   // I2C_CR1_NOSTRETCH | // 0x80 Clock Stretching Disable (Stretching enabled) // I2C_CR1_ENGC | // 0x40 General Call Enable (master only) // I2C_CR1_PE | // 0x01 Peripheral Enable (set at end) I2C->CR1 =

I've been using vscode as my editor since the one in stvd seems to have features from 15 years ago. I have files also open in stvd since clicking on errors opens files. This means that when I switch to stvd from vscode I get the warning about files changing externally. This is very annoying and I do this constantly. Is there a way to turn off this warning? Or, even better, could clicking on errors open up files in vscode?

I would like to use the STM802 as a supervisor but I need to disable the watch dog intervention in certain conditions (for example firmware update).The manual says that the WDI pin cannot be left floating to block WD intervention.Is there any other way?Is there another ST IC that allows this function?The system is 3.3V ThanksRobert

Hi there! I am using STM8s for UART communication but recently I found that UART Rx does not work sometimes. I am using UART Idle interrupt for Rx at this moment. Could someone suggest a way to me for debugging?Cheers,Morris

Hi,Good day everyone.I am trying to setup SEMTECH SX1231 transiever to send and recieve RF packets by having SPI connection between SX1231 and STM8 controller. Its getting really hard to achieve this because of unknown configurations. Has anyone achieved this? Any example code will be of great help !Thanks,Ankush

Hello, I am getting the below error. I am using the eclipse workspace for debugging. xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2021-10-16-21:19)Licensed under GNU GPL v2For bug reports, read http://openocd.org/doc/doxygen/bugs.htmlError: Debug adapter doesn't support 'swim' transportD:/work/Renu_Projects/Compiler/STM8S/xpack-openocd-0.11.0-2-win32-x64/xpack-openocd-0.11.0-2/bin/..//scripts/target/stm8s.cfg:7: Error: in procedure 'script' at file "embedded:startup.tcl", line 26at file "tools/openocd-v0.10.0-scripts/stm8s105.cfg", line 8at file "D:/work/Renu_Projects/Compiler/STM8S/xpack-openocd-0.11.0-2-win32-x64/xpack-openocd-0.11.0-2/bin/..//scripts/target/stm8s.cfg", line 7

​Excuse me, set the GPIO(Pin B5) corner to True Open Drain and whether to allow Inject current on any other pin(+-4mA)?

I downloaded the blink LED demo from ST and loaded in that nucleo board to check out how things worked, soon I found out that every time when I pressed the "USER" Button (Connected to PE4), It won't be able to successfully switch to next blink pattern 100%, It sometimes would fail to switch over. I thought it maybe was a bad button issue but I debugged with IDE inserts a few breakpoint into the codes and I found some interesting behavior from the Interrupt Handler:Related Code as follows:NTERRUPT_HANDLER(EXTI_PORTE_IRQHandler, 7) { /* In order to detect unexpected events during development, it is recommended to set a breakpoint on the following instruction. */ #if defined(USE_STM8S_NUCLEO_64) if(BlinkSpeed == 3) { BlinkSpeed = 0; } else { BlinkSpeed ++; } #endif /* USE_STM8S_NUCLEO_64 */ }It just a simple code for switching modes, If I insert breakpoints in line 7,9 and 10 and execute line by line in debug mode, it work out per

error

I am using the STM8L151C8T6 microcontroller (high density with 64k flash) and the StandardPeripheralLibrary v1.6.1, as well as the IAR Embedded Workbench for STM8 v3.11.1. I need to write and erase blocks of flash memory with high speed. For this I want to use a block writing. In the peripheral library there are functions FLASH_ProgramBlock (...) and FLASH_EraseBlock (...) for this. According to the documentation, these functions should be run from RAM. I have uncommented #define RAM_EXECUTION (1) in stm8l15x.h file.The problem is I am getting a compiler warnings:

I found their datasheet,which said that their ROM codes are different, but I'm not sure if they can be agreed through software.

Per my QC observations, seeing multiple pieces across multiple lots with cracks on the bottom surface in between contacts and pads, as well as several samples with very rough marks on the contacts. Using the high powered scope, cracks were confirmed, as well as odd, textured metal contacts. Please advise if this is due to design & material selection related.

Hello,I am trying to program a STM8S103F3 on one of these chinese breakout boards with an original ST-LINK/V2 programmer. Everytime I try to read/ write something I get: "Error : Cannot communicate with the device !Check the SWIM cable connection and check all the needed pin connections on the SWIM connector.If the application code uses Swim Disable and Reset pin as Output or has disabled SWIM Clock Divider:Try Now to SWITCH OFF and ON the application Power Supply while NRST Reset pin is forced low.Error : < PROGRAM MEMORY reading failed."I doesnt matter if its program memory, data memory or option byte.I am pretty shure I connected it right, I also tried every possible combination until now. I also tried connecting VCC and GND directly to the board, because the SWIM connector had no proper ground connection. It is already the second one of these boards I am trying, as I thought the

I also tried to make some configuration changes in the code, like putting the halt mode or disabling the timers.Kindly suggest me to solve this issue

Hi,Reference: AN5179 - RS232 communications with a terminal using the STM8 Nucleo-64 boardshttps://www.st.com/resource/en/application_note/dm00513075-rs232-communications-with-a-terminal-using-the-stm8-nucleo64-boards-stmicroelectronics.pdfAN5179 page 6 have a circuit of RS232 communication with a terminal using NUCLEO-8L152R8 board and I want to know if the same circuit can be used with STM8L-DISCOVERY changing only USART port.I have two questions:1. In STM8L152R8 datasheet we can see that almost all ports including USART default port and PB5 are FT (5V tolerant). But in STM8L152C6 datasheet we can see that almost all ports including USART port and PB5 are TT (3.6V tolerant). Is this a mistake in STM8L152C6 datasheet or

Since I short connect VLCD and PD1, when there is uart communication, there will be communication waveform like below on VLCD pin, will this affect MCU work?  I set VSEL to 1(External source) by the code below in MCU initialization CLK_PeripheralClockConfig(CLK_Peripheral_LCD, ENABLE); LCD->CR2 |= 0x01; CLK_PeripheralClockConfig(CLK_Peripheral_LCD, DISABLE); 

Hello,I try to write into program flash in block write. Therefore I have a functionwhich is executed from RAM:void ram_flash_write_block(uint32_t startaddress, const uint8_t *buf) { uint16_t i = 0; // enable flash block write FLASH->CR2 = FLASH_CR2_PRG; FLASH->NCR2 = (uint8_t)(~FLASH_NCR2_NPRG); // write data from buffer to flash for (i = 0; i < FLASH_BLOCK_SIZE; i++) *((volatile uint8_t*) (uint32_t)(startaddress + i)) = ((uint8_t)(buf[i])); //Wait for write operation to complete according to PM0051, Page 18, Step 6 while((FLASH->IAPSR & FLASH_IAPSR_EOP)!=FLASH_IAPSR_EOP); }FLASH_BLOCK_SIZE is 128 (I am on STM8AF5288). startaddress in my case is 0xC000.The program stops, if I write the flash control registers CR2 and NCR2consecutively. If I write only one if these registers, the program does not stop(but also does not write to flash...).This is a hint, that the block pro

Hello,I try to read from user flash. Everything is fine until I try to read from address beyond 0x10000. Then I get random values. I use SDCC (3.8.0 and 4.1.0, the behaviour is the same). My device is STM8AF5288 which has 64 KB of flash memory. A program which is located at the flash and occupies it beyond address 0x10000 runs fine (compiled with memory model large), but reading the flash using the StandardPeripheralLibrary function FLASH_ReadByte() returns random values.A similar question is already here:

Per corporate policy, USB Mass Storage devices are DISABLED on our corporate laptops. There is no means to get around it, these are the rules.Im Working on Stm8l_discovery boad with on board debugger, for debugging it need USB Mass storage ,How to disable this.Kindly help me on this.currently Debugger has v1.J0.S4