Solved

Hi, I have tons of question about the command $PSTMSETPAR and some related command:​First of all, I would like to change the NMEA Baudrate to 38400, as the software manual said, I should transfer​"$PSTMSETPAR,1102,0x8""$PSTMSAVEPAR"​and NMEA gives me the result (no comma due to the way I'm processing the string):​$PSTMSETPAROK 1102*31$PSTMSETPAR 1102 8​as the manual says, I should reset the system, so I've enter the command "$PSTMRR", and it returns "$GPTXT DEFAULT LIV CONFIGURATION*2B". But when I change my Baudrate from 9600 to 38400, I got scribbled message, only when I change back to 9600 will the message be shown properly. However, after I unpowered my stm32 and power it again, I ""sometime"" find it changes its Baudrate to 38400, vice versa. So here are my questions:​ How to reset X-NULCEO-GNSS1A1: As I dig into the example code from cubeMS, I found that reset is done by setting low on the reset pin, wait for a while, then setting it to high, then wait for a while, but doing so d

I'm trying to develop a custom application, but noticed that if I disconnect the touch screen cable of the AMOLED LCD, the joystick stops working. I'm looking through code for dependencies, but I think it's not in the provided code, but something programmed into the Port Expander, anyone know how where I can find code for that and if not, how can I disable dependencies on the touchscreen so I can keep using the joystick. Thanks!

Hello,I'm a software expert, and ignorant in any hardware fields.I have some faulty air condition controller board, and need help with identifying some faulty component installed on it.Could you please tell me what is this EEPROM component (see picture), and what component could be used to replace it, preferably of FRAM type?Thanks,Mark

We use a CR95HF on our system and communicate with it using SPI. I've already successfully selected a NFC216 tag, read its UID and can read its memory. I'm using the ISO-14443-A protocol and don't make any adjustments to the CR95HF's registers.Writing to memory using the NFC WRITE (0xA2) command>>> 0x0407a20ddeadbeef28 <<< 0x87 (timeout or no tag)fails with error 0x87, despite data being successfully written to the tag.Instead using the NFC COMP_WRITE (0xA0) gives similar results:>>> 0x0403a00d28 <<< 0x90040a240000 (ACK) >>> 0x0411deadbeef00000000000000000000000028 <<< 0x87 (timeout or no tag)However, the data was written in both cases:>>> 0x0403300d28 <<< 0x8015deadbeef000000000000000000000000b244080000Is this expected behavior? According to the NFC Forum Type 2 Tag specification, the tag should respond with ACK after a successful write.

I write a delay function using systick,it works well in stm32f103rbt6，but the same function does not works well when I select another chip stm32f105rbt6.when I toggle the led every 500ms,it is actually toggled every 1562ms,much slower than expected when I measured the delayed time using the oscilloscope.I have checked the 8M Crystal/Ceramic resonators and found it works well.Please help me find the problem,thank you very much!compiler:ARM MDK 5.15LED PIN:PD2RCC:8M Crystal/Ceramic resonators

Hello,I am trying to overcome some strange issue using IAR when starting freeRTOS thread from main.I have used the following example for usb\en.stm32cubeh7\STM32Cube_FW_H7_V1.3.0\Projects\STM32H743I_EVAL\Applications\USB_Host\HID_RTOSIt detects a HID automatically when inserting into board, and display information about it on LCD.But when I started adding some threads, it suddeny stopped detecting the inserted device.After some debugging, I've came to conculsion that it is a matter of stack size.Even if I have only one thread (the usbtest thread) and I give it a large size then it fails:- osThreadDef(USER_Thread, StartThread, osPriorityNormal, 0,        128);+ osThreadDef(USER_Thread, StartThread, osPriorityNormal, 0,        1480);I thought that stack size from main is a matter of changing in icf and rebuild : -define symbol __ICFEDIT_size_cstack__ = 0x400;+define symbol __ICFEDIT_size_cstack__ =

Posted on July 05, 2018 at 08:56 Hi all, I'm having a strange problem with a design using the STM32F072V8 MCU. MCU operates at 3.3V. We have a USB connector internal to the product, solely for programming the MCU via DFU. I have the BOOT0 pin connected to VBUS on a USB connector through a resistor divider that means 3.3V is on the BOOT0 pin whenever USB is connected, and the BOOT0 pin is grounded when no USB is connected. The intended procedure to access the DFU is to: - Connect USB to host while device is unpowered - Power up the device We expect to enter DFU mode since the BOOT0 pin is held high before the system power is up. Instead of entering DFU mode, I see the following in Linux dmesg: [28936069] usb 3-13: new full-speed USB device number 49 using xhci_hcd [28064068] usb 3-13: device descriptor read/64, error -71 [28300075] usb 3-13: device descriptor read/64, error -71 [28536067] usb 3-13: new full-speed USB device number 50 using xhci_hcd [28664084] usb 3-13: device

..

Am working on a SPI driver for STM32H7 (for Ada language).I use the board Nucleo-H743ZI.I'd like to make SPI4 working as a master in full dulplex mode (no DMA mode).What are the proper steps to follow? the reference manual is not very specific (for me as beginner)I tried to follow the C code, but I think am missing something.For the moment what I did:- I configured the GPIO pins SCK to PE2 / MISO to PE5 / MOSI to PE6- The clocks of the GPIO pins are set to Alternate Function mode (value 5), resistors to Pull_Down, speed to 100Mhz, the output type to Push_Pull.- I enabled the clock for the port SPI4-- APB2ENR.SPI4EN register set to 1- I made sure the SPI is disabled to start configuring it-- SPI4.CR1.SPE is false[When I set the the SPI4.CFG2.MASTER to 1 (mode Master), the Mode Fault flag (SPI4.SR.MODF = 1) is raised and can't enable the SPI port anymore.When then I try to set the flag to 0 using the register IFCR.MODFC to 1, the SPI4.CFG2.MASTER returns to 0.Infinite loop...] solved tha

..

I tried a search, but couldn't find the information. This is probably basic and simple, but I just couldn't find how to do it.I'm trying to bring up the Simulator peripheral window so I can emulate the key presses of the joystick in the STM32L4R9I-DISCO kit. I tried the code on the target and it works,a but in simulator I can't see the peripheral window to enter key presses using the keyboard.Thanks for the help!Update: I tried pressing every key on the keyboard, but it still doesn't seem to bring up any peripheral console in simulator. Is there a code snipped that needs to be inserted? I'll check some example and see if I can dig anything up.

Hi I am using STM32F469 Disco Board. In TouchGFX Progress Indicator example the images gets blurred if i placed all the images in external nor flash. But if i placed the same images in internal flash, then it is working fine. What is the issue in this. I'm using Atollic True studio.

Hi, I'm using latest FW STM32Cube_FW_L4_V1.13.0 and the PWR_STOP2_RTC example seems to fail waking from sleep mode. It goes to sleep after 5 s alright and power consumption drops from cca 11 mA to 4 uA but after cca 33 s, as stated in readme, nothing happens, only power consumption rises a little bit to 141 uA. I tried two NUCLEO-L452RE boards and a custom PCB featuring STM32L462RE and the behavior was the same.Could someone replicate this behavior as to confirm my observation or what can I do to get it working??Thanks.

Posted on October 06, 2017 at 10:56I can't find any indication in DS/RM, what OTG_FS_NOE pin might be good for.Please, explain.Jan Waclawek

..

If, as the basis of time, I use a different timer than the systick in the hal_timebase_tim file in the ruler uwTimclock = HAL_RCC_GetPCLK2Freq ();there is an error. Should uwTimclock = HAL_RCC_GetPCLK1Freq ();

Hello, at this moment i'm investigating the possibilities of our current system and would like to know if the 2 Octo-spi peripherals can be used as legacy, normal SPI.

The code works if i enter in stop mode but not if i enter in under drive mode.I think i have to reinit something after stop mode but i dont find what.Here is the code :int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_ADC1_Init(); MX_RTC_Init(); while (1) { HAL_GPIO_WritePin(GPIOB, LED_Pin, GPIO_PIN_RESET);   if (HAL_RTCEx_SetWakeUpTimer_IT(&hrtc, 500, RTC_WAKEUPCLOCK_RTCCLK_DIV16) != HAL_OK) { Error_Handler(); }   HAL_SuspendTick(); HAL_PWREx_EnterUnderDriveSTOPMode(PWR_LOWPOWERREGULATOR_UNDERDRIVE_ON, PWR_STOPENTRY_WFI); // -200uA //HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFI); // 0.450mA   HAL_RTCEx_DeactivateWakeUpTimer(&hrtc);   SYSCLKConfig_STOP();   HAL_ResumeTick();   if (HAL_RTCEx_SetWakeUpTimer_IT(&hrtc, 500, RTC_WAKEUPCLOCK_RTCCLK_DIV16) != HAL_OK) { Error_Handler(); }   HAL_PWR_EnterSTANDBYMode(); } }   void SystemClock_Config(void) { RCC_O

I am using the USBD driver provided by your company to communicate via USB as a virtual com port in STMCube32_FW_F7_V1.7.0. I am using the STM32F7 series. When I receive messages, the buffer fills with additional characters at the end. I have not edited the USBD_CDC.c file, or the interrupts that lead to it. And the additional characters fill the pClassData buffer. This means that none of the data buffers that I have added to the program are adding these characters. They are being inserted before my code manipulates the data at all.Sometimes these additional characters are messages that were previously sent by the device (ex. device sends "HELLO" then the PC sends back "HI" and I receive "HIh23HELLO". Other times they are seemingly random, but consistent (the same for multiple messages (HELLOasd, GOODBYEasd), or only the same for the same message (HELLOasd, GOODBYEdrt5, HELLOasd, GOODBYEdrt5)) depending on a variety of factors. The type of response depends upon the type of termina

..

..

I use __HAL_SYSCFG_REMAPMEMORY_SRAM(); this function ,but MX_USB_DEVICE_Init(); can't work.After I went to debug tool ,it appear cannot access memory this problem.I don't know how to solve it.Maybe it should register address problem,or init address error.

We are suing STM32F429IET6 in our project. The schematics as follow:​if VBAT=2.2~3.6V :backhand_index_pointing_right: :backhand_index_pointing_right: :backhand_index_pointing_right: Power off the VDD and wait 0~180 seconds, then power on again. The RTC always lost(reset to the begin value).if VBAT=1.6~2.0V :backhand_index_pointing_right: :backhand_index_pointing_right: :backhand_index_pointing_right: Power off the VDD and wait 20~180 seconds, then power on. The RTC work fine.if VBAT=1.6~2.0V :backhand_index_pointing_right: :backhand_index_pointing_right: :backhand_index_pointing_right: Power off the VDD and wait 2~15 seconds, then power on. Sometime, the RTC lost(reset to the begin value).RTC lost value when VBAT > 2.2V.How to resolve the issue? Do you have any recommend?Best Regards,Aaron​

Posted on April 21, 2018 at 23:02 I am generating stimuli for a CPLD circuit using my Discovery board - STM32F303VCT. I use CubeMX for peripheral/clock initialisation, and AC6 (Eclipse) for code. I am using TIM15 - PWM CH1/CH1N - One Pulse Mode - with RCR of some value, say N-1. The PWM signals are to run a half-bridge for an AC motor, and hence need to be complementary with a small dead-time. That is, when CH1 is high, then CH1N is low and vica verca, but with a small period where both are low to prevent shorting the bridge. Both may be low, but both may never be high s imultaneously. The code in question is pure polling, where I start the timer-pwm using HAL functions. The first pulse-train is working fine... Both pwm-signals start from idle and generate N pulses with a small dead-time. After those pulses, I have a 500 ms delay, and then generate N new pulses, using HAL again. However, this time I always get a ''glitch'' in the ''pwm1'' signal, prior to the pulse-train, as sh

Disclaimer: I am using V1.14.0 and have not edited the HAL or LL divers. I am running the chip at the USBD CDC example project settings. I am communicating at FS.I am seeing this(hpcd->OUT_ep->xfer_buff) buffer populate with additional/non-existent characters when sending messages to the board. As soon as I send a message to the board, this buffer populates with the additional characters (not the sent character), then I allow the HAL_PCD_DataOutStageCallback function to call and this buffer fills with the message that I sent and keeps the additional/non-existent characters at the end. I have checked and seen that the actual memory register space (USBx_DFIFO(0)) that receives these messages filled with the actual sent character and non-existent characters (it does not "fill" this 1000 byte space. It fills the first few bytes that contain my sent message and the additional characters). This space being 0x50001000 on my stm32f7xx chip. This space is set to zero before enumeration, t