Solved

From what I gather, sunlight causes the sensor to return a much larger value. Should this always be the case? Or is sunlight going to cause a variety of different values. I have mixed results in testing.

I use MX25LM51245GMI00 flash. But I dont have few pins so I use 4 pins for OCTO SPI. Does it work 4 pins OCTOSPI? What do I it for 4 pins OCTOSPI. What changes do I need to make

We are prototyping a ST95HF NFC in combination with an embedded Linux board.Since we can only find Linux demo code for the ST3916 on your website wetried to combine the ST25r95 rfa library found in STSW-ST25RFAL003_v2.6.0with the Linux demo code found in STSW-ST25R013 - Linux demo of ST25R3916 for Raspberry Pi using X-NUCLEO-NFC06A1 which has demo code based on RFAL 2.2.0Our efforts so far to combine the code is able to to discover the technology of the card presentedbut after this we end up with communication failures to/from the ST25r95 chip.Is there code available of the Linux demo project for the ST25r95 forversion v2.6.0?We successfully used the poller based version of Linux_RFAL_st25r95_v2.0.4 to read NFC cards, but this is version is too CPU intensive and version 2.6.0 seems to be a much improved version.

hi I have the ihm08m1 how can I change from 1 shunt to 3 shunt if by default it is soldered on 1 shunt?

Currently I am trying to set up the emmc boot on a stm32mp157. I have mirrored the partitions of a working SD card to the emmc with:sgdisk -e /dev/mmcblk1 sgdisk -R=/dev/mmcblk2 /dev/mmcblk1 sgdisk -G /dev/mmcblk2   dd if=/dev/mmcblk1p1 of=/dev/mmcblk2p1 bs=512 conv=fdatasync dd if=/dev/mmcblk1p2 of=/dev/mmcblk2p2 bs=512 conv=fdatasync dd if=/dev/mmcblk1p3 of=/dev/mmcblk2p3 bs=512 conv=fdatasync dd if=/dev/mmcblk1p4 of=/dev/mmcblk2p4 bs=512 conv=fdatasync dd if=/dev/mmcblk1p5 of=/dev/mmcblk2p5 bs=512 conv=fdatasync dd if=/dev/mmcblk1p6 of=/dev/mmcblk2p6 bs=512 conv=fdatasync   echo 0 > /sys/block/mmcblk2boot0/force_ro dd if=/dev/mmcblk1p1 of=/dev/mmcblk2boot0 bs=512 conv=fdatasync echo 1 > /sys/block/mmcblk2boot0/force_ro   echo 0 > /sys/block/mmcblk2boot1/force_ro dd if=/dev/mmcblk1p2 of=/dev/mmcblk2boot1 bs=512 conv=fdatasync echo 1 > /sys/block/mmcblk2boot1/force_ropartition is fsbl1, fsbl2, ssbl, boot, rootfs1, rootfs2.Then i used the OTP boot device conf

I have recently started with STM32G0. I want to configure and use FDCAN. So, if there are any implemented examples and or some programming manual on this; please share.Thank you.RegardsJayam Srivastava.

GreetingsI'm using an STM8S003F3 TSSOP20 (my first STMicro) for a simple project with one input (low frequency PWM) and one output (high frequency PWM). I seek to keep it as simple as possible. Since I'm not familiar with STMicro MCU's, I would like to confirm the wiring of this:100nF between NRST and VSS1uF between VCAP and VSS1uF and 100nF in parallell between VDD and VSS+5V to VDD0V to VSSVDD, VSS, NRST and SWIM connected to ICSP plug.PWM input on PD2PWM output on PD3All other pins connected together, with one configured as output, driven to 0VThanks in advance for any helpful advice!

Hello,I am trying to find an example or application note that describes how to do OOB pairing using an NFC tag and the STM32WBx series. Has anyone out there successfully done this before, or can you point me to some good information for doing this?Thank you for any help.

..

Why doesn't firmware upgrade to ST-LINK not stick?Cube Programmer says it upgrades it successful but it doesn't do it

..

We are using the STM32H753 and cannot enter the bootloader using pattern 8.AN2606 states that when BOOT0 is low and the option byte BOOT_ADD0 is 0x0040, then the bootloader is activated.Does this work for the STM32H753?Pattern 8Option byte set to 0x0040 in STM32CubeProgrammer Thanks for your help!

Hello, I have three GPIOs output configured. I'm having some strangeness on two of these that I don't quite understand.I'm using a nucleo STM32L432KC, and I have some custom circuitry attached to the GPIOs (detailed below)The situation I am experiencing is as follow.When I set the 3 GPIOs like so, I have expected results.HAL_GPIO_WritePin(GPIOB, GPIO_PIN_7, GPIO_PIN_RESET); HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_RESET); HAL_GPIO_WritePin(GPIOA, GPIO_PIN_6, GPIO_PIN_SET);PB7,PA5 are low and PA6 is high.The next condition I test:HAL_GPIO_WritePin(GPIOB, GPIO_PIN_7, GPIO_PIN_RESET); HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_SET); HAL_GPIO_WritePin(GPIOA, GPIO_PIN_6, GPIO_PIN_RESET);Should show PB7 low, PA5 high ad PA low.But instead I see this:PA5 appears to be bouncing all over the place, and once in a awhile PB7 does as well.(This is short sample, of like 5 seconds)Finally, when I do this:HAL_GPIO_WritePin(GPIOB, GPIO_PIN_7, GPIO_PIN_SET); HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5

NUCLEO-H723ZG dev. kit.I need take over the full control of the USARTx. I need a TX interrupt and the RX interrupt handled manually independently the HAL_UART_*** functions. The HAL_UART_Receive_IT() and the HAL_UART_Transmit_IT() is useless for me. During initialization I need to enable the receiver. When one byte is received then I need an interrupt and I will store the received bytes in the RXBuffer. The main() loop periodically checks the received bytes. If it finds a complete message in the RXBuffer[] then it processes the message, then creates the answer into the TXBuffer[], enables the TX interrupt and sends back answer.To do this I need a TX interrupt when the TX buffer becomes empty. I simply send the next byte. When I get the TX buffer empty interrupt and I have no more bytes to send I disable the TX interrupt, clear the RXBuffer and re-enable the RX interrupt. I am sure it is possible to do with STM32H723ZG MCU but I could not find such an example. How can I do this? Th

I am trying to read temperature from SL900A tag. As base I am using in SDK provided. demo_gen2GenericCommand . Although tag is accessible and I am able to read the memory when I try to read the temperature from TAG I always get the failure response.Data sheet of the Tag is available here: https://ams.com/documents/20143/36005/SL900A_DS000294_5-00.pdf/d399f354-b0b6-146f-6e98-b124826bd737I changed the function demo_gen2GenericCommand and am sending following command:....    genericCmd.cmd = cmd;    genericCmd.noResponseTime = 0xFF;    genericCmd.appendRN16 = true;    genericCmd.sndDataBitLength = 24;    // 24: length of effective cmd data, headerbit + rn16 (if any) are computed by FW    genericCmd.sndData[0] = 0xE0;    genericCmd.sndData[1] = 0xAD;    genericCmd.sndData[2] = 0x00;    genericCmd.sndData[3]

Hi everyone,I am using stm32mp157f-dk2 with openSTLinux-5.4-dunfell-eglf distribution.​I would like to configure my device tree using cubeMX.​The generated dts file seems OK to me. However, how can I tell yocto to use my newly generated device tree?​The instruction on https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machinedidn't mention anything about this.​I have tried to modify the meta-st-stm32mp-addons/classes/cubemx-stm32mp.bbclass but it doesn't work.​It seems to me that the default meta-st-stm32mp-addons/conf/machine/stm32mp1-mx.conf is not used.​Regards, Leung​

I've just watched a few tutorials on ADC, and I've enabled IN1 on ADC1 which seems to map to the connector labeled A3 as per this doc.I then added the following to my main.c within the CM4 project.uint32_t raw = 0; char msg[100]; HAL_ADC_Start(&hadc1); HAL_ADC_PollForConversion(&hadc1, HAL_MAX_DELAY); raw = HAL_ADC_GetValue(&hadc1); HAL_Delay(100); sprintf(msg, "%d\r\n", raw); VIRT_UART_Transmit(&huart0, msg, strlen(msg));Then I plugged pin A3 directly into GND so I could validate it's working by getting a reading of 0, but I get either 32768, 65518, or 0. I've also tried to supply it 1v and it seems to give 65518 constantly. I've also tried to switch to hdac2 by creating the same configurations in the IOC and I had the same results. It seems like it may be reading multiple different values from the different ports and displaying them all as they come in, but I don't even have anything defined in the other INs.Furthermore, if I did define multiple INs for one ADC (which

HelloI have encountered a strange problem at work using stm32f439zi processors.Some context:We're using two board:development board NUCLEO-F439ZI, with a processor stm32f439ZITx in revision 4custom board, with a processor stm32f439ZIYx in revision 3The difference between the two processor are only the package and the revision.We have a program developed in the stm32Cube that works well and is debuggable on both board.We have an other program developed using mbedOS that works well on the development board but fails to launch on the custom board.We starting a debug session, the mbed program crash and gives a segmentation fault.Debug console of the crash:```Selected port 50000 for debugging0001458:INFO:board:Target type is stm32f439xi0001477:INFO:coresight_target:Asserting reset prior to connect0001488:INFO:dap:DP IDR = 0x2ba01477 (v1 rev2)0001515:INFO:ap:AHB-AP#0 IDR = 0x24770011 (AHB-AP var1 rev2)0001601:INFO:rom_table:AHB-AP#0 Class 0x1 ROM table #0 @ 0xe00ff000 (designer=020 part=411)

As exposed in the Application Note AN5231 of the VL53L1CX, a gasket may be required to limit the negative crosstalk effect if a cover window and a large air gap were both present. Is there any similar Application Note specific for the VL53L5CX model?For example, the following specifications can be considered:VL53L5CX with window coverPCB and window are parallel to each otherPCB to cover window distance = 3mmwindow thickness = 0.5mmranging distance from 20mm to 1000mmCould a gasket be required in these conditions?Thank you

..

When I try to connect to a STM32MP157F-DK2 board via SWD/JTAG, STM32CubeProgrammer aborts with a segmentation fault on my host system (openSUSE Leap 15.2).I get the following error message, when I start STM32CubeProgrammer within a shell:# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fee0c8259fe, pid=14499, tid=0x00007fee00ee6700 # # JRE version: OpenJDK Runtime Environment (8.0_265-b01) (build 1.8.0_265-b01) # Java VM: OpenJDK 64-Bit Server VM (25.265-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libCubeProgrammer_API.so+0x5b9fe] connectStLink+0x2ee # # Core dump written. Default location: /usr/local/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/core or core.14499 # # An error report file with more information is saved as: # /usr/local/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/hs_err_pid14499.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugrepor

..

I am trying to use the output compare mode of TIMER1 to produce an accurate time course on the PE9 pin. For some reason I don't get an output signal on this pin. Instead, when I use TIMER3 with the same settings as TIMER1, I get an output signal on pin PC7.What is the reason for this? What can I change to also get the output signal from TIMER1?/** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * <h2><center>© Copyright (c) 2022 STMicroelectronics. * All rights reserved.</center></h2> * * This software component is licensed by ST under BSD 3-Clause license, * the "License"; You may not use this file except in compliance with the * License. You may obtain a copy of the License at: * opensource.org/licenses/BSD-3-Clause * ***************************************************

Hi everyone,I have a project for a dual core microcontroller (STM32H755) in CubeIDE structured as follows. I'm trying to export and import it to another CubeIDE via the import/export functions but I can never get it to import correctly.Does anyone have experience with this or know if there is a procedure that explains how to do it?Thank you 

I have been programming with the STM32F411CE and I have now had this happen multiple times to different boards. Basically I program the board a few times and then all the sudden it will no longer connect. I get the following message from cubeIDE, STMicroelectronics ST-LINK GDB server. Version 5.9.1 Copyright (c) 2021, STMicroelectronics. All rights reserved.   Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled   Waiting for debugger connection... Debugger connected ------------------------------------------------------------------- STM32CubeProgrammer v2.8.0 -------------------------------------------------------------------   ST-LINK SN : 2105041B2315303030303032 ST-LINK FW : V2J39S7 Board : -- Voltage : 3.16V SWD freq : 4000 KHz Connect mode: Under Reset Reset mode : Hardware reset Device ID : 0x431 Revis