Solved

Using Rowley Crossworks and CMSIS DSP V5.6.0 library. Function  arm_cfft_f32 works but arm_rfft_fast_f32 hard faults. arm_cfft_f32 (&arm_cfft_sR_f32_len16, TestInput, 0, 1);   arm_cfft_f32 (&arm_cfft_sR_f32_len16, TestInput, 1, 1);   status = arm_rfft_fast_init_f32(&S, 32); arm_rfft_fast_f32(&S, TestInput, TestOutput, 0); //FAULTS !The call to arm_cfft_f32 works as forward and inverse and the call to initialise the fast rfft works but the call to arm_rfft_fast_f32 hard faults.Anyone know if the CMSIS DSP 5.6.0 has problems?I'm using the Cortex M7 little endian + FPU version and have added the appropriate preprocessor definitions.

Hi,I'm using the F469I-DISCO Board, since a couple of days I can't pause the execution of my program, without it causing a Hard Fault after continuing. I know it doesn't have anything to do with my code, because I took old projects, which ran fine and tried to debug them, and the hard fault handler triggers again.The Hard Fault Handler reads: Attempt to do exception with bad value in EXEC_RETURN number (INVCP).PC and LR just point to the last executed function, but since it always occurs in different parts of code, this doesn't really help.The only thing I could think of was the IDE being at fault, if I remember correctly these things happened, after I set some printf breakpoints, but I removed them all.Are there any things I can set in the IDE, because even after creating a new project the hard fault gets triggered.

Noticed that new Cube versions and CubeIDE, generate initialization code for UARTs TX and RX pins with GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOWPrevious Cube versions (at least 4.x) generate instead GPIO_SPEED_FREQ_VERY_HIGH.Was this change intentional?GPIO_SPEED_FREQ_LOW seems to work on H7 at least at 115200. But can it make trouble at higher speeds?-- pa

Hi there,I am working on Murata cmwx1zzabz (i.e. STM32L072CZ) and my code is based on the ST en.i-cube_lrwan. For all the basic stuff (joining, sending messages) it runs fine. The Mac commands, that actually manage the network, are OK except the "sticky" ones.As stated in the Semtech library, "The sticky answers were introduced to the specification in order to ensure that critical MAC commands have been understood by the end-device. You can see the sticky answers like an acknowledgement." So these sticky Mac commands require some acknowledge from the device because it is related to critical parameter (sticky Mac commands are SRV_MAC_RX_PARAM_SETUP_REQ, SRV_MAC_RX_TIMING_SETUP_REQ, SRV_MAC_DL_CHANNEL_REQ). So when the device is receiving one of these, the Mac layer notifies the application layer that an uplink is required as soon as possible. The MlmeIndication callback is then executed.But looking at the ST library lora.c (more specially LORA_TxNeeded() ) nothing is implemented. Nothin

In the document RM0407 Rev.5 there are two different memory maps on pages 87 and 717.  According to p.236 we have to write 2 DCF records (16 bytes) in one program operation, but now we have RESERVED area after DCF Start record area. How we should write start record properly? The screenshots are attached.

I sended a dr_swap request, and the target will response a ack/reject/wait. I use the follow api to send dr_swap, and the target response a reject. However, this api just return USB_OK not USBPD_REJECT. And where I could get the response from the target?yy = USBPD_PE_Request_CtrlMessage(port_num, USBPD_CONTROLMSG_DR_SWAP, USBPD_SOPTYPE_SOP);

..

I have found something which is unexpected behaviour / errata in the STM32G071's DAC. In summary, once the DAC channel is enabled (in this case I'm using CH2) then the pin cannot be used as a normal GPIO output, even if the DAC's output buffer is disabled and its mode is set to 011 or 111 (DAC routed to on chip peripherals with buffer disabled). The manual seems to indicate otherwise, but is unclear. (15.2 says "Each DAC output can be disconnected from the DAC_OUTx output pin").Test setup as follows : STM32G071xRB Nucleo64 board: PA5 (the LED pin) set to : MODE for PA5 = 0x1 (output)OTYPER for PA5 = 0 (push/pull)OSPEEDR = 0 (low speed)LCKR = 0AFRL for PA5 set to 0DAC CH1 and 2 set up : DAC->CR EN1 and 2 set, no other bitsDAC->MCR MODE1 and MODE2 set to 0x3 or 0x7 (DAC channel connected to on-chip peripherals with buffer disabled - tested with both 0x3 and 0x7)I am using Keil and testing the results in the debugger, but observed same behaviour when running

Hi SirI used the same e-marker cable that i tested with FUSB307BGEVB.The Ra in the cable can be detected when i used the FUSB307EGEVB but it didn't be detected by the STUSB1602.I tracked the code i found that when cable attached then the register value of 0Eh was 2Dh which means Sink attached.But i except to see 2Fh which means Powered cable with sink attached.In the STUSB1602 evb i close the JP400 that makes Vconn from the local regulator.Dose the STUSB1602 needs to configure other setting to detect the Ra ?I have read the UM2191 but can't find any hint.Please give me some suggestion to fix the issue.Thanks.BRJohn

I am using the NUCLEO-144 (STM32H743ZI) board. It contains the following memory regions:DTCMRAM (xrw)   : ORIGIN = 0x20000000, LENGTH = 128KRAM_D1 (xrw)   : ORIGIN = 0x24000000, LENGTH = 512KRAM_D2 (xrw)   : ORIGIN = 0x30000000, LENGTH = 288KRAM_D3 (xrw)   : ORIGIN = 0x38000000, LENGTH = 64KITCMRAM (xrw)   : ORIGIN = 0x00000000, LENGTH = 64KFLASH (rx)   : ORIGIN = 0x8000000, LENGTH = 2048KAll I would like to do is assign the data section to RAM_D2 and the bss section to RAM_D2. The issue is when I set the data section to RAM_D2 in the linker script, the application I build hard faults (InvState Error) on the following instruction in the startup script:/* Call static constructors */  bl __libc_init_arrayThe following is how I am assigning memory to data and bss sections: /* Initialized data sections goes into RAM, load LMA copy after code */ .data :  {  . =

STM32CubeIDE: Version: 1.1.0STM32MP1 FW Package: I built a custom and default device tree for A7, and fails to compile because of a syntax error (same line in both cases)| NOTE: make -j 12 HOSTCC=gcc -isystem/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/include -O2 -pipe -L/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/lib -L/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/lib -Wl,-rpath-link,/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-li

on pg 22 per DocID029105 Rev 1 for Long Rangewe are able to setsignal rate to 0.1mcpsdefault timing budget is 33ms so no change thereVCSEL pre range period to 18VCSEL final range to 14but cannot do the final recommended setting configuration of setting Sigma to 60I know the attached isn't a validated library but it has worked for us and was hoping for assistance to expand from it for long range.

Hello, I`m using M24SR64 to config wifi using I2C on Raspberry Pi.And now I have a problem that after conmunicating with M24SR64 by I2C, and deselect I2C session, I found the RF session is closed too. I want to use Android App to config NDEF message after deselecting I2C session. I found in the datesheet that "An RF session is taken when M24SR64-Y receives a valid Select Application. " but I didn`t find the "Select Application" command.Can anybody helps me out?Thank you very much!

Hello,I would like to use the STM8L001J3. I am very new with STM8 family. I used to using STM32. STM8L001J3 seems to be great for my application, i started to draw the schematics but i wonder how to connect the debug probe. For VCC, VSS, and SWIM pin, it is ok, but there isn't nRESET pin ... How the probe could monitor the CPU without reset ? Am i wrong ?Thank you in advance.Best regards,Aurélien

My X-NUCLEO-GNSS1A1 does not have any response after changing the baud rate. How can I recover it?I have write the following commands to change the baud rate:​$PSTMSETPAR,3102,0x5*66$PSTMSAVEPAR*58$PSTMSRR*49​After setting to it , if fail to have any UART output anymore. Only PPS have some changes every second. I have tried to use Teseo-Suite Pro 's "STA808x/9x Firmware Upgrade", I select the options "Recovery" and the binary is downloaded from the official website, however the status is keeping at " Sync in progress". How can I recover the board? Thank you

Hello ST community,What is the purpose of Carrier cancellation circuit and Log amplifier in RF chain? We are making a standalone circuit design on our own pcb, Do we need to include that in our design?Thanks and Regards,Sumeet Patil

..

Hello,I have project currently running in the simulator only. One screen consists of a swipe container with several pages, in the swipe container is a scroll list. I've created a custom container for the scroll list and one of those widgets is textArea. The text area contains one wild card. I've unchecked Auto-size for the text area, set the text as <v>, selected Wildcard 1 as single use, checked Use WIldcard Buffer and set an initial value. In Typographies, I've set the Wildcard Ranges for that typography as 0x20-0x7E. I use the following code in my screenView.cppvoid settingsScreenView::portSelectListUpdateItem(listItemContainer& item, int16_t itemIndex) { uint16_t buffer[32]; uint8_t size = 32;   if(itemIndex >= 0 && itemIndex < PORT_MAX) { presenter->getPortString(itemIndex, buffer, size); } else { Unicode::snprintf(buffer, size, "STRING_ERROR"); }   touchgfx_printf("buffer: %s, size: %d, itemIndex: %d\n", buffer, size, itemIndex);

Do they coexist peacefully on one system? Will CubeIDE overwrite any components such as OpenOCD or programmer, or standalone CubeMX data?Thanks,-- pa

Hi everyone,Figured I banged my head against a wall long enough, so might as well ask even if it is a really simple fix.So far I have only used USART2 to write data to the Virtual COM port from my nucleo board, now I have need to write other data out through a different USART channel (USART1).I generated the template for the initialization for both of the USART ports using CubeMX and I double/triple checked the initialization are the exact same minus the Ports and Pins the TX/RX are mapped to.I am using the HAL_UART_Transmit() (not the DMA or IT) function, and it works flawlessly on USART2 but nothing happens when writing to USART1. I have stepped through the function and everything is the same, it is successfully writing it but I am not receiving anything on the transmit line (Serial console on PC). I have also tried receiving with USART1 and I still am receiving nothing on the nucleo board end.I have debugged this from many different ways and I feel like I am missing a specific step

Hello,I am developing a USB HID application on STM32L443. The HID communication works in both directions when I put the controller in Sleep mode with WFI and Sleep on Exit. I am currently experimenting on the suspend/resume capability of the USB. I have 2 LED on my board and I toggle them in the USB interrupt routine on suspend and resume events. On a Linux host machine I am using the powertop utility to manually send suspend and wake-up signals. I assume this setup works, because the LEDs flash the way they should when I send the suspend/wake-up commands. According to the datasheet, the USB peripheral is able to wake up the MCU from Stop0/1 modes. So I try the following in the USB interrupt routine:if (USB->ISTR & USB_ISTR_SUSP){       USB->ISTR = USB_CLR_SUSP;       USB->CNTR |= USB_CNTR_FSUSP;       USB->CNTR |= USB_CNTR_LPMODE; if(device_status == USB_CONFIGURED)

I can connect from STM32CubeProgrammer via ST-Link/v2 running V2J3457 when I lower the frequency from 9000Hz to 2250Hz. However, I can't connect from the STM32CubeIDE debug because there is no (obvious) way to set the frequency.

Hi there,I am trying to get the ID of the MP1 from a given address. But when I try to do so in Linux, using the microprocessor core A7, it gives me a Segmentation fault (core dumped) error.When I run the same program on the microcontroller, core M4, it prints the ID just like this:[0]2359324[1]859328773[2]876098352How can I get that same ID when running my code on Linux?Here is my code:#include <stdio.h> #include <stdint.h>   // 0x5C005234 is the address where the ID is stored #define VAL ((uint32_t *) 0x5C005234)   void main(){   printf("[0] %d [1] %d [2] %d", VAL[0], VAL[1], VAL[2]);   }

I'm working on getting a Distribution Package build working on an aarch64 machine, specifically a Nvidia Jetson Nano. After downloading the 1.1.0 ecosystem package and sourcing the bitbake environment, bitbake st-image-core runs successfully for a while but fails while executing the strip command in the populate-sysroot section of gcc-arm-none-eabi-native-7-r0. When I execute the strip command by hand the failure is actually an "unknown format" error on the file being stripped. When I execute the "file" command against the file giving the error it has been compiled for x86_64. This would imply, I think that the recipes for gcc have be set up for a 64-bit Intel architecture. My question is where do I modify the recipes to ensure they are using the local machines architecture to build the components?An example of the error I am getting is:ERROR: gcc-arm-none-eabi-native-7-r0 do_populate_sysroot: Fatal errors occurred in subprocesses:Command '['strip', '--remove-section=.comment', '--remo

I'm running out of ideas, there is no interrupt triggered when sending data over I2C.Processor: STM32L451Middleware: FreeRTOSI2C interrupts are enabled in STMCubeMx, also pins are configured for I2C.Sending data with HAL_I2C_Master_Transmit_IT():CR1: PE, TXIE, NACKIE, STOPIE, TCIE, ERRIE are enabledISR: BUSY, TXIS, TXE are setHandlers for all I2C interfaces (event and error) are placed in the interrupt vector table in startup_stm32l451vetx.sDirectly in these handlers i put a breakpoint and additionally turned on a debug LED, but neither the breakpoint is reached nor the LED is turned on.I tried it with all 4 I2C interfaces, none triggers an interrupt.On the I2C line, i can see the first byte is sent and acknowledged by the receiver; the ACK also disappears after one clock, so the I2C interface obviously has received the ACK.Tried it with another board as well, to no success.Sending data with HAL_I2C_Master_Transmit() (not interrupt driven) works fine.Then i enabled the debug LED in the