Solved

Hello,I am working with X-Cube-NFC3 (V2.0.0) for source code. Using one of the projects built for F401RE, I setup a project wherein:I mapped each pin according to various User manualsTo test the pinout mapping, I wrote a simple code to check if User LEDs were mapped correctly. They are. I added the middlewares into the project from the folder inside X-Cube-NFC3 (V2.0.0)I added the BSP drivers for the F401RE into my project. I now used the Ready projects to create some dummy code. I got the code built but all I get is that my board is not initialized. Check out my source code and my output: /* USER CODE BEGIN 2 */ /* Initialize log module */ // __HAL_SPI_CLEAR_OVRFLAG(&hspi1); logUsartInit(&huart2);   platformLog("\r\nWelcome to X-NUCLEO-NFC03A1 (SPI Interface)\r\n");   /* Initalize RFAL */ rfalAnalogConfigInitialize(); if(rfalAnalogConfigIsReady() == 1) { platformLog("rfalAnalogConfigIsReady\r\n"); } else if(rfalAnalogConfigIsReady() == 0) { platformLog

Posted on March 25, 2016 at 01:52I've got a board with a Gyro (L3GD20H) and Accel/Mag (LSM303D).  I'm interfacing with the sensors using I2C.  I can communicate with the Accel/Mag without issues.  However, the Gyro is showing up at (7bit) address 0x68 and it should be 0x6A (since SA0 is low).  I'm able to dump the registers and some of them are correct (WHO_AM_I), however, the data isn't correct.  I've scoped the lines and they look OK, it's just responding at the wrong address.  I've attached the scope readings and the schematic. Has anyone seen this before?  I've probed all the pins and they look correct. Thanks.

Hi Team, I need you support, I am using STM32F429zi, CubeMx Version 5.3.0, STM32Cube_FW_F4_V1.24.1, REERTOS_version  10.0.1 and Platform is atollic truestudio.Issue: Ethernet UP/Down Link status I enable, #define LWIP_NETIF_STATUS_CALLBACK 1#define LWIP_NETIF_LINK_CALLBACK 1observation: Ethernet INT4 is not enable or is not heating.

Hello,I don't understand the description of the Clock Security System in the Ref Manual of STM32H7 (section 7.5.3).First question is : what exactly is the CSS doing ? (what kind of control is done on the clock). What is a definition of "a failure of the HSE" ?Second question: the ref manual mentions both a dedicated interrupt rcc_hsecss_it and the NMI. Why is there both ? Why not only the NMI or only the interrupt ? Thank you

Hi all,Afer copy/paste of project cubemx .ioc file name is not updated accordingly and cannot be opened.Manual updating name of .ioc file is fixing this issue.Regards,Pawel

Hi, I installed STM32CubeIDE for the first time. As the picture illustrated, the keywords, GPIO_PinState and uint32_t, seems like the comment, is there anyway to solve this problem?Best regards.

Posted on July 07, 2018 at 04:41Hi, I'm having trouble reading a register in a slave through I2C communication. Slave: bq25895 http://www.ti.com/lit/ds/symlink/bq25895.pdfIn main:while (1){   HAL_StatusTypeDef status = HAL_OK;    uint16_t return_value = 0;    status = HAL_I2C_Mem_Read(&hi2c1, 0xD4, (uint16_t)(0x07), I2C_MEMADD_SIZE_8BIT, &return_value,1, 1000);    if(status != HAL_OK) { printf ('Error');}    else {printf ('No error');}}Problem: The I2C_FLAG_AF is set since there is no ACK from the slave. Tracing the problem down: /* Send Slave Address and Memory Address */if (I2C_RequestMemoryRead(hi2c, DevAddress, MemAddress, MemAddSize, Timeout, tickstart) != HAL_OK)/* Wait until TXIS flag is set */if (I2C_WaitOnTXISFlagUntilTimeout(hi2c, Timeout, Tickstart) != HAL_OK)/* Check if a NACK is detected */if (I2C_IsAcknowledgeFailed(hi2c, Timeout, Tickstart) != HAL_OK)/* Check if N

I built the rootfs according to the instructions at https://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_Package, but the userspace program of gcnano is not installed in the rootfs, the / vendor directory is empty. I need to manually install gcnano-userland- multi-binary-stm32mp_6.2.4.p4-r0.0_armhf.deb to complete the installation, where is the problem

HiDoes anyone know if the DebugPrinter is still available in current version (see Link)?​. I tried to implement it but it looks like LCD16DebugPrinter isn't available anymore.If it is still available, how can I use it?ThanksMarco

When will ST release the access to buy the new ST25R3916 Discovery Board? And the design files of this board?

ST25R3916 Datasheet DS12484 Rev 1 Typo/Errors:Page 22/123 Table 3. SPI operation modes (continued) FIFO Read Pattern is wrong C5 shall be set to 0Page 79/123 §4.3.46 Antenna tuning control register 1 Type shall be set to RW (and not Read Only)Page 79/123 §4.3.47 Antenna tuning control register 2 Type shall be set to RW (and not Read Only)ST25R3916 Datasheet missing details/chapters about how to use the registers:It will be very good to have some chapter to guide users/developers how to configure the different chipset common mode like:ISO Type A/B/F/V configuration and how to Read UID of Tag A/B/F/VI understand we can find that information indirectly by reading the code of STSW-ST25RFAL002 (RF/NFC abstraction layer (RFAL) for the ST25R3916) but it would be convenient to explain that in the datasheet with some Logic Analyzer/Oscilloscope screenshot (using SPI) ...NFC card emulation modes configuration with example to emulate a Tag UID for Tag Type A/FP2P mode configuration with

Hello Everybody,I am trying to get the USB CDC device only with VBUS sensing to work. Sadly I get allways the device descriptor request error (Error 43) nd the device won't enumerate with my PC host.Most possible solutions or discussion about this problem are more than one year old and do not utelize the new STMCubeIDE which inherits STMCube isnide the IDE and did also modify the USB driver lib.Pleae find below images of my initialization settings:It is the first time that I work with USB together with a STM32 MCU.I would be glad if somebody can help me with this problem.Benjamin

Hi,I want to use matlab simulink to program a ST-Nucleo_F303RE board,with Matlab Simulink 2019b ver.2 with and extensions, ST MAT/TARGET,CubeMX newest version and SW4. (because CubeIDE it does not work)As a first attempt, I followed the MAT / TARGET documentation to implement a simple source code generation. More or less, that worked after several hours/days. Without this forum, I would have no success. Because, as always special error treatment knowledge is needed. I mean very special. For this read other posts, not from me. Now I want to use the external mode, because I need it in the end. I followed the MAT / TARGET documentation again, without success ! Then I looked at an example code, in the example ADC folder, I generate with the CubeMX software my new processor icon file and this example Simulink circuit.Then as I thought so a TransportLayer: ext_comm error !After several hours, I came up with the idea to select the rider times and back again. A success. Again special error tre

I'm porting some fully functional older CMSIS firmware to STMCube and TrueStudio. The old report is 363 bytes which compiles, but Windows Device Manager detects an error in the Report Descriptor. After some tinkering, setting USBD_CUSTOM_HID_REPORT_DESC_SIZE to 361 solved the problem, and the Device Manager error disappeared with the device correctly identified.I suspect its related to the __ALIGN_END macro (== aligned(4)). Values of 362 fail, and 360 gives expected compile errors. Looking at the USB HID mouse/kbd sample app, its Report Descriptor is 74 bytes, and it does not have the problem.Anyone have some ideas why USBD_CUSTOM_HID_REPORT_DESC_SIZE has to be 2 bytes less that the actual size?

CubeIDE 1.0.2 deb linux.IDE see STlink.v2​, I sucessfully upgraded it.When I click on build (checked debug or release) project builds without errors but it dont flash target.​​Only once it flashed my board (disco f407vg) when messing with debug configuration (checked - release), but really dont know how to replicate this.​​I will prowide more info (screenshoots) if needed.

Hi,I'm using the STM32H750 Discoveryboard. When running my code from TouchGFX Designer, everything works fine.But when running with Keil IDE, something strange is happening:-Flashing the application and loading with the debugger -> hard fault occurs in funtion crc_lockIf I unplug and replug the board, the application starts just fine. Only when connected to the debugger, the hard fault occurs.Do you have any hints?__HAL_RCC_CRC_CLK_ENABLE is being called, so that shouldn't be a problemThanks.

..

Refer to AN2606 p. 260 - 263There it says, that for STM32L43xxx derivatives CAN1 bootloader is mapped to PB8 pin (RX) and PB9 pin (TX). My derivative supports CAN but doesn't have these pins, because of a 32 Pin package. Is there a possibility to use the CAN Bootloader anyway?Best Regards!

Hello,I've been using the NUCLEO-L476RG board for development. Now I want to design my own PCB with the same component. My question is about the JTAG port - in the NUCLEO board it is implemented as a USB connector but they used an additional uC for that. I would like to use only the stm32l476RG. I see in its datasheet that it has USB connectivity but I can't find the USB pins in the pinout section. Would appreciate some kind of reference or application notes for USB connector for this coponent, so that I'll be able to connect it to a PC in order to program it, debug and read data over serial.Thank you,David

I want to use SPI implement SWD protocol. Found this one enter link description hereIs there any advice you can provide detail?Have a nice day

Hello Folks, Is there a list of mcus (STM32LXXX) that support the boot modes over USB port? ​

I have written a program in the STM32CubeIDE to receive UART data using DMA. I am using the STM32F030K6T6 processor. I am using the HAL functions, eventually doing a call to HAL_UART_Receive_DMA.In the *.ioc file, USART1_RX is set to use DMA1 Channel 3, Peropheral to memory, and Memory increment is checked.Stepping through the HAL code with the IDE, there is generated code like this in main: /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ADC_Init(); MX_TIM1_Init(); MX_I2C1_Init(); MX_USART1_UART_Init(); MX_DMA_Init();The call to MX_USART1_UART_Init gives rise to the following stack trace:(gdb) bt #0 HAL_DMA_Init (hdma=0x200001a4 <hdma_usart1_rx>) at ../Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_dma.c:140 #1 0x08001340 in HAL_UART_MspInit (uartHandle=0x200001e8 <huart1>) at ../Core/Src/usart.c:96 #2 0x08004a64 in HAL_RS485Ex_Init (huart=0x200001e8 <huart1>, Polarity=0, AssertionTime=0, DeassertionTime=0) at ../Drivers/STM32F0xx_HAL_Driver/Src

Hey.Im using adc dma to transfer data from adc to memory. After each sequence of conversion I need an interrupt.My first question is that is using dma in my case something useless?My second question is that after adc sequence of conversion interrupt flag is set,can I immediately read data from my dma buffer or the data is not transferred to memory yet and i need to get some flag from dma?

Temperature compensation for this magnetometer is not working as I expect. When heating device from room temperature to 50-60 degrees Celsius in 3 minutes magnetometer values are changing a lot. I have 100Hz ODR, high-precision mode, temperature sensor and temperature compensation enabled, offset cancelation disabled. Anyone having an idea what else should I set up? What is the normal (delta C / minute) which sensor can work with while compensating properly? 

Hi all,I am capturing 10 pwm pulses from proximity sensors by making the all pwm pins in rising falling interrupt mode.PWM is captured by a timer at every 100us interrupt.some times pulses are missing, I don't know why this is happening.I am sharing code ISRs:    /* * @name interrupts_Timer_50usCallback * @brief Timer6 period elapsed Callback at every 50us * to capture the time of input pulses. * (50us will also be treated as resolution of input pulse capturing). * @param none * @retvalue none */ void interrupts_Timer_100usCallback(void){ //==== For Pulse Input1 ==== if(pulseCaptureFlags.pulse1Present != 0){ if(++pulse1_1ms_cntr > 17){ pulse1_1ms_cntr = 0; if(pulseCaptureFlags.pulse1TimerSet == 0){ if(++pulse1_Capture_Thrshld > inputCaptureTime[0]){ pulse1_Capture_Thrshld = 2; pulseCaptureFlags.pulse1TimerSet = 1; pulseInput_1.counter++; pulseInput_1.timer = pulseInput_1.timer + inputCaptureTime[0]; }   } e