Solved

..

Hi, Does TESEO-LIV3R require to connect EEPROM? If it's yes why do we need it? In my application i need to do hot start. Is it just enough to connect V_Back to external battery?Best regards Anas

..

124/5000Please help!I have an idea, information for someone about what this product might be and how it can be replaced. It would be urgent!Have a good day everyone.I ask for help with universal information that allows me to be uniformly unable to identify. Someone can already find with him what can be and what can be replaced. It would be very important, it can only be found in the off-road control unit of a single truck and cannot be used.I attach a photo.

Hi,I'm looking at replacing a STM32F103 with a STM32F151 in my design and couldn't find the PM0062 referenced in the AN3422 migration application note.Is there some steps I need to go through to get the flash / eeprom programming manual ?from the ANTo benefit fully from the information in this application note, the user should be familiar with the STM32 microcontroller family. You can refer to the following documents that are available from www.st.com.�? The STM32F1 family reference manuals (RM0008 and RM0041), the STM32F1 datasheets, and the STM32F1 Flash programming manuals (PM0075, PM0063 and PM0068).�? The STM32L1 family reference manual (RM0038), the STM32L1 datasheets, and the STM32F1 Flash and EEPROM programming manual (PM0062).

I've located a part which is over heating and need to replace? Is there an alternative or is this part still available anywhere ​

Hello, everyoneWhen I adjusted the Angle in the designer, I got a lot of decimal places.why is this？I only use the buttons in the designer to adjust the Angle./korry

I have successfully built and downloaded the motor control application using ST motor control workbench and the CubeIDE etc and can connect to flash and step through my program. However when it comes to using CubeMonitor i get an error giving "not connected ! Unknown JTAG chain (16)"In the config screen i can flash the LED on the board ... I have tried both protocols SWD and and JTAG .. Can i use monitor with the BG431B-ESC1 board ?Many thanks if youve got this far ....

Hi, i want to make a transparent clock on the background in all screens. So i think Alpha value is the only method to make transparency on two screens. And Analog clock and container don't have Alpha in their library. Could you please let me, how to set alpha value to an analog clock or any container.Or let me know if there is any way to make transparent screens without alpha value.Thanks and Regards,Bala

Hi,In my project two 16 bit timers chained together to achieve 32bit capture resolution. TIM3 as master timer and TIM4 as slave timer clocked by TIM3 overflow event (TIM4 works in external clock mode 1). Capture signal is connected to both timers input (CH2 for TIM3 and CH1 for TIM4). Master timer running at 36Mhz (72Mhz / 2).Captured data processed in TIM3(master) capture interrupt.Interrupt looks like:uint32_t period_ticks = 0; uint16_t ccr_msb = TIM4.CCR1; uint16_t ccr_lsb = TIM3.CCR2; uint32_t ticks = (ccr_msb<<16) + ccr_lsb; period_ticks = ticks - pre_tick_count; pre_tick_count = ticks; // pre_tick_count is static    Most time this code works as expected, but issue occurs when ccr_lsb (master timer captured value) == 0, than ccr_msb (slave timer captured value) is one less than expected, and period_ticks become 65535 less than expected. Looks like some sync problem when capture event at the same time with slave timer overflow event. Ugly workaround likeif (ccr_lsb

Hello, Can we, now, generate a STM32L4R9AI project with STM32CubIde including TouchGFX Middelware ? X-CUBE-TOUCHEGFX v4.13.0 offer this possibility or not yet ?Tankyou.

HAL does not work in * .hpp and * .cpp files. Can it be bypassed?

Hello, I am trying to make communicate a NUCLEO STM3F030 with a STM32F030K6T6 mounted on a custom pcb.Tx sends from NUCLEO is ok when i check it on an oscilloscope but when i connect the power supply of my pcb on the NUCLEO (or even on an external power supply), the TX low state level is shifted from 0 to 600mV without understanding why. Here are my connections:VDD (5V) of the pcb is connected to the 5V pin of the CN6 arduino connector GND of the PCB is connected to any ground on the arduino connector (let's say GND pin under 5V pin)Rx of the STM32F030K6T6 (pin PA10 without any HW component on the line) on the custom pcb is connected to the TxUART1 of the NUCLEONote: i observe directly at the oscilloscope the Tx signal and the GND discussed above.Did i do something wrong or missing anyconfiguration?Thank you in advance,

environmentTouchGFX4.12.3Select STM32F746G Discovery Kit in APPLICATION TEMPLATESelect Blank UI in UI TEMPLATE and createCreation of TouchGFX Application failed.Why?How can I check the error log?Thank you.

I'm using a custom board with a STM32WB50CG part. When I send this:0x10 0xFC 0x52 0x00 (FUS_GET_STATE) or any command for that matter, I always get this back:0x11 0x0E 0x04 0xFF 0xFE 0x00 0xFE 0x00I've tried this while running the bootloader code as well as my own code.Anyone see the error in my command? I've mostly followed AN5185. But there's errors in that app note. For example Section 6.1 says FUS only uses the device information table and system table, yet the bootloader also fills in the async event table. Only after filling in that table do I see the event announcing CPU2 is up and running FUS.

Hello. I've built a sensor similar to that pictured in 'Figure 3. H sensor (single layer)' from the AN4313 Projected sensor design document. I'm using it in conjunction with the Touch Driver library as part of the STM8TL5x_STMTouch_Lib_V2.1.0 touch library.When I touch the sensor, I reliably get TSL_STATEMASK_DETECT states (normally preceded by DEB_DETECT states). When I stop touching the sensor after a moment, I reliably get RELEASE states (usually preceded by a few DEB_RELEASE_DETECT states). But NOT when the touch is long (greater than a second or so). In that case, I always get intervening CALIBRATION states that precede subsequent RELEASE states and those RELEASE states are often transmitted while the sensor is still being touched. And that is complicating the ability to determine the moment when the sensor is no longer touched. My goal is to determine the moment when the sensor is touched and the moment when it is no longer touched with equal reliability no matter how long the to

Posted on February 22, 2017 at 10:26Hi everyone, I'm trying to get the internal temperature on my STM32L0.I have write the major part of the script but unfortunally the reading value is 0.Does anyone can have a look on my script and tel me if you see something ?Thank you very much for your helpRegards Simon&sharpdefine TEMP130_CAL_ADDR ((uint16_t*) ((uint32_t) 0x1FF8007E))&sharpdefine TEMP30_CAL_ADDR ((uint16_t*) ((uint32_t) 0x1FF8007A))&sharpdefine VDD_CALIB ((uint16_t) (300))&sharpdefine VDD_APPLI ((uint16_t) (330))int32_t ComputeTemperature(uint32_t measure){      int32_t temperature;      temperature = ((measure * VDD_APPLI / VDD_CALIB) - (int32_t)*TEMP30_CAL_ADDR );      temperature = temperature *(int32_t)(130-30);      temperature = temperature /(int32_t)(*TEMP130_CAL_ADDR -*TEMP30_CAL_ADDR);      tempera

I have tried making a Project from scratch and selecting the C++ during the wizard, and also tried converting an existing project by going to properties and selecting convert to C++.It just doesn't seem to be a C++ project.I'm using a STM32L476RG dev board and select this board in the wizard process. I select the C++ option but none of the produced files have a CPP extension, including the main.c. If I put the following in the main.c file:#include <string> // I do not get an error on this line but...string fred = "Fred"; // produces an error (or two)../Core/Src/main.cpp:32:1: error: 'string' does not name a type; did you mean 'stdin'? string fred = "Fred"; ^~~~~~Is this the correct way of generating a C++ project?Does the main file need to be main.c or main.cpp?Is there anything else I need to change?Thanks,Neil

Hello all,I'm trying to prototype a shutdown mode with a RTC alarm.I'm flashing the LED 5 times, then I set-up the RTC calendar, clock and alarm A (5 seconds after set-up clock). Then I go to shutdown mode. Everything works when I program my system (now testing with a 432KC Nucleo) and go to debugging. I see 5 LED flashes, then a 5s pause, and then 5 flashes again (forever). But when I unplug the USB, and plug it again, the system goes to shutdown but never wakes again.I'm using __HAL_RCC_PWR_CLK_ENABLE(); HAL_PWR_EnableBkUpAccess();just before configurating RTC to avoid parasitic protection, and also wait for sync after each write to RTC registers,but no success.This is my code, mainly MX generated and ST firmware examplesint main(void){ HAL_Init(); SystemClock_Config();  MX_GPIO_Init(); __HAL_RCC_PWR_CLK_ENABLE(); HAL_PWR_EnableBkUpAccess(); MX_RTC_Init(); MX_USART2_UART_Init(); while (1) { for(int i =0; i < 5; i++ ){ HAL_Dela

..

I am trying to compile the ST25RU3993_Eval fw project provided with the SDK. But the build process fails due missing files common_hostdevice_clib.h and stuhfl_testsAPI.h, where I can get those?Thanks

My code here:... @ some code ... end: nop b end   thread0: mov32 r1, 0x4001100C @ GPIOC_CRH address ldr r0, [r1] orr r0, 0x8000 @ switch_on C15 only str r0, [r1]   b end   nvic_systick: push { lr } @cpsid i mov32 r1, 0x4001100C @ GPIOC_CRH address ldr r0, [r1] eor r0, 0xA000 @ toggle pin state on C13 & C15 str r0, [r1]   adr r2, thread0+1   @push { r2 } <<<<---- EVIL INSTRUCTION pop { lr } bx lrCode works well, but i want to controller going to 'thread0' function after returning from interrupt.GDB says:(gdb) info all-registers r0 0x0 0 r1 0xed04 60676 r2 0x1e1 481 r3 0x8a1e8883 -1977710461 r4 0xef5fffff -278921217 r5 0xfffbffee -262162 r6 0x21136d6a 554921322 r7 0x7a8191d 128456989 r8 0xf7efbf75 -135282827 r9 0xfffffffb -5 r10 0xca444668 -901495192 r11 0xc2378b49 -1036547255 r12 0xff5bbfdf -10764321 sp 0x20005000 0x20005000 lr 0xffffffff 0xffffffff pc 0x1ce 0x1ce xpsr 0x41000000 1090519040 msp 0x20005000 0x20005000 psp 0x9f48dd1

Hi.​This is my system.STM32F103 - ST25DV <-> ST25R3911 <-> STM32F091 <-> CAN <-> PC ​In my system, st25r3911 and st25dv communicate through FTM function. ​And the system communicates with a period of 100 msec.​Generally, communication is good, but data is intermittently broken.I Implemented it based on RFAL. Even if the return rfalST25xVPollerFastReadMessage is ERR_NONE, the data is broken.So, when the data corruption occurs, I read the FTM of tag using S25R3911 EV board and I check ​the data that is not corruption.So I always add the CRC code in my message.Is this normal case?

Hi,First time poster here, I have looked around for answers and didn't find anything that could help me. I also tried to reach out to ST but they doesn't want to help and they are throwing me to local suppliers instead.So here's the thing, the ADC isn't able to go through all the values, I can reach all the range ( 0 to 4095 ) but sometimes it's skiping few steps. According to the datasheet, it's normal to have a +/- 3 step error and I understand that. But I am seeing bigger steps here.The configuration :ADC in scan mode, scanning 11 channels at 112 cycles per samples.ADC transferring data through DMA when a conversion is doneAn external trigger from Timer2 starts the scan every 20msThe clocks :HSE of 16MHzHCLK of 84, so APB1 is at 84MHzADC prescaler at 4, so 21 MHzBefore going through the code, I have to mention that I have tried few things to get rid of this behavior:Using HSIUsing ADC Interrupts instead of DMAScanning only 1 channelDividing APB2 by 2Tried every sampling rate availab

I have a Nucleo F103 board on which I'm playing with some code to generate a variable bit rate FSK data stream. The code seems to generate the right signal but at twice the expected frequency.I have searched these boards and found one question for exactly the opposite, which hints that I may have misread the data sheets or not spotted some subtle detail. From what I can tell, timer 3's internal clock is the APB1 (low speed) clock. My code sets up :SYSCLK to 72MHzAPB1 to 36MHzTIM3 pre-scalar to 35ARR to 116 or 204 and CCR to half thatI was expecting this to give me output signals with 116us or 204us cycle times - timer clocked at 1MHz - but I see half that, as if the pre-scalar is being clocked at SYSCLK instead of APB1.What have I missed?