Solved

I am using the software of b-g431b-esc1 and the driver used in the board as per schematics is in my board the micro is RB series but the problem is with the Mosfet driver which has an active low signal, IR2108What changes do i need to make in the software to make it work? Will it be huge or minor changes? Please advise.

I have a board that is running well. There are about 50+ PCBs in production operating fine. The firmware is pretty complex, but the hardware relatively simple, just some SPI devices and some PWM outputs.I revved the board, and the new board doesn't work at all. Well, it works enough to execute some code, but not much. So to debug, I started with a blinky program:int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init();   while (1) { HAL_GPIO_TogglePin(FAULT_GPIO_Port, FAULT_Pin); HAL_Delay(1000); } }If I configure the RCC to use the HSI, the program gets as far as `HAL_Delay(1000)` at which point it chokes on `HAL_GetTick()`.If I configure the RCC to use the HSE (a crystal is present), the program only gets as far as `SystemClock_Config()`, where it again chokes on `HAL_GetTick()` or sometimes `HAL_RCC_OscConfig()`.By "choke" I mean it throws a HardFault. Though for a reason I can't understand, it won't execute my handler.So, the code runs ok using the HSI at 16

hello,For me stm32f746-disco has two versions.1) The first is the green PCB. The following label is attached. MBI1191 B-03 / 2154300550 -> LCD screen normal operation / LCD Touc normal recognition2) The second one is the blue PCB. The following label is attached. MB1191-F746-C01 / C220200062​ -> LCD screen normal operation / LCD Touc normal operation not recognizedThe purchase is Mouser, but first I bought the normally working red PCB and after 1 year I bought the BLUE PCB.https://www.mouser.kr/ProductDetail/STMicroelectronics/STM32F746G-DISCO?qs=KuGPmAKtFKV4xEByQ7IKqA%3D%3DI want to know why the touch recognition doesn't work normally on the newly purchased green PCB.

Hey,I was able to successfully flash the Starter Package following this article and after building the OpenSTLinux distribution following this, I'm having trouble with flashing it. After completeing the build process, inside the flashlayout_st-image-weston, there are 3 folders optee, extensible and deleteall. I was looking for trusted folder like in starter package but it is not available. Then I tried to follow article found here with cube programmer interface and through terminal with FlashLayout_sdcard_stm32mp157f-dk2-optee.tsv but i'm getting following error.Error: failed to download Segment[0]   Error: failed to download the File   Error: Download partition 0x05 failed   Error: TSV flashing service failedAfter that I tried to flash with FlashLayout_sdcard_stm32mp157c-dk2-optee.tsv in Starter Package but it also showed the same issue. I have attached the cube programmer terminal output. Apreciate if anyone can help me with this.Thanks.

I am trying to incorporate the X-Cube-EEPROM package into an existing STM32WB55 Nucleo design that I have. In the process one of the compile errors refers to an RCC bit:​'RCC_CR_HSEBYP' undeclared (first use in this function); did you mean 'RCC_BDCR_LSEBYP'?​Your stm32wbxx.h file within the CMSIS/Device/ST/STM32WBxx/Include folder calls out the RCC_CR_HSEBYP as bit 18.​This bit doesn't even exist in the manual....What kind of code is this???This is VERY subpar.

I am trying to connect LCD (SPI interface) to my custom stm32f030c8 board, PB13 -> SCK, PB15 -> MOSI (Transmitt only mode).I created a test project with cube configurator (attached a screenshot).I did not change anything in the generated code, just added sending test:/* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ADC_Init(); MX_SPI2_Init(); MX_TIM1_Init(); MX_TIM14_Init(); MX_TIM16_Init(); MX_TIM17_Init(); MX_USART1_UART_Init(); /* USER CODE BEGIN 2 */   uint8_t testData[] = { 0x11, 0x22, 0x33, 0x44 }; HAL_SPI_Transmit(&hspi2, testData, 4, 5000); /* USER CODE END 2 */   /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */   /* USER CODE BEGIN 3 */ }I uses ST-Link to debug. All initializations pass so as the transmit subroutine, but there are no any signals on MOSI and SCK appears (I use oscilloscope with sync by signal front). I tried to change pins mode to general outputs and to toggle output

Hello everybody:I’m facing the following problem. To boot the microcontroller right know I have pin PA14 – BOOT0 to GND through a 10K pull down resistor (This pin is also shared with SYS_SWCLK) and BOOT0, nBOOT_SEL bit to 0 -> Boot area main Flash memory.I want to achieve the same thing with nBOOT_SEL, nBOOT1, NBOOT0 bits. To do that, I connect the programmer and access the option bytes -> user configuration -> set the pins as shown in the image and apply.When I disconnect the programmer, power off then power on again the program doesn’t boot (now PA14 – BOOT0 is not connected with pull-down resistor). I am doing something wrong?Thanks in advance.

 JW

Hi, I notice that CubeMx allow choose 16-bit resolution but STM32L476 has range from 6 to 12 bit. When I generate code I can't compile it:Moreover in datasheet we read on page 1: but it's only one information about mystic 16-bit resolution :D

Hi,coudl someone paste simple code to send some bytes between I2C1 and I2C2 on one board?Prefer HAL. I try this: uint8_t data = 69; uint8_t data2 = 0; HAL_I2C_Master_Transmit(&hi2c1, 32, &data, 1, HAL_MAX_DELAY); HAL_I2C_Slave_Receive(&hi2c2, &data2,1,HAL_MAX_DELAY);and HAL_I2C_Slave_Receive_IT(&hi2c2, &data2,1); HAL_I2C_Master_Transmit(&hi2c1, 32, &data, 1, HAL_MAX_DELAY);but not works. Slave address is 16 (shift left is 32).

..

..

..

Hi fellas,Whether STM's SPC5x AUTOSAR MCAL is free or licensed version. Also, its been told, it provides CDD and no AUTOSAR OS,for which FreeRTOS is used. Whether this FreeRTOS version for AUTOSAR is free/licensed?

I am using development board MB1519C. I was trying to disable trust zone in my board. For that I have followed below step in stm32cubeProgrammer.Open option byte and set RDP level to 1 and apply and power reset and then RDP 0 along with trust zone uncheck (0).After that I am not able to connect with my board via stmCubeProgrammer.It shows below error. I also tried with hardware reset configuration. Guide me to resolve issue.  Also tried with UART mode, In that case I received below error.How to disable RDP?

Hello!I have my ADC DMA setup so that Timer 1 will trigger a conversion with a specific frequency. Both DMA continuous requests and Continuous conversions are disabled. DMA is set to Normal mode.When the buffer is full and HAL_ADC_ConvCpltCallback is triggered, I stop the ADC with HAL_ADC_Stop_DMA, and some processing is performed on the DMA buffer. Once the processing is completed the ADC is restarted with HAL_ADC_Start_DMA.This all works as expected until the MCU enters and exits from STOP mode. I'm unable to restart the ADC, the DMA buffer still contains the previous data, and HAL_ADC_ConvCpltCallback is never triggered.Here's my code:while (1) { /* USER CODE END WHILE */ /* USER CODE BEGIN 3 */   HAL_GPIO_WritePin(LD3_GPIO_Port, LD3_Pin, GPIO_PIN_SET); HAL_ADC_Start_DMA(&hadc1, (uint32_t*)sampleBuffer, samplesPerFrame);   while (dataReadyFlag == 0) ; dataReadyFlag = 0;   // TODO: Process sampleBuffer   if ((uint32_t)(HAL_GetTick() - prevTime) > a

Hi!We are working on a remote FW update feature, where we receive the FW binary from another MCU via UART4 in chunks. The process starts with erasing a region in flash bank 2 (page 256 - 406). Then it receives the FW image in 2K chunks, CRC checks them and flashes them. Finally, it CRC checks the entire new FW in the flash memory. If everything is fine it will:uint32_t usedBank = LL_SYSCFG_GetFlashBankMode();if (HAL_FLASH_Unlock() != HAL_OK) { consoleLog(LOG_INFO, "The HAL_FLASH_Unlock process failed!"); return FirmwareUpdateResultCode::flashLockUnlockError; } if (HAL_FLASH_OB_Unlock() != HAL_OK) { consoleLog(LOG_ERROR, "The HAL_FLASH_OB_Unlock process failed!"); return FirmwareUpdateResultCode::flashOBLockUnlockError; }   consoleLog(LOG_DEBUG, "Firmware update data content uploaded successfully."); rtosTaskDelayInMilisec(500);   FLASH_OBProgramInitTypeDef optionBytesStruct; HAL_FLASHEx_OBGetConfig(&optionBytesStruct); optionBytesStruct.OptionType = OPTION

I am analyzing the UART data frame of an outsourced device that uses the STM8S105 MCU. The data frame specification is:* 1 start bit,* 8 data bits, * 1 parity bit,* 2 stop bits.Therefore I expect a data frame as in the below Figure 115 from the STM8 reference manual RM0016. However, both the logic analyzer and oscilloscope show an extra bit after the 2 stop bits. Then the next data frame begins. This is illustrated in the second figure below.Question: what feature creates the extra bit? This is unexpected.Is it possibly related to the break character feature?Thank you for your response.Figures 1 and 2 ...................

We want to allow customers to download firmware directly.Are you trying to pass the STM32CubeProgrammer\bin file, no licensing issues?I'm trying to make a batch file so that I can download it right away.I've tested it. If you pass only this file and the database file together, there seems to be no problem with downloading.We ask if there will be any licensing issues if we pass this file on.

We are designing a board that uses the ST25RU3993 Reader. We will have a Raspberry Pi 2040 microcontroller on the board for communication. Do you have any firmware or code that can be used to communicate to the reader from this Microcontroller?

We recently udated from OpenSTLinux v2.1 to v4.1. The boot chain is solid, but occasionally we are getting TEE aborts (trace listed below). I am not sure exactly how to debug this, any help would be appreciated. E/TC:1 E/TC:1  Core data-abort at address 0x2fff8805 (translation fault) E/TC:1   fsr 0x00000207 ttbr0 0x2ffd8020 ttbr1 0x00000000 cidr 0x0 E/TC:1   cpu #1         cpsr 0x000001f3 E/TC:1   r0 0x2fff8805     r4 0x2ffda889   r8 0x2ffda889  r12 0xffffffe0 E/TC:1   r1 0x2ffcda91     r5 0x000000f7   r9 0x00000000   sp 0x2ffda788 E/TC:1   r2 0x2fff8805     r6 0x00000000  r10 0x2fff8805   lr 0x2ffcb297 E/TC:1   r3 0x2fff8806     r7 0x2ffda870 &n

I'm trying to use the Motor Profiler software through my Motor Controller SDSK 6.1.1. When I launch the profiler, I Select my boards - Nucleo-F302R8 and X-Nucleo-IHM07M1 3Sh. Then I set the motor parameters to match my motor Bull Running BR2804. When I then hit Connect I get a warning to update the board firmware. I select Accept and then the process gets stuck forever on the "Checking ST-Link connection" step. What might be the issue here?

Hello!I'm trying to run SPI in Transmit Only Master mode.It's strange - result of HAL_SPI_Transmit is HAL_OK but I can't see any signals on SCK and MOSI pins.main.cint main(void) { /* USER CODE BEGIN 1 */   /* USER CODE END 1 */   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init();   /* USER CODE BEGIN Init */   /* USER CODE END Init */   /* Configure the system clock */ SystemClock_Config();   /* USER CODE BEGIN SysInit */   /* USER CODE END SysInit */   /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_SPI3_Init(); /* USER CODE BEGIN 2 */   /* USER CODE END 2 */   /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { uint8_t dacRegisterAddress = 0xAA; uint8_t dacRegisterData = 0xAA; uint8_t sendData[2] = {dacRegisterAddress, dacRegisterData};   HAL_GPIO_Write

uVision V5.38.0.0 Trying to compile first program for STM32G0 and don't even get to the real compilation errors yet.Single file except for includes:#include "stm32g070xx.h"#include "stm32g0xx_hal.h"The warning and error are:ERNode_G070.c(61): warning: In file included from...C:/Users/ashto/AppData/Local/Arm/Packs/Keil/STM32G0xx_DFP/1.4.0/Drivers/CMSIS/Device/ST/STM32G0xx/Include\stm32g070xx.h(103): warning: commas at the end of enumerator lists are a C99-specific feature [-Wc99-extensions] USART3_4_IRQn              = 29,    /*!< USART3, USART4 globlal Interrupts                                */                       &

Unless I'm missing something, I don't see a HT flag documented in the STM32L0X0 reference manual in the USART_ISR register. I see the TC, idle, etc. flags. So how is that interrupt getting triggered (because I have verified it does get triggered)? EDIT: Also don't see it if I examine the UART SFR in the CubeIDE.