Solved

I am using the X-CUBE-CRYPTOLIB (V4.2.0) in a project for STM32F207.I am successfully able to generate ECC key pair using cmox_ecdsa_keyGen() and generate ECDSA signature using cmox_ecdsa_sign() but I am now needing to generate a shared secret using cmox_ecdh() function. The problem I have is that the cmox_ecdh() function expects the public key in raw data format (64 bytes) but I only have the public key available in compressed format (33 bytes) where 32 bytes is the x component and the other byte indicates if the y component is odd or even. The y component can be derived from this information but I could not find a function within the  X-CUBE-CRYPTOLIB that does this which means I am unable to generate the shared secret.Is there a way of achieving this with the  X-CUBE-CRYPTOLIB?

i am new to makefile Enviromint please refer the screenshot  regards,raj

Using STM32CubeIDE v1.6.1 on MacOS 11.3.1Steps to reproduce:Create a new STM32 project.Board Selector -> Select STM32F411E-DiscoName project, leave everything else as default, hit finish.Initialize all peripherals with their default Mode? YesDebug as STM32-M C/C++ Application.Hit play then pause and you'll end up in the Error_Handler.Stepping through the program it errors out waiting for the HSE to be ready.Troubleshooting:I made sure I wasn't insane and choosing the wrong board. I am staring at the board name on the back of the PCB as I write this. I am able to use the board and interact with the LEDs and button when using the internal clock.Tried to increase HSE Startup Timeout to 10 seconds, still times out.I checked the solder bridges, SB14, SB16, R66 are off and I made sure with a multimeter.I want to use the USB OTG but can't do so without the external clock but I haven't tried to use an entirely separate clock circuit yet. What bothers me the most is that I'm using entirely d

Hello,For the vd55g0, you provide a kernel driver and device tree as source here: https://www.st.com/en/embedded-software/stsw-img505.htmlYou also provide a libcamera integration stack (STSW-IMG505_LCAM), but this is closed source, and only the libcamera-base.so and libcamera.so files are provided via the .deb package. This makes it such that we cannot work with the libcamera source or custom applications, unless we use your pre-compiled libcamera libraries.Could we please get source code for the changes, per LGPL 2.1, which libcamera uses? Or, for now, if this takes some time for you to do, please just the camera helper file would be massively helpful. This is likely called "camera_helper_vd55g0.cpp" inside of "src/ipa/rpi/cam_helper/". Of course we can write our own but we chose this path for ease of integration and speed.This would greatly assist us in integrating your sensor to our product.Thank you! We would greatly appreciate it.

Hello,Since the latest release of CubeMX (6.12.1) installed, I have been encountering syntax errors related to the "FLASH.ld" file.This issue only arises when I generate code while setting the Toolchain/IDE to CMake. I am using STM32F103C8T6.It seems that CubeMX does not specify which RAM to use when setting the Toolchain/IDE to CMake.I have also included the FLASH.ld file that was generated for your reference. The terminal output the wrong as below , after  run  the default cmake-build task with the project templete generated by CubeMX (6.12.1)  :STM32F103C8Tx_FLASH.ld:56: syntax errorcollect2.exe: error: ld returned 1 exit statusninja: build stopped: subcommand failed.build finished with error(s).Then, after replacing 6.12.1 flash.ld  with 6.12.0 flash.ld  , the errors are eliminated.Here are two versions of the flash.ld  attached. ---Thanks for your help.

Hello everybody,I am developing a custom board strongly inspired by the STM32MP157D-DK1, except that I use a parallel DPI RGB on 24bit display.I use openstlinux-6.1-yocto-mickledore-mpu-v24.06.26.The frequency of "LTDC_CLK" changes by itself after waking up from "deep suspend".Before putting it into "deep suspend", I measure 31.65Mhz which corresponds well to what is expected for "innolux,at070tn92"But after waking up, i measure 86.21Mhz and this is completely outside the display specifications.All other frequencies changed in the same proportion "HSYNC", "VSYNC", ...Here is the configuration in the kernel and u-boot DTS file : panel_at070tn92: panel_at070tn92@0 { compatible = "innolux,at070tn92"; enable-gpios = <&gpioi 10 GPIO_ACTIVE_HIGH>; power-supply = <&vdd>; status = "okay"; port@0 { reg = <0>; panel_in: endpoint { remote-endpoint = <&ltdc_ep0_out>; }; }; }; &ltdc{ pinctrl-names = "default

GoodmorningI have a new STM32L496ZGT6PU board and I'm currently trying to print a message on the debugger serial terminal, I've followed many official guides step by step failing every time.In particular, I perform the following:Connect the board through a USB type micro-B cable to my laptop (USB PWR connector).Create a new STM32 project, selecting the NUCLEO-L496ZG-P board from the board selector -> target language C++ -> initialize the peripherals with their default mode (YES).In Pinout & Configuration I go to Connectivity -> USART2 -> Mode Asynchronous and leave the default values.Device Configuration Tool Code GenerationIn Src/main.c simply write the following two lines of code in the main() function: /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */ /* USER CODE BEGIN 3 */ HAL_UART_Transmit(&huart2, (uint8_t*)"Ciao ", 6, 100); HAL_Delay(1000); } /* USER CODE END 3 */ Then I build the project and sta

Hello,my injected Adc sequence was not being triggered, and I found that the cause is that, with LL driver, the trigger source is not being set by the CubeMX code generation.I had to add this line in the main code:LL_ADC_INJ_SetTriggerSource(ADC1,LL_ADC_INJ_TRIG_EXT_TIM1_CH4); I am testing on a Nucleo L432KC P.S. I have fitted SB17 to have the 8MHz clock in from the STLInk. Otherwise, to use a default solder bridge configuration, the clock source in the IOC file needs to change.

hello, I am developing an application which makes use of LIN break interrupts. At the moment I am using two STM32 dev boards:STM32C0116-DK ( which uses STM32C011F6U6)STM32 NUCLEO G531 (which has STM32G431KBT)We are using the LL drivers interface.Although one processor is Cortex-M0+ and the other is M4, the description of the USART operation seems the same for each processor, as does the low level interface.However, we are seeing very odd behaviour on the C11 (Cortex M0+) platform - we get the LBD interrupt, but it happens a considerable time after the break.. On the M4 platform we see the interrupt a few us after the break is done.UART config and ISR implementation is the same on each platform. (Most of it is generated by Cube.) Here is the code for UART initialisation:  static void MX_USART1_UART_Init(void) { /* USER CODE BEGIN USART1_Init 0 */ /* USER CODE END USART1_Init 0 */ LL_USART_InitTypeDef USART_InitStruct = {0}; LL_GPIO_InitTypeDef GPIO_InitStruct = {0};

Hi all, I am trying to benchmark a TCN (causal cnn)-model on an STM32u5, however, when using any of the AI-Tools (online, CubeIDE or CLI), the analysis step fails with the output:  ST Edge AI Core v1.0.0-19894 INTERNAL ERROR: 'numpy.ndarray' object has no attribute 'get_shape_map'  Which is sadly not helpful. The model is attached, it was converted to onnx from pytorch (or rather fastai) using opset 13. It should take an input of 1x500x1 (bs x 1DSample x channels) and give an output of the same shape.I would be happy to get any pointers on what I can do to fix this, thank you!

I haven't been able to wait 500ms without affecting the timers for 7 days.In this block, doesn't PB14 become "0" after 500ms?Even if I use comment lines, it doesn't work.Note: volatile uint32_t Counter = 0;The "Counter" variable is incremented every 1ms with Timer16. ** STM32F030C6T6 I'm using.** Own PCB board..*** Note: Card of a working system.. There is no card design error.  if(htim->Instance==TIM16) { Counter++; if(HAL_GPIO_ReadPin(GPIOC, GPIO_PIN_13)==0) { if(HAL_GPIO_ReadPin(GPIOA, GPIO_PIN_2)==0) { if(PA10_On==0) { HAL_GPIO_WritePin(GPIOB, GPIO_PIN_12,GPIO_PIN_RESET); HAL_GPIO_WritePin(GPIOB, GPIO_PIN_14,GPIO_PIN_SET); Counter=0; PA10_On=1; // Tick_PA10_On= HAL_GetTick(); // PA10_On=1; } else { if(Counter>500) // if((HAL_GetTick()-Tick_PA10_On)>=500) { HAL_GPIO_WritePin(GPIOB, GPIO_PIN_14,GPIO_PIN_RESET); Counter=501; } } } else {

I have ported rfal platform to work on my esp32 and have successfully detected all kinds of cards. Now I want to send select APDU message to the phone but I am unsucessful at doing so.The code I have used: err = rfal_nfc.rfalIsoDepPollAHandleActivation(RFAL_ISODEP_FSXI_512, RFAL_ISODEP_NO_DID, RFAL_BR_424, &isoDepDev); Serial.print("handle activation: "); Serial.println(err); err = rfal_nfc.rfalIsoDepStartApduTransceive(param); Serial.print("APDU txrx error: "); Serial.println(err); if (err == ERR_NONE) { do { rfal_nfc.rfalNfcWorker(); err = rfal_nfc.rfalIsoDepGetApduTransceiveStatus(); Serial.print("."); // delay(200); Serial.print(err); } while (err == ERR_BUSY); Serial.println("Received!"); Serial.println(rxLen); } The param I've used is: rfalIsoDepApduTxRxParam param; rfalIsoDepApduBufFormat txapdu; rfalIsoDepApduBufFormat rxapdu; rfalIsoDepApduBufFormat temp; uint16_t rxLen; txapdu.apdu[0] = SELECT_APDU[0]; txapdu.apdu[1] = SELECT_APDU[1]; txapdu.apd

Hi !I got some samples of G473CBTx from ST through one of the official distributor, which were populated on prototype boards. I am trying to flash them, but unfortunately stumbled upon the "no STM32 Target found" error. I tried the following. 1. Use a different ST-Link programmer / Nucleo board from F3/G0 family2. Double check the pinout with CubeMX file (I use CubeMX to generate the initial pinout assignment for ease of layout designing).3. Check the voltage levels across the µC pins (VDD, VSS, SWDIO and SWCLK).4. Use the NRST functionality along with ST-Link along with SWDIO and SWCLK.5. Update the ST-Link driver of the Nucleo board / ST-Link programmer.6. Try the new ST-Link software (STSW-LINK009) My attempts are unsuccessful until now. It must be noted that the G431CBTx were already populated on similar prototype boards and are working properly as expected. I tried to flash the G431 with the same setup and could flash it successfully. But not with the G473x.It will

 Hello,I have a large .onnx model which, untouched, I am unable to run on my STM32 board. To tackle this problem, I wanted to quantize the model in order to decrease its size. I followed the official STM wiki (https://wiki.st.com/stm32mcu/wiki/AI:X-CUBE-AI_support_of_ONNX_and_TensorFlow_quantized_models). First, I preprocess the model using onnxruntime as described in the wiki, and then I change the opset version of the preprocessed model to 13. Finally, using almost identical code to the wiki, I apply static quantization to the model, drastically reducing its size. (As in the wiki, I also tried quantizing with and without the per_channel=true option, but both attempts failed.)When trying to analyze this model using X-CUBE-AI, I get the following error:ST Edge AI Core v1.0.0-19894TOOL ERROR: list index out of rangeHow can I fix this? The strange part is that the original, larger model can be analyzed successfully, so the quantization process must have introduced a change that made

hello what is the diffrence between stm32f29i-disc1 and stm32f429zi

Original post: https://community.st.com/t5/stm32cubemx-mcus/problems-with-data-reception-via-usart2-on-stm32f429zi/td-p/741765 Even setting USART3 it doesn't work (see attachments). Did I make a mistake setting some parameters, or is something missing? Thanks a lot

Hello,It seems that the example BLE_p2pServer_ota works with an operating system? I want to forward certain payload data to a UART2 interface via DMA after a connection has been established.Where is the right place to insert a HAL_UART_Tx_DMA transmission function in the code?In the example provided, the function to check the payload is queried in the p2p_server_app.c file in line 122: if(p_Notification->DataTransfered.p_Payload[1] == 0x01) { BSP_LED_On(LED_BLUE); LOG_INFO_APP("-- P2P APPLICATION SERVER : LED1 ON\n"); P2P_SERVER_APP_Context.LedControl.Led1 = 0x01; /* LED1 ON */ // Here, i want to include the HAL_USART_Tx function ... } if(p_Notification->DataTransfered.p_Payload[1] == 0x00) { BSP_LED_Off(LED_BLUE); LOG_INFO_APP("-- P2P APPLICATION SERVER : LED1 OFF\n"); P2P_SERVER_APP_Context.LedControl.Led1 = 0x00; /* LED1 OFF */ } For example, here i want to transfer the string "LED ON" to USART2.Is this the right place to insert the code?

Hallo together,i`m working with the STM32H573I-DK EvalBoard to check if the Chip fits our project needs.I was working with the template STiROT_Appli from the STM32Cube_FW_H5_V1.3.0 Firmware. Full path to the template: STM32Cube_FW_H5_V1.3.0\Projects\STM32H573I-DK\Templates\ROT\ STiROT_Appli.I followed the steps within the readme.md, entered the provisioning state (0x17) and provided the OBK delivered with the firmware. (As I have done in the previous tutorials security tutorials)Full path to OBK: STM32Cube_FW_H5_V1.3.0\Projects\STM32H573I-DK\ROT_Provisioning\DA\Binary\ DA_ConfigWithPassword.obkThen i continued the development and now i wanted to restore the product_state back to OPEN using the regression process. Now the Board is in CLOSED State.However, since this template used TrustZone, regression is not working with the password.bin, but with certificates. Is there a way to recover this EvalBoard?As I understand it, I would need a Certificate matching the DA_ConfigWithPas

How to solve this error 'error loading software packs run-time environment might work incorrectiy see build output for details' when using STM32H745?Thank you!

Hello everyone,Thank you for clicking this post. I am new to the community and ecosystem. Here's my task, I am trying to use the X-CUBE-SBSFU libraries to perform a secure firmware update procedure. I am using the STM32L496ZG-NUCLEO-144 board to test before applying it to our hardware.There exists the 32L496G discovery project in the XCUBE-SBSFU example projects. I was able to flash the NUCELO board with this and use the project over UART and an FTDI to usb serial adaptor. Great.Now I want to rewrite the communication layer in the SBSFU example to use the USB_OTG_FS virtual com port using the USB CDC libraries instead of UART.I have an example project build with the ".ioc" graphical tool where I can successfully print hello world over the virtual com port. I noticed some Middlewares/ST/STM32_USB_Device_Library and USB_DEVICE folders in the hello world project so I copied them into the SBSFU application folder.I also selected project->properties->MCU GCC Compiler and added the fol

Hi allI am trying to debug an issue at work where we use the LSM6DSV accel/gyro IMU chip and I am running into a little problemThe result registers for the accelerometer and gyroscope both say that they return a 16-bit two's complement result, and I get the followingGyro / AccelRaw unsigned value(LOW | (HIGH << 8))Two's complement value (Signed)Result (mG or mDPS)Accelerometer X65524-12-0.732Accelerometer Y1334713347814.167Accelerometer Z1111116.771Gyroscope X32772-32764-143342.5Gyroscope Y3276432764143342.5Gyroscope Z37149-28387-124193.125My system is sitting very still and on a somewhat level surface. The accelerometer seems correct. For a value close to 0, we see the unsigned value close to 0 or very high around 65535 which is what I would expect.The gyroscope values for a zero rate I would expect to also be similar given the datasheet says this "The value is expressed as a 16-bit word in two’s complement"My basic thinking is that these are expressed as a 15-bit word in two's

my daily job is C# programming, so after a break on stm32, I started again with platformIO and CubeMx ( and thought how hard can it be to turn a led on and off ? )   the problem i have with the STM32F0 discovery ( the green one ) the EXTI IRQ event is not triggered.   i found this example. https://www.youtube.com/watch?v=xawN4Y7uSJ4 this is my platformIO.ini [platformio] default_envs = disco_f051r8 [env:disco_f051r8] platform = ststm32 board = disco_f051r8 framework = stm32cube board_build.mcu = stm32f051r8t6 upload_protocol = stlink build_flags = -I./Inc board_build.f_cpu = 48000000L   after adding the include path ( Inc ) it worked.   connecting the board, building debugging step by step. etc etc.  turn a led on and off ,  push   a button reading the value 1 or 0  ( so i know the button is working ) got it quickly working.   the the next step is EXTI interrupt. ( made it with CubeMX32 ) very easy to choose the pins and set up ever

Hello,I want to use LSM6DSM, so I got the dev-kit and tested it out.Now I decided to use this sensor and was looking for the symbols in Altium, but it is NRND, so I double checked in ST Micro web site if it was NRND, but it is still Active.As I am going to use this sensor now, I would like to make sure of guaranteed longevity. I couldn't find this in the longevity page.   

Hi!When I use this device tree nodes, or very similar. I get this error code:As you can see, I'm getting this kind of errors. I don't know if the Device Tree or the IC chip is faulty. I would like to know if there are any ways to find out if the IC chip is the cause of the problem or if there is any way for me to find out if the USB2514B is faulty. Can you give me any suggestions?I have checked the hardware configuration and it seems to be in order. I have checked the voltage levels. It seems very OK as well. All VDD are 3.3VAlla REM[0:1] is 0VVBUS_DET is 3.3VRBIAS is about 1.2V because there is a 12 kOhm pull-down resistor thereAll PRTPWR[0:3] are 0VAll SEL[0:1] are 0VTEST is connected to GNDAll OSC_N[0:3] are closed with their pull-up on about 2.5VRESET_N is 3.3VPLLFILT is connected to a capacitor to GNDXTALIN is 0.63VXTALOUT is 0.64VUSBDM_UP is 0VUSBDP_UP is 3VOnce RESET_N goes low, the error codes in Linux terminal will re-write the error codes again. So I guess that the RESET

Hello!I am working on integrating ST25R3916B into our product based on PSOC 6 CM4.  I can read the ID and initialization seems to succeed but I cannot detect any tags.Setup:* I am using STEVAL-ST25R3916B reader expansion board with ST25R3916B.* I have VBUS connected 5V, 3.3v to 3v3. SPI pins are properly connected and can read the ID. IRQ as +ve edge.* I have attached spi transaction logs, I have the SPI bus connected to the logic analyzer in case if need any transaction through the logic analyzer.* I have attached rfal_platform.h and have ST25R_COM_SINGLETXRX enabled and spi_transfer handles the SS pin.Please let me know anything to try, not sure where to start.