Some common problems encountered when debugging STM8-EEWORLD

Collect

Some common problems encountered when debugging STM8 are code optimization and not using 32-bit characters in interrupts.

When using the minimum compilation of the code, some parameters may be optimized. If there is sufficient code space, it is best to use the default code compilation format.

Using 32-bit characters in interrupts can cause conflicts with applications. For example, the correct length of a 32-bit byte is more than 100, but if a conflict occurs, it becomes 6,500.

This is the reason why infrared is constantly being sent.

Keywords：Debugging Reference address：Some common problems encountered when debugging STM8

Previous article：stm8f103 debugging problem
Next article：Causes and solutions for STM8S error messages

Recommended ReadingLatest update time:2024-11-23 07:14

IAR FOR STM8 study notes firmware library GPIO

After some struggle, I decided to use the official firmware library. Download a STM8S firmware library from the Internet, remember it is FOR IAR. Find the IAR template inside and you can start using it. These are all pre-written library functions that can be called directly, but you must first read and under

[Microcontroller]

IAR FOR STM8 study notes firmware library GPIO

STM8 data @near@tiny definition

How to assign a variable to a specific address Example: unsigned char temp_A@0x00; //define unsigned variable temp_A and force its address to be 0x00 unsigned char temp_B@0x100; //define unsigned variable temp_B and force its address to be 0x100 @tiny unsigned char temp_C; //define the unsigned variable temp_C

[Microcontroller]

STM8 AWU ultra-low power mode

__interrupt void AWU_IRQHandler(void) { AWU- CSR = AWU- CSR; /* Clear the update interrupt flag*/ } void Enter_Halt() { CLK_DeInit(); AWU_DeInit(); AWU_Cmd(ENABLE); CLK_SlowActiveHaltWakeUpCmd(ENABLE);//Enter ultra-low power mode asm("halt"); } Welcome to use Markdown editor to write blog

[Microcontroller]

Summary of STM8 usage problems 2----STVD (COSMIC) defines variables to specify their types and bit definitions

Summary

[Microcontroller]

STM8 development environment construction (revised version)

Some of the steps I wrote before are bullshit. I don’t know why no one has given feedback. I mainly recorded them for myself. I wanted to write them well, but when I got to the last step, I used the Backspace key to delete, and it returned to the previous page. I also had to manually enter the width when uploading pic

[Microcontroller]

STM8 development environment construction (revised version)

STM8 study notes - timer timing function and interrupt related

All timers are similar, they just count, set the overflow flag, and generate an interrupt if interrupts are enabled. Speaking of interrupts, the interrupt vector table of the STM8S105 is as follows Time base unit: When the internal clock is selected, CK_PSC is provided by fmaster, and is divided by the t

[Microcontroller]

How to use the built-in bootloader of STM8

1. First, confirm whether the STM8 you are using has its own bootloader. Refer to the table below. 2. STM8 empty devices can directly use their own bootloader. 3. After STM8 is burned using SWIM, if you want to continue to use its own bootloader, you must set the optional byte to 0x55AA. As shown below: The method

[Microcontroller]

How to use the built-in bootloader of STM8

ST-LINK/V2 + STM8 + STVP download program + Error on Option Bytes

gdi-error : Option bytes read error: not complemented; please use a programmer Personally, I feel that ST-LINk/V2 is a scam. I wasted a day looking for the cause! The first step is to connect, which must be correct: LED Status Description Flashing red: The first USB enumeration process after ST-LINK/V2 is connecte

[Microcontroller]

ST-LINK/V2 + STM8 + STVP download program + Error on Option Bytes

Popular Resources
Popular amplifiers