Solved

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

Hi, I want to send five,16 bit data over SPI. WHile executing the code i cant see any transmission. What i wanted isSS = 0 -> 16 bit data1 -> SS=1, SS = 0 -> 16 bit data2 -> SS=1,or2, SS=0 , word0, word1, word2,word3, word4 ss=1i tried both methods but no action..How to configure FifoThreshold and NSS. DDS_CS_Pin is CS and is connected to PD14HAL_GPIO_WritePin(GPIOD,DDS_CS_Pin,0); HAL_Delay(1); HAL_SPI_Transmit(&hspi6, (uint8_t*)&DDS_CR, 2, 10); HAL_SPI_Transmit(&hspi6, (uint8_t*)&DDS_FL, 2, 10); HAL_SPI_Transmit(&hspi6, (uint8_t*)&DDS_FH, 2, 10); HAL_SPI_Transmit(&hspi6, (uint8_t*)&DDS_PR, 2, 10); HAL_SPI_Transmit(&hspi6, (uint8_t*)&DDS_RST,2, 10); HAL_Delay(1); HAL_GPIO_WritePin(GPIOD,DDS_CS_Pin,1);static void MX_SPI6_Init(void){ hspi6.Instance = SPI6; hspi6.Init.Mode = SPI_MODE_MASTER; hspi6.Init.Direction = SPI_DIRECTION_2LINES_TXONLY; hspi6.Init.DataSize = SPI_DATASIZE_1

When trying to initialize external SRAM in the SystemInit() function in system_stm32lf76xx.c, I call HAL_Init which calls HAL_InitTick. This function calls HAL_SYSTICK_Config which uses the global variable SystemCoreClock to initialize the SysTick. However, it seems like SystemCoreClock is not initialized in memory at the time it is being called here. Are there any workarounds for this?

Hello,I have recently moved RAM from DTCM to AXI SRAM (so that I get more RAM).It then failed in dma example.After investigation I found out that the call to  SCB_InvalidateDCache results in HardFault_Handler.I've changed it to use   SCB_InvalidateDCache_by_Addr((uint32_t *)aDST_Buffer, (BUFFER_SIZE));and now it function OK, but I don't yet understand why SCB_InvalidateDCache fails with AXI SRAM.I am using st32h743-evalThank you,ranran

Hi,I installed the Unico 7.0.0, the driver for the MKI109V3 and the DfuSe application contained in the MKI109V3 package. I wanted to upload the firmware on the board as the instruction manual UM2116 says. Therefore I changed the board to DFU mode and I uploaded the firmware eMotionV5.0.0.dfu that is in the folder named FIRMWARE (also contained in the package). After the upload was completed I clicked on the option of "Leave DFU mode" in the DfuSe program. Suddenly the LED stopped blynking and the board disappeard of the Windows Device Manager. Now I cannot use the board. My supposition is that I uploaded the wrong firmware that makes the board unuseful. Do you know what can be done in this case? How can I upload the right firmware?

Hey guys,I have expereinced a very strange behaviour of my STM32F429ZIT6 custom board:When I execute the following code the processor behaves differently in free running then in manual stepped mode or my oscilloscope seems to be completely broken - which I doubt. _5_PLUS_COIL_HIGH; delay_TIM10(50); STANDARD_COIL_LOW; _5_MINUS_COIL_LOW;the macros behinde _5_PLUS_COIL_HIGH , STANDARD_COIL_LOW and _5_MINUS_COIL_LOW are simply GPIO output state settings:#define STANDARD_COIL_HIGH STANDARD_COIL_GPIO_Port->BSRR = STANDARD_COIL_Pin #define STANDARD_COIL_LOW STANDARD_COIL_GPIO_Port->BSRR = (STANDARD_COIL_Pin << 16U) #define _5_PLUS_COIL_HIGH _5_PLUS_COIL_GPIO_Port->BSRR = _5_PLUS_COIL_Pin #define _5_PLUS_COIL_LOW _5_PLUS_COIL_GPIO_Port->BSRR = (_5_PLUS_COIL_Pin << 16U)and the function delay_TIM10(50) is a msec delay function:#pragma GCC push_options #pragma GCC optimize ("O3")   void delay_TIM7(uint32_t ucnt) // IMPOR

Hello, I found a problem in eDesignSuite when i try to use STNRGPF01 (PFC boost interleaved IC).At input current sensing the ICS Target Voltage is 3.00V and in the datasheet the ICS Target Vltage looks like it is 1.25V (also in the Help section of eDesignSuite). Which one is correct?Also, is there any other datasheet (maybe we need to sign an NDA for it or smth like that) because the one on the site is very poor.Best regards,Mihai I.

Hello, I already used x-cube-nfc4 as a basic code for application use of RFID tag but it didn't work only it indicates the nfc tap while using near to tag and even this code doesn't support uart. So, i want to know why UART is not supporting in it. I am attaching the code which I used.#include "main.h"UART_HandleTypeDef huart;sURI_Info URI;extern sCCFileInfo CCFileStruct;/* Private function prototypes -----------------------------------------------*/void UARTConsoleConfig( void );HAL_StatusTypeDef UARTConsolePrint( char *puartmsg );extern void SystemClock_Config( void );int main( void ){  char uartmsg[6]="hello"; HAL_Init( ); /* Configure the System clock */ SystemClock_Config( );    /* Init of the Nucleo Board led */// BSP_LED_Init(LED2); /* Init of the Leds on X-NUCLEO-NFC04A1 board */ NFC04A1_LED_Init( ); NFC04A1_LED_ON( GREEN_LED ); HAL_Delay( 300 ); NFC04A1_LED_ON( BLUE_LED ); HAL_Delay( 300 ); NFC04

ES0320 [1] describes an I2C errata "Spurious bus error detection in master mode":DescriptionIn master mode, a bus error can be detected spuriously, with the consequence of setting the BERR flag of the I2C_SR register and generating bus error interrupt if such interrupt is enabled. Detection of bus error has no effect on the I2C-bus transfer in master mode and any such transfer continues normally.WorkaroundIf a bus error interrupt is generated in master mode, the BERR flag must be cleared by software. No other action is required and the ongoing transfer can be handled normally.I have two questions:Does this mean we won't be able to detect actual bus error situations because we are required just to ignore it?Can a DMA transfer be halted because one of these "spurious" bus error detections? Or maybe we are in luck and DMA doesn't give any attention to the BERR flag?Thank you.[1] https://www.st.com/resource/en/errata_sheet/dm00218224.pdf

Posted on March 20, 2018 at 03:12Hi all I am making RF reader using ST25R3911B.Communication distance should be more than 50cm.Please let me know if is possible without an external power amp.#st25r3911b

Posted on May 02, 2018 at 14:34Hi,I am developing a product based on the AS3993, AKA ST25RU3993. I have been using the FEMTO module (by AMS) to test my application code.So far I was able to verify the initialization, SPI, interrupt line, cristall stabilization and PLL lock. Everything seems to be OK.I am now trying to read a TAG.Using the defautl configurations of the FEMTO, as follow:In order to start reading a tag. I first write the values above in the registers, then I enable the bit RF_ON on register 0x00.After send the Query command 0x98 and write the following bytes to the FIFO://0b00//dr = 0b01//m = 0b10//Trext = 0b000x18//sel = 0b00//session = 0b00//target = 0b00//q = 0b000x00After that I start to wait for the end of tx interrupt, but I detect a irq_noresp instead.Any insights?

The vertical scroll bar in the GPIO Settings window used in various peripheral does not appear.Left-click on a timer (for example), in the central window you can see the "Configuration -> Parameter Settings" with the vertical scrol bar, this is OK. It's possible to scrol the window:Instead selecting "GPIO Settings" and clicking on a line of a GPIO to check the settings, we get:The vertical scroll bar is missing, and the upper part overlaps with the lettering and does not allow you to read the settings. There is no way to scroll the window.Obviously this happens with small monitors (15 "). With large monitors (22") this does not happen because seeing all the lines of the parameters it is not necessary to scroll the window.Are you already aware of this defect?RegardsAndrea

..

DMABR->SR should be auto-cleared when set 1.I haven't modified code - auto generated by hal.It always timeouts - any ideas why? I tried to extend timeout time - bit 0 is always 1.Here is code from HAL: /* Ethernet Software reset */ /* Set the SWR bit: resets all MAC subsystem internal registers and logic */ /* After reset all the registers holds their respective reset values */ (heth->Instance)->DMABMR |= ETH_DMABMR_SR; /* Get tick */ tickstart = HAL_GetTick(); /* Wait for software reset */ while (((heth->Instance)->DMABMR & ETH_DMABMR_SR) != (uint32_t)RESET) { /* Check for the Timeout */ if((HAL_GetTick() - tickstart ) > ETH_TIMEOUT_SWRESET) { heth->State= HAL_ETH_STATE_TIMEOUT; /* Process Unlocked */ __HAL_UNLOCK(heth); /* Note: The SWR is not performed if the ETH_RX_CLK or the ETH_TX_CLK are not available, please check your external PHY or the IO configuration */ return HAL_TIMEOUT; } }Bit 0 SR: Software reset When this bit is

I want try the new stm32l0 series, stm32l010k8t6, but when I used stm32cube to generate MDK project, the MDK seems not support stm32l010 already. So I looked to TrueStudio and IAR, unfortunately they don't support stm32l010...So, I want to know, does anyone had already used stm32l010, which IDE you used?

​Hi everyone)I've attached project, that I refer further.I'm trying to write program on my STM32F103(C8T6)."From scratch" I've made CubeMX project, set all needed pins in modes I need to, generated it.I've tried to flash a led on a couple of ports, it's ok.So, next thing, I've converted project to C++, and this is part, when all the fun begins.I've added function "my_main" to my_main.cpp file, used it from main.c, it worked, but when I tried to call some function from my_main() (HAL_Delay, or one of my class methods), I keep getting errors like "ld.exe: region `FLASH' overflowed by 17904 bytes", it can be caused by "stm32f103_lcd_board.elf section `.text' will not fit in region `FLASH'" or for example '.ARM' might not fit too (I've seen it on a project, that I used previously).I can't understand, what's wrong, since earlier I've done projects like this with no trouble at all.So, if someone have a clue, or can check attached project, I'll be grateful)

I'm designing the interface board for post-SMT in circuit programming / functional testing of a product with this MCU. I'm trying to decide whether to embed an SWD programmer for flashing or not.I've looked through all the system bootloader related docs and it's still unclear to me whether low-pin count packages that don't have a BOOT1 pin can still enter DFU via external signal control. Does anyone know?Thanks.