Solved

Hi,my post build command produces the following output with 16 Byte per data line:  :020000040802F0 :1000000000000120E9C00008593D0008CD3D00086E :100010001D3E00081F3E0008213E000800000000B1arm-atollic-eabi-objcopy.exe -O ihex --gap-fill 0x00 --pad-to 0x08019000 "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.hex"   I want to have 32 Bytes in a data line e.g.  :020000040802F0 :2000000000000120E9C00008593D0008CD3D00081D3E00081F3E0008213E0008000000002F  What additional flag can I use to change this?Thanks in advanceMartin

I use stm32wb5x_BLE_Stack_full_fw.bin v1.13.2 on STM32WB5MMG.The installation address is 0x080CF000.What happens if I write the stack to the wrong address (0x080C7000, the install address for v 1.13.0).In my board, it looks work fine. Is there any concern or limitation?

hello , i want link to download touchGFX and gui 

I know the product is new, but are there already some plans on the horizon to maybe increase the flash size and/or have some more intermediate sizes?

Hi, I have a question. I just completed a program for a dual processor MCU, specifically an STM32H745, which has one M7 core and one M4 core. Now I have to organize the production of a hundred cards, and the manufacturer asked me for the .hex file to load into the chip. But in the CubeIDE project, two completely separate projects were generated, each of which generated a .hex file. So I find myself in the situation of having two .hex files, one for the M4 and one for the M7, while the manufacturer of the card, having only one chip, expects only one .hex file to load. How should I proceed in this situation, what is the exact procedure to load two .hex file into the same chip?

Hello, I'm STM F/W Beginner .Recently, I was tasked with a project to implement BLE with the Stm32wb MCU.As a result of referring to Example such as Heartrates or P2PServer Projects, I could successfully send Data to a mobile phone by Nucleo Board.However, I still can't receive and handle Data with my board.Is there any example I can refer to?    

Hi,does someone know the diffenences between MP34DT05 and MP34DT05-A?The MP34DT05 is not in prodiction. Cant find other differences, what does the -A means?Thanks for helping me out.

Hello,​ I am able run successfully mqtt example on my stm32f4 MCU ​and on my local network.​I want to run the same code on a cloud platform. However there is a link provided by mqtt cloud pro​vider not an IP address like 192.168.0.10​​Can I directly use the below link instead of the IP address ? If not, then How can I ?​​1f87a053302042c7a0ccb2dac5d1263b.s1.eu.hivemq.cloud​B​est Regards​​

 Hello all,                   I made custom PCB board with STM32WB5MMG in my project. I have confirmed that the SWD pins are working and Code is Debugging ok.I have also set up HSEM, IPCC, RCC, RTC, RF, STM32_WPAN required but I can't detect the Bluetooth.Iam using  STM32CUBEMX V6.8.1 and STM32CUBEIDE V1.12.1Firmware package version is 1.16.0 (STM32Cube_FW_WB V1.16.0) . 

Encountered an annoying project generation bug recently. By default CubeMX adds to keil project a hwhole bunch of files:Even if you don't need any of the LL. So, when you tick "Enable Full Assert" checkbox, it causes an error, because no "stm32_assert.h" file was created. Probably because cube unnecesarily adds LL lib, but never generates it's templates. I'd suggest to look into it's pack xml or whenever list of necessary files is stored 

Hello All, I am very beginner in embedded technology. I would like to learn and implement XIP.Currently I am working on a project which uses STM32F746 discovery board and uses TouchGFX and FreeRTOS. It uses qspi in memory mapped mode to store the font, graphics and text section required for touchGFX application. I am looking for documentation which explains the functionality and concept to achieve XIP using qspi along with FreeRTOS and touchGFX.Any inputs are highly appreciated. Please forgive me if my post is not adhered to STM Community standards as this is my very first post. Thankyou for your time and consideration. Regards,Pitbull

Hello, i configured FreeRTOS to enter STOP2 mode on idle task, my wakup source are RTC and LPUART. when the mcu is waked up by RTC according to ulExpectedIdleTime, every think is ok but when it is waked up by the LPUART the tick count is not updated correctly (so all my software timers are not executed with the right period) it should be an implementation on PostSleepProcessing() to modify the value of ulExpectedIdleTime according to RTC counter, but i cannot find how to do it ! any body have an idea ? where i can find the RTC counter for wakeup timer (i already checked all RTC register, i assume that it exist, but i cannot find it)   void PreSleepProcessing(uint32_t *ulExpectedIdleTime){ //LPUART : //make sure that no LPUART transfer is on-going while (__HAL_UART_GET_FLAG(&hlpuart1, USART_ISR_BUSY) == SET); //make sure that LPUART is ready to receive while (__HAL_UART_GET_FLAG(&hlpuart1, USART_ISR_REACK) == RESET); //set the wake-up event:specify wake-up on

Hi all,  I have designed and built a custom circuit using the ST25R3916 (in differential mode with AAT) and a ATxmega128A4U micro controller. I have spent the last two weeks trying to get it working so my phone can detect it as a card as a starting point. Eventually I want to the phone to read data files from the device.  I believe I have the hardware working, as I have a 13.56MHz signal on the antenna which is +-7V and I get EON and EOF interrupts when I place my phone over the antenna.  However, I am not able to get the phone to detect it as a card. I feel that I am 90% of the way there, but I am struggling to understand the configuration of the chip fully and the RFAL code in ST25 embedded lib (STSW-ST25R016 for 3916) which I have spent quite a bit of time looking at. It is way more complicated than I need and I cant find the basic initialisation that I need.  I have been through other forum threads including this one, and tried to replicate the register settings

Hello,I'm building a proprietary NFC reader based on ST25R3917 chip and STM32F070CBT6 MCU. I use Bare Metal approach without any HAL or RFAL which might complicate my query a bit but I'll try to ask anyway. So far I'm able to Poll Type A and Type B cards, carry APDU over higher protocol layer etc without any issues. What I'm struggling with is switching over to WakeUp mode to save power.Below is a log of i2c communication from none-eabi-gdb. << represents a flow to the reader:<< Direct Command: 0xc0<< Address: 0x0, Data: {0x0, 0x80, 0x0}<< Address: 0x16, Data: {0x6e, 0x9f, 0xff, 0xff}<< Address: 0x10, Data: {0x7, 0x0}<< Address: 0x13, Data: {0x21, 0x1b}<< Address: 0x2, Data: {0x80}<< Direct Command: 0xd3<< Address: 0x34, Data: {0x63}<< Address: 0x33, Data: {0x32, 0x30}<< Address: 0x32, Data: {0x38, 0x34}<< Address: 0x2, Data: {0x4}<< Address: 0x16, Data: {0xff, 0xff, 0xfb, 0xff}Basically I follow&nb

Hello, When i configure a project with CubeMX and TouchGFX Generator stuff and save this,after a new start of CubeMX and opening the .ioc file again i get this error message:And my TouchGFX Generator Configuration is lost. The other configuration is still there.Now, under "Software Packs Component Selector" the Generator Application is "Not selected" although i selected the Generator Application in the previous session:After selecting the Generator and Clicking OK button, the TouchGFX Generator is back, but not what i have configured there in the previous session.Does someone know why this happens? I use:Debian Linux 11.9CubeMX 6.10.0X-CUBE-TOUCHGFX 4.23.0 Thank you. 

I'm using STM32CubeIDE (Linux generic version) on Linux Mint Debian Edition, KDE Window Manager. When starting it as normal user the Themin is not working (Preferences-General-Appearance). The window has a dark theme (the one I choose in my KDE preferences). But I would like to use the default light theme. The only way to do this is by running STM32CubeIDE with sudo. Is this expected or is there a workaround?  Thanks

I am struggling since days to get "my audio" out via SPDIF (electrical).What I see on scope (there is a voltage divider and cap for DC-free on PC12, Vpp is 0.6V, approx. 75 Ohm impedance):It makes sense - but my SPDIF receiver (a STM32F769I-DISCO board, which works fine as SPDIF receiver with another source) does not get any audio (but it seems to sync and realize there is SPDIF signal, but completely silent).Intention:any audio I have in MCU (it will be PDM MIC via CODEC to I2S, as 24bit, 48 KHz) should be forwarded via SPDIF TxI want to use SAI2_B as SPDIF Tx (with PC12), also as 24bit (both are 48 KHz)I tried with "faking", sending buffer content for SPDIF Out as a sine wave (24bit, 48 KHz) #ifdef SPDIF_TEST #define SPDIF_TIME 100 #define SPDIF_WORDS 4 /* 24bit values, but 32bit word */ #define SPDIF_CHANNELS 2 #define SPDIF_AUDIOFREQ 48 #define SPDIF_DOUBLEBUF 2 int32_t SPDIF_out_test[SPDIF_CHANNELS * SPDIF_AUDIOFREQ * SPDIF_TIME * SPDIF_DOUBLEBUF] __aligned(4); void Genera

Create IOC file with CubeMX at "Root"Generate code from CubeMX for IAROpen "Root\TouchGFX\NGEN_NTZ.touchgfx" in TouchGFX designer and generate the code.It fails, as it tries to update project in "EWARM\Root" instead of "Root\EWARM", i.e. one level up comparing to what it is supposed to be.By manually creating extra directory "EWARM\Root" and placing there fake EWP project file, the problem gets fixed and Designer is able to finish code generation. However, then that file has to be manually edited to change correctly referenced but from incorrect location files and then be copied back to a proper location at "Root\EWARM".Seems like there is still some problem with counting dots in file paths. However, 23.1 places all the rest of files at correct locations, unlike previous versions, which is definite progress!See the attached screenshot. Thanks 

Hi, I need a comprehensive description of STUSB1602 registers to see if there's a possibility to control the I/O lines with them. I checked the git repository of firmwares and found something but I'd like to get a general description of the registers and what can be done with them. This seems to have been asked before without any clear replies and I can't find it in ST documentation either. So if you know any links that tell something about this, please post here.Another question is: what is the reason a pull-up is required on the SPI lines?The problem is, the MOSI line is sinking 200uA excess current due to the 10k pull-up when the device is in standby mode and this is not acceptable in this battery operated device. Is there a way to set the I/O pins in different states to avoid such current loss? There's a STM32G071 on the other end which currently has its SPI pins defined as no-pull.If I remove the resistor this current doesn't flow and the problem disappears. But does the SPI bus w

Hey!When I use images in TouchGFX, the color sequence seems different than in regular widgets. It only appears when images are stored on external flash (QSPI flash in my case), images stored on internal flash are fine.Below is an example: the top 3 squares are BOX widgets, the bottom 3 are images in .png format.In TouchGFX:IRL:I'm driving RGB display with LTDC module. I'm using the ARGB pixel format, so the pixels are aligned at 32 bits:Also I tried to fill framebuffer manually with pixels to verify their colors and everything showed as expected:   const uint32_t colors[8] = { 0xFFFF0000, // Red 0xFF00FF00, // Green 0xFF0000FF, // Blue 0xFFFFFF00, // Yellow 0xFFFF00FF, // Magenta 0xFF00FFFF, // Cyan 0xFF000000, // Black 0xFFFFFFFF // White };   What setting am I missing?

Hello,I am working on a version of the STM32L476RG_NUCLEO_AP2P_PROP_NFC8 demo included with the RFAL library examples, trying to get it going on a NUCLEO-F072RB.I have my code running, and if I bring an L476RG flashed with the unmodified AP2P demo, the boards will transact, but the F0 board is always the initiator.  Previously, when using two L476RG boards and the original demo, they would change which was the initiator and target depending on the timing they were brought in proximity.I've been debugging thoroughly, but I can't quite narrow down what my issue could be.  rfalNfcWorker() seems to be setting gNfc.state to the correct states: RFAL_NFC_STATE_POLL_TECHDETECT, RFAL_NFC_STATE_LISTEN_TECHDETECT, etc.  I've noticed when stepping through, though, that it never leaves RFAL_NFC_STATE_POLL_TECHDETECT, but if I set a breakpoint at the different cases in rfalNfcWorker() it will cycle through them during discovery.My big issue: when I program two F0 boards with my modifi

Beside an already solved warning (.elf has a LOAD segment with RWX permissions),after updating the STM32CubeIDE to version 1.15.0 I am observing the second warning below:C:\ProgramFiles\STMicroelectronics\STM32Cube\STM32CubeIDE_1.15.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256\tools\arm-none-eabi\bin\ld.exe: C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeIDE_1.15.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256/tools/bin/../lib/gcc/arm-none-eabi/12.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc.a(libc_a-getentropyr.o): in function `_getentropy_r':(.text._getentropy_r+0xe): warning: _getentropy is not implemented and will always fail In those C++ projects I’m retargeting std::cout from iostream to the serial line. But the same problem comes up,when I’m retargeting printf from cstdio or stdio.Are there any ideas to solve

Hello everyone, I have to communicate I2C to IC TM1640. In this datasheet of the IC, It show me this IC don't have address and not response ACK. So, my Stm get stucked when i wait for Txe bit is set.How can I fix this?

Hi,After deleting some actions from a project I get this error:Sorry - something unexpected has happened which caused an error to occur in the Designer.For more information, see the log file located at: C:\Users\admin\AppData\Roaming\TouchGFX-4.23.2\TouchGFXDesigner.logPlease consider reporting this bug and steps to reproduce it at the TouchGFX Help Center so it can be fixed in a future version.You can find the Help Center here: https://community.st.com/touchgfxError: Should never convert Action   

Using HAL_ADCEx_Calibration_Start() to calibrate the ADC. This function always returns HAL_ERROR.Debugging shows its failing after it collects the 8 samples and attempting to disable the ADC is timing out.  (ie.  if ((HAL_GetTick() - tickstart) > ADC_DISABLE_TIMEOUT) is TRUE.)Using CubeMX to generate drivers. CubeMX version 6.8.1Note: ADC conversion are working IF I don't calibrate. Thanks for your help.