Solved

I'm struggling to get the SPI CRCERR flag and IRQ to work the way I expect.I am using an STM32WB55. The SPI communication in full duplex is working. The master is adding the CRC to the end of the Tx data. On the slave side, the CRC is read in. I can see the RXCRC updating, and I can see it go to 0x00 when the final CRC byte is read, which tells me that the CRC calculation is working. However, I cannot get the CRCERR flag to turn on when I purposefully have a CRC mismatch (using different polynomials on master and slave to trigger a mismatch).I suspect the issue is related to the DMA transfer sizes. I have read the advice about what length of transfer to use (Tx side = data length without CRC; Rx side = data length with CRC), and I have tried various combinations. I suspect that slave SPI does not know the transfer is done, so it does not do the final comparison and set the error bit.So, some actual questions:Should I expect the CRCERR flag to work with SPI + DMA on processors like the

Hi,I created a project for the Tiny Shark using TouchGFX 1.17 and found it generated code for the NOR Ram OCTOSPI interface that was incorrect such that a Hard Fault was generated.I built another project using Ver. 1.18 and had the same problem.Luckily i put a tag next to the modded line so I found it in the earlier project and put it into the new one.The relevant code is:/** * @brief OCTOSPI1 Initialization Function * @param None * @retval None */ static void MX_OCTOSPI1_Init(void) { uint32_t statusResult;   /* OCTOSPI1 parameter configuration*/ hospi1.Instance = OCTOSPI1; hospi1.Init.FifoThreshold = 1; hospi1.Init.DualQuad = HAL_OSPI_DUALQUAD_DISABLE; hospi1.Init.MemoryType = HAL_OSPI_MEMTYPE_MICRON; hospi1.Init.DeviceSize = 26; hospi1.Init.ChipSelectHighTime = 2; hospi1.Init.FreeRunningClock = HAL_OSPI_FREERUNCLK_DISABLE; hospi1.Init.ClockMode = HAL_OSPI_CLOCK_MODE_0; hospi1.Init.WrapSize = HAL_OSPI_WRAP_NOT_SUPPORTED; hospi1.Init.ClockPrescaler = 3; hospi1.Init

But What It's mean exactely ? I must buy a Debugger like ST-LINK/V2 ? Thank you for your helps. Regards

I'm working with the STM32L4 Nucleo-64 Development Board and compiling with STM32CubeIDE 1.6.1. I have created a project using STM32CubeMX that I then imported into STM32CubeIDE. Hence, my linker script file was generated by STM32CubeIDE. Whenever I compile, my resulting (hex or binary) firmware file contains 96 bytes starting at address 0x20000000. Where do those bytes come from and what's the purpose of them?

..

Like I said, I can not find the spice model for the STD134NF7AG MOSFET.

STM32WB55RGV6 connects ADS1299 by spi. And I choose spi2. There are three signas miso\ mosi and sck. SPI2 has two alternative: GPIO_AF3_SP2 and GPIO_AF5_SPI2.① STM32CUBEMX automatically generated miso(GPIO_AF3_SP2), mosi and sck(GPIO_AF5_SPI2).Initialization is ok, but no data.② All ​GPIO_AF3_SP2. Initialization is failed and application crash.③​ All ​GPIO_AF5_SP2. Successfully.Although the result is good, I do not understand why:sad_but_relieved_face:

Hello,Can you help me to use the DMAMUX in the STM32G474 microcontroller?How can I program the uC to make TIM2_CH1 sends a DMA request when CC. I have found this in the reference manual but I can't undesrtand which channel of the DMA is involved. Thanks for the clarification

The STM32CubeMX generate:```#define LCD_SPI_Send_DMA(rd, ln)           BSP_ERROR_FEATURE_NOT_SUPPORTED```instead if I modify the generated DISPLAY/Target/lcd_conf.h with`#define LCD_SPI_Send_DMA BSP_SPI1_Send_DMA`seems work correctly.I am using:Nucleo WB55RGGFX01M1STM32CubeIDE 1.9X Cube Display 2.1.0 (in the package 2.0.0 was correctly defined)Is this only a STM32CubeMX bug or I can't use SPI + DMA+ Display?Thanks for the support

In order to achieve minimum power drain on the B-L072Z-LRWAN1 discovery board, it is necessary to remove some solder bridgesSee: https://community.st.com/s/question/0D50X00009XkbSOSAZ/excess-current-consumption-running-bl072zlrwan1-from-batteryAnd:https://community.st.com/s/question/0D50X00009q4M1zSAE/cant-power-bl072zlrwan1-with-batteryTo be able to use the onboard ST-Link again, these connections need to be restored:NRST: link CN4.3 to CN12.5;SWD: fit two links on CN8;VCOM: link CN5.1,2 to JP6. Rather than have to mess about with 2 separate links for the SWD, a single-row 4-pin header can be adapted:

We recently received our B-L072Z-LRWAN1 but are not able to run the program while batteries are plugged in. In the datasheet it says that we need to remove SB37 to accomplish this. But then I cant program it anymore? How can I use the board with battery only and still be able to program it?

Posted on December 11, 2017 at 20:21   I have removed all the solder bridges & links to minimise stray consumption. When I measure the combined current through JP3 and JP1 (ie, MCU & RF), it is ~0.87mA between Tx pulses.  (SB19,14,17 are removed; JP2 is not fitted - so no current to USB_LRA) But, when I power the board from the battery, and measure the battery current, I see 1.95mA  (SB18 is removed) The ST LD39050 regulator (U7) is supposed to be ''low quiescent current'': the datasheet says it should only, typically, be taking 100uA at 500mA load - so we should be nowhere near that! So where is this extra milliamp going?? EDIT To clarify: the ~0.87mA to MCU & RF is measured while powered from the battery. #current-consumption #b-l072z-lrwan1 #low-power #current Note: this post was migrated and contained many threaded conversations, some content may be missing.

Hi,I am using an official STM32MP157C-DK2 board.I tested to build OP-TEE 3.17.0 for stm32mp1 however the boot hangs.I am building OP-TEE OS using:make PLATFORM=stm32mp1 \ CROSS_COMPILE_core=arm-linux-gnueabihf- \ CROSS_COMPILE_ta_arm64=arm-linux-gnueabihf- \ CFG_ARM32_core=y \ CROSS_COMPILE_ta_arm32=arm-linux-gnueabihf- \ CFG_TEE_CORE_LOG_LEVEL=2 \ CFG_TEE_CORE_DEBUG=n \ CFG_EMBED_DTB_SOURCE_FILE=stm32mp157c-dk2.dtsThe full image (st-image-core) I am using is based on meta-st-stm32mp and open-stlinux (dunfell branch)The kernel is the one present in the meta layer: kernel (5.10.61)I am aware that an existing version of OP-TEE is present in the build however it's from version 3.12.0.I tried to build OP-TEE OS version 3.16.0 apart and include it in the final image and it works as expected.I investigated and the issue comes from the linux-stm32mp kernel patches because when I built the stable kernel based on the same version 5.10.61 without patches, it works with OP-TEE 3.17.0 without issu

Bug report in HAL.Under heavy load, the USB Host stack can hang due to the EPDIR flag on an IN Channel being incorrectly cleared by the HAL.stm32f4xx_ll_usb.c, function USB_HC_Halt, clears EPDIR in the case that the request queue is full. This routine is called by IN & OUT interrupt handlers and can there leave EPDIR wrongly reset for an IN channel.In the case of using DMA, tech ref says (in section 'Halting a Channel') that code does not need to check for request queue full - so I think the code should probably take DMA into account as well.I am using DMA, I have commented out the process queue check.

Trying to identify the best temperature profile to ensure an optimum solder flow and resulting solder connection.

Hi everyone,I'm new to using STM32MP1, in particular I bought a STM32MP157A-DK1 and I wanted to know if it was feasible to load Linux with the classic GUI, open a TCP-IP server and run some python code that I had already developed.Thank you all

Hi,I am working on ST25DV64KC NFC chip. I am trying to write system configuration memory from i2c.Steps:1) I have opened i2c security session by sending present password command. I have read I2C_SSO_Dyn register from dynamic register memory and its returning '0x01' means the i2c security session is correctly open.2) After that I tried to change byte value of LOCK_CFG register to 0x01 by keeping first 14 bytes as it is and 15th byte which is LOCK_CFG to 0x01 using i2c block write.3) I have read system configuration registers from ST25 NFC tap android app but LOCK_CFG value is not updated to 0x01.4) For user memory I am able to read and write from i2c side correctly. I am also able to read system configuration memory correctly but failed to write.Note from datasheet:I2C security session must first be open, by presenting a valid I2C password, to grant write access to system configuration registersWhat could be the cause? Am I following correct procedure to write in system configuration?

As I said, I get the assertion "zigbee_app_info.colorControl_server_2 != NULL" failed error from a standard debug function in the code.I thought it could have something to do with this struct, which is a bit above it.struct ZbColorClusterConfig colorServerConfig_2 = { .callbacks = ColorServerCallbacks_2, .capabilities = ZCL_COLOR_CAP_HS, }I feel like it has to be something I have to add here because this struct is checked to be NULL, but I can't seem to find what it is I have to add.The place where the struct is set to something other than NULL is here:zigbee_app_info.colorControl_server_2 = ZbZclColorServerAlloc(zigbee_app_info.zb, SW2_ENDPOINT, zigbee_app_info.onOff_server_2, NULL, 0, &colorServerConfig_2, NULL);From what I could gather, this would allocate the space needed, but I guess something goes wrong and no memory is allocated.This error occurs every time I start a new project and add the color control cluster. So it happens even when I haven't added anything.

I've struggled with this for a few days and read a dozen forum posts that end unanswered.I am trying to put my micro controller into standby mode and then wake it up with an IMU pulling the PA0/SYS_WKUP1 pin high. What I am finding, which is somewhat corroborated by the reference manual, is that PA0 is pulling low harder than my IMU can pull high.The IMU is a BMX160 that is programmable and doesnt require continuous communication with the MCU, it is designed to provide wakeup interrupts for smart watches and wearables. What I have seen is that I am able to pull the WKUP pin High while the device is in normal mode, but not when it is in standby mode. I have triggered an interrupt just before going into standby and watched the pin state go low prematurely. I have made the wkup pin go high while in sleep mode, but gave up on sleep mode after realizing that wakeup and sleep aren't related. I'm wondering if i am either configuring my standby wrong or the wakeup wrong, I am using Cube_IDE an

Hi all,I'm trying to use a version of the elua interpreter on a stm32f446re nucleo board.I've encountered a problem, the program is jumping on an infinite loop after entering a couple of functions of the interpreter. The system is blocking in an WWDG_IRQHandler set to the default irq handler that is a infinite loop, here's the code where it's blocked:/** * @brief This is the code that gets called when the processor receives an * unexpected interrupt. This simply enters an infinite loop, preserving * the system state for examination by a debugger. * @param None * @retval None */ .section .text.Default_Handler,"ax",%progbits Default_Handler: Infinite_Loop: b Infinite_Loop .size Default_Handler, .-Default_HandlerThe debugger can't find the source of the interrupt in the stack trace. Debugging the C code I discovered that the program blocks inside an obscure call to a function pointer, so I tried to debug directly the asm code to find out exactly where the code is blocking and I

Hello !STM32L4R9I support True Random Number ( 32 bits per 1 time generation)I run an example and then make an program to generate 100.000.000 bits1 st iteration (100M bit) : HW is 0.5 and Passed NIST Test2 nd iteration (100M bit) : HW is 0.5001 and Failed NIST Test ( 3 Non-overlapping )Did TRNG pass All NIST Test ?If yes, how to set up NIST Test ? ( I attached my setup as below) If no, why?P/s: https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-22r1a.pdfThanks so much !

..

Same situation as before - using a STM32MP157C based design + KSZ9021GN PHY but now actually wired for MII mode. Previous board was wired for GMII mode, even verified by Microchip/Micrel, not realizing the MPU did not support that mode (should have checked with CubeMX!) . So, we made the change to actually MII wiring into a different but similar board being designed at the time. That board is now being brought up. Again, PHY issue, but different this time and I hope its not another design error. I suppose there could be an assembly problem of course. I only have one board currently to test. Here is the TL;DR of the bootup relating to ethernet. Note "device missing", and we are at address 3. ... [ 2.510008] stm32-dwmac 5800a000.ethernet: PTP uses main clock [ 2.514391] stm32-dwmac 5800a000.ethernet: no reset control found [ 2.520607] stm32-dwmac 5800a000.ethernet: No phy clock provided... [ 2.527384] stm32-dwmac 5800a000.ethernet: User ID: 0x40, Synopsys ID: 0x42 [ 2.533753] stm32-dwmac

I bought an X-NUCLEO-LPM01A that works very well on windows 8 with the STM32 Cube Monitor-Power software. I had to put the driver STSW-STM32102. Then, I tried on Windows 10. However, with Windows 10, it is written that this driver (STSW-STM32102) should not be installed because it is natively included in windows 10. But, the STM32 Cube Monitor-Power software cannot communicate with the board... I had to download the driver STSW-STM32102 made for win8 despite it being discouraged. It works on win10 only with the Win8 driver (for me at least).Is it normal ? Thank you

Hi,I'm computing CRC32 with 04C11DB7 polynomial with different methods : through python binascii.crc32(...), on the following website " https://simplycalc.com/crc32-text.php ", and with ST embedded module on STM32G483.On basic strings such as "0123456789", i get the same CRC from the python library and the website but not from ST (python/web : 2 793 719 750; ST : 4 171 674 919).I enabled ST CRC through CubeMX with a config as in the linked pic, and call it in my code as the following : uint8 data[] = "0123456789"; uint32 crc = HAL_CRC_Calculate(&hcrc, (uint32*)data, 10u);I tried modifying the output and intput data inversion, changing the string and its size, but I can never get the same result as the python/web one which always get the same. I don't really get what could be happening here.Any idea where I could be going wrong? Thank you for your time.