Solved

Table 226 on page 906 has an entry HRTIM_TIMxCMP1CR <- I don't think this is a real register.Section 27.3.8, page 888 second line in last paragraph says "any of the 5 timers". I think that should be 6 timers.Section 27.5.66, page 1050 says Bits 31:0 Refer to HRTIM_ADC1R bits description <- this should be HRTIM_ADC3RSection 27.5.67, page 1051 says Bits 31:0 Refer to HRTIM_ADC2R bits description <- this should be HRTIM_ADC4RSection 27.5.69, page 1055 has a footnote that should be at the end of section 27.5.68, page 1053.Section 27.5.68, page 1052 bit descriptions call out "ADC trigger 3 ...". If this same description is used for HRTIM_ADC1R, then the trigger number is wrong i.e. it should be "ADC trigger 1 ...". Section 27.5.69, page 1054 bit descriptions call out "ADC trigger 4 ...". If this same description is used for HRTIM_ADC2R, then the trigger number is wrong i.e. it should be "ADC trigger 2 ...".

Basically we have follwing problem: We have an App which reads out the ST25DV04K, behind we have STM32L011xxx which makes some calculations as well and the result is stored in the ST25DV04Kxxx. However sometimes the NFC field is not strong enough and the STM32 does not start and cosequently does not write new data in the EEPROM. So "old" data are read out from the EEPROM, does any one has a suggestion to check wheter the data in the EEPROM (ST25DV04K) has been new calculated? Best regards Christian

..

Hi STteam,my name is Himavanth, working as an Embedded Engineer at Supralax Electronics Pvt.Ltd. please have a look at the problem.@brief : We are working PD source solution(i.e. 60Watt (20V @ 3A max)) using STM32G081RBT6. We are taking USB-PD_Provider_1port as an Base reference project.@Reference : I have gone through each and every line of UM2552 reference manual I found really good information to setup the USBPD stack.@context:I am not able to find the PDO initialization Even for provided example (i.e USB-PD_Provider_1port )from the STM. I found the code template(attached below)regarding PDO definition and initialization of PDO. But I couldn't find any initialization process for PORT0_PDO_ListSRC(As control going to #ifndef __USBPD_PWR_IF_C loop not to else loop)/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file usbpd_pdo_defs.h * @author MCD Application Team * @brief Header file for definition of PDO/APDO valu

HiIn my design I want to place a dedicated STM32F for debugging with st-link via USB.Where do I get the initial binary code? and how do I flash the device with it?For my understanding following that I can use the st-link firmware upgrade utility.Thanks

Touchgfx Version: 4.15 not currently visible on the st company's site

I'm going back over a project trying to clean up all of the warnings.The first time i build the project there are a few hundred warnings. So i clean a few up and build again to make sure i didn't break anything but then all the warnings are gone. Can i change this behavior? I'd like the warnings to hang around please.Thanks.

On my STM32L151CB-A (external PCB), the following issue is occurring when using the internal Real Time Clock:I configure Date, Time and Alarm A using the initialization routines generated by CubeMX. The Alarm A is set to trigger 7 seconds after the beginning of program execution. The alarm interrupt is sent through the EXTI line 17. Clock source of the RTC is the internal LSI 37kHz oscillator with prescaler values 124 and 295 to generate a 1Hz tick.The RTC alarm interrupt is issued after 7 seconds - as we would expect. In contrast, the RTC Time Register TR (either accessed by RTC->TR or HAL_RTC_GetTime) does not seem to be incremented.The UART debug output yields:RTC TR00203000 RTC Seconds: 1800   RTC TR00203000 RTC Seconds: 1800   RTC TR00203000 RTC Seconds: 1800   RTC TR00203000 RTC Seconds: 1800   RTC TR00203000 RTC Seconds: 1800 RTC TR00203000 RTC Seconds: 1800 RTC TR00203000 RTC Seconds: 1800 RTC ALARM A EVENT RTC TR00203000 RTC Seconds: 1800

Following the instructions found in en.FLASH-stm32mp1-openstlinux-5-4-dunfell-mp1-20-06-24.tar.xz and using create_sdcard_from_flashlayout.sh to write the data to an SD card did not work for me. When I inserted the card on the stm32mp157c-dk2 dev board and power up, nothing happens on the serial port or the units display. Things are working with the card shipped with the unit, so the HW is working.Is there a pre-built SD card image to write to a card to get the v2.0.0 equivalent of what was on the card that came with the dev board?As I'm posting this and scrolling back in my terminal window I notice warnings about sgdisk. Are those fatal? Here is a log of what I tried:```$ ./create_sdcard_from_flashlayout.sh ../flashlayout_st-image-weston/trusted/FlashLayout_sdcard_stm32mp157c-dk2-trusted.tsv [WARNING]: A previous raw image are present on this directory[WARNING]:   ../flashlayout_st-image-weston/trusted/../../FlashLayout_sdcard_stm32mp157c-dk2-trusted.raw[WARNING]: would

Hi,I just installed IDE v1.4.0. I can't find any example for the Nucleo-L476RG board from the Example Selector tabof the Target Selection window. The provided list of the boards doesn't contain L4 family as well as many other families (Lx, F1 and etc.). The examples can be found directly from the MCU family packs in the same way as for the boards included into the selection list. So the examples do exist while IDE doesn't find them.So I think that it is just a bug in the IDE configuration files. BR,Mikhail

I try to get the sample app and the sensor app running on a Nucleo-STM32F411RE together with a X-Nucleo-BNRG2A1 expansion. I configured everything as it was described in the corresponding docu. But I was not able to get it running. The device does not even show up in a Bluetooth scanner. I setup the same board with the older X-Nucleo-IDB05A1 many times and had no problems getting it running. Is there anything that is different with the X-Nucleo-BNRG2A1 expansion? I alread checked the jumpers. J10 is connected. J14 connects Pins 2 and 3. and J15 is open. What am i doing wrong here? I tried to debug the applications and found out that the hci_*** command don't return the BLE_STATUS_SUCCESS as they should do.Thank you very much for your help.

I have an application who requires a stable clock source in the whole temperature range but the power budget is tight, so we chose to use the MSI in sync with an external low power 32khz clock.To save extra power we send the core to sleep while it's not needed and wake on interrupt with the line (MSI is 2Mhz):HAL_PWR_EnterSLEEPMode(PWR_LOWPOWERREGULATOR_ON,PWR_SLEEPENTRY_WFI);then while testing the device we saw the output of one of the timers drifting too much.I connected the MSI to the microcontroller clock output and measured with the oscilloscope, the result can be seen in the second video attached. The clock is drifting with a sawtooth shape, the period of this sawtooth is about 220ms at room temperature and decreaeg with temperature, to about 1ms at 100°C.The same period can be seen on the input current of the system.This causes too much disturbances for my application.Then I found that if I enable the 'main' power regulator with this line:HAL_PWR_EnterSLEEPMode(PWR_MAINREGULATOR

Hello!I'm using a custom board with STM32F767 and external Flash memory connected to the QSPI (MX25L12835F).I want to create a simple test, where I read and write some data into the external Flash.In the first shot I want to use the normal SPI mode to:Readout the Manufacturer & Part IDSet the Write Enable Bit in the Status RegisterReadout the Status Register to check if the Write Enable Bit was set.So, the first setp (1.) is working fine. I'm getting correct data after reading out the Flash ID.But when I write to the Status Register and then read out the content, then nothing is changed. My expectation is that the WEL bit will change it's state to 1.Here the code from the main: //Readout the manufacturer and device ID sCommand.InstructionMode = QSPI_INSTRUCTION_1_LINE; sCommand.Instruction = READ_JEDEC_ID_CMD; sCommand.AddressMode = QSPI_ADDRESS_NONE; sCommand.AlternateByteMode = QSPI_ALTERNATE_BYTES_NONE; sCommand.DataMode = QSPI_DATA_1_LINE; sCommand.DummyCycles

Hi,I'm working on a project in which I use both ADC1 and ADC2 in independent mode, with JEOS of both ADCs as interrupt triggers. In the interrupt handler I do some calculations for current controllers. Mockup code below:void ADC1_2_IRQHandler(void) { if (ADC1->ISR & ADC_ISR_JEOS) { ADC1->ISR = ADC_ISR_JEOS; { <Do something> } }   if (ADC2->ISR & ADC_ISR_JEOS) { ADC2->ISR = ADC_ISR_JEOS; { <Do something> } } }The conversions of ADC1 and ADC2 are triggered by hrtimers (at different frequencies) and therefore JEOS flags of both ADCs can be set while the interrupt handler is still running. I would expect the interrupt handler to be re-evaluated immediately after it has finished, since there still is a flag set in its ISR. However, this does not seem to happen and the interrupt handler is triggered only after a new flag has been set.For instance, ADC2 has finished its conversion sequence so it sets JEOS -> Interrupt handler is called -&g

The Nucleo f429zi comes with a set of arduino avalaible pins compatible with the x-nucleo-ihm04a1 physical connections, but I´m not sure if regarding software it´s able to get a link between them. Can anyone help me?

Hello, I'm having a trouble to read or write bits on registers, for example I would like to change the comparator input minus pin, according to the RM I have to change the INMSEL bits in the COMP1_CSR register, but when I write this line code:COMP1_CSR = 0xF7854876 // just an examplethe IDE tells me that "COMP1_CSR is not declared", and it's the same thing with other registers, I cannot directly manipulate them...I'm using STM32 Nucleo L476.

Does load capacitance matter for a given device? Or does that only effect the caps you pair with the oscillator?

Is there a way to directly start M4 and run M4 firmware from BootRom.I am aware of the Engineering mode, however it requires the help of a debugger to copy the M4 firmware into the memory and run it. I like to do the same but in stand alone mode.I am also aware that M4 can be started and run M4 firmware using SSBL, however we want the M4 firmware to configure clocks instead SSBL. Some could point out why not then use a M4 based microcontroller instead of the MPU, but we have a specific requirement to boot from BootRom to M4 on the MPU.I am thinking about an idea to store M4 firmware as FSBL with the correct headers on one of the Flash devices (NOR/NAND Flash), once FSBL is stated by bootRom, copy M4 firmware and run it.I have not come across such approach, that is why I like to ask if this is going to be even possible?

Hello,One of my previous post the driver for the sensor lsm6dsox hub mode 2 configuration, I have written that the function lsm6dsox_sh_read_data_raw_get was not working correctly. I managed to fix it.Now I see someone fixitNow I'm using lsm6dsr and the same function lsm6dsr_sh_read_data_raw_get needs to add the length.And also this needs to be changed typedef enum { LSM6DSR_EXT_ON_INT2_PIN = 0, LSM6DSR_XL_GY_DRDY = 1,} lsm6dsr_start_config_t;totypedef enum { LSM6DSR_XL_GY_DRDY = 0,LSM6DSR_EXT_ON_INT2_PIN = 1, } lsm6dsr_start_config_t;Please can someone check and confirm.

Hello I have previous implemented the motionfx to get quartenions using lsm6dsl and lsm303agr over i2c, and everything was working great. Now I changed the sensor lsm6dsl with lsm6dsox who is communicating over spi with stm and lsm303agr in mode2(spi-to-i2c). I have configure it the same way as it was working with the old sensor. But now If I leave the board still on the table not moving, the quartenions are changing from -0.9 to 0.9 like there are incrementing. I tried to change the orientation,data_rate,sensitivity, but nothing. I checked the raw data from the sensors and seems ok,values are stable, but still getting weird quartenions. I can confirm that read and write are working for all sensors.

..

I am new to STM32. My problem is that the BLE Sensor App not showing my SensorTile , I have tried to erase the STM32 and load it with the BLE Sensor.bin. PWR button seems not working, tried fit in power, result is same. Appreciate for any type of advices or suggestion.

Hi ST Community,I am using the RTC on the STM32l100RBT6 µC to display the date and time every hour. It is battery powered and therefore at some point i would have to change the batteries, therefore, the µC will lose power. I have thought of using the RTC Backup registers to store the last date and time but according to the datasheet, the backup registers will be reset if there is a loss of power or am i wrong? and also the RTC clock will be stopped anyway.My question is, is there a way to make sure that after power up the RTC is not initialized again because then the displayed date and time will be wrong? and also make sure that the date and time will still be correct after power up?P.S. : the µC has no VBAT pin for connecting the RTC Clock and Backup registers to.

Hello all,I am trying to get started with a STM32DISCO board, like described here:https://www.st.com/en/evaluation-tools/32l476gdiscovery.html#documentationHowever, I can't get it powered.I use the USB USER connector to power it with my laptop.SB settings 13, 15, 16 and 17 are correct.I also can't find demo code for this board.

I'm using SPC_studio programer and debuging my aplication whit PLS UDE StarterKit. It's conected and program all.But i don't is possible debug? I'ts possible debug the SPC58EE84E7 with PLS UDE Starterkit? If is possible, could you sendme example software for conect in SPC58EE84E7 with GTM3?