Solved

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.

Posted on April 13, 2018 at 01:22Hi,I recently bought the following development boards : - NUCLEO-L476RG- X-NUCLEO-IDW04A1 (Wifi expansion board)I am also using the following software packages: - STM32Cube_FW_L4_V1.11.0- STM32CubeExpansion_WIFI1_V3.1.1- System workbench for STM32 (SW4STM32)- I believe I have the latest ST-LINK driver : V2.J30.M20The NUCLEO-L476RG works great. I have programmed it with a few different projects from the package and everything works fine. The problem I have is when I try using the WiFi expansion board. I have tried all the examples that come with the package (Client, Server, Http request, WiFi_VCOM). I have had no luck with all of these. The WiFi expansion board just doesn't seem to do anything. I get stuck during the Wifi initialize process (see figure 1).I am assuming the Wifi expansion board is not flashed properly. So, I tried to flash it using the STM procedure :X-NUCLEO-IDW0xx1- FW upgrading over UART_v1.2. I already have a problem during

Hello all, We are working on STM32F429 Discovery board. Following are the steps we followed to create a project in TrueStudio using CubeMX and TouchGFXCreate a project in CubeMX by defining STM32F429 Discovery board .Do the configuration in GRAPHICS as shown in the screenshot as an attachment herewithGenerate the codeOpen TouchGFX project throuch "Execute" button on the same screenAdd a simple image in TouchGFXGenerate the code in TouchGFXAgain open CubeMX and generate the code in TrueStudioCompile the project created in TrueStudio containing CubeMX with UI created in TouchGFXBut this results in compilation and linking errors as shown in below screenshots Please help me with the solution to above errorsUPDATE:One more change I did in testing today.Create a CubeMX project with GRAPHICS enabledGenerate the code and compile it in TrueSTUDIO without any touchGFX interface attached to it.RESULT: Same compilation errors as aboveThere are no compilation/linking errors without GRAPHICS en

Hi guysI am bringing up a small test board containing a STM32F042 MCU with just several connections.I have exported code from CubeMX5 and imported into Eclipse. I am trying to debug the board with j-link but according to debugger code loops infinitely somewhere from 0x1fff c6e0 to 0x1fff c9f0. The code never stops unless I suspend it and that is where the debugger always land with message: Break at address "0x1fffc6e0" with no debug information available, or outside of program code. Im not sure is this the startup code. Below are the images showing how is the MCU connected and the clock setup. When I first connected the board it seemed to be working and entered the main() but but I had to reset the j-link on every start. Now I cannot get it to work even with completely freshly generated project from CubeMX. Debugger always lands in that part of code. I pasted relevant part of my schematic and the clock configuration diagram below.Does anyone has any idea how to debug this?

S2-LP transceiver, STEVAL-FKI868V1: it has a feature 'Automatic acknowledgement, retransmission, and timeout protocol engine".1. Does the acknowledgement automatically come from receiver?2. Does this feature automatic for S2-LP transceiver or it may be enabled/disabled programmatically?3. If I want to use a few receivers, is it possible to disable this feature or enable it only for one receiver, which is placed on the longest distance?

Hi,So the way the USB class drivers are implemented is that USBD_ClassName_Setup for a SET_CURRENT request will call USBD_CtlPrepareRx to receive the SET_CURRENT data payload and then the request will be processed from the USBD_ClassName_EP0_RxReady function.The problem I am having is that it seems that after one such SET_CURRENT request, no more setup packets are received. Its as if USBD_LL_PrepareReceive should be called from the USBD_ClassName_EP0_RxReady so that future setup packets can be received, however, the examples from STM32CubeMX don't do this.1) If I was to try calling USBD_LL_PrepareReceive or similar from EP0_RxReady, what parameters? Does this sound like the problem or am I on the wrong track? Its hard to believe that something so obvious would have been overlooked

Hi,I want to  configure the DMA so that it transfers data from the GPIO lines (8 bit data lines) to the RAM buffer upon receiving a trigger signal on the timer capture input channel TIM1_CHI (PE9) . I am using stm32f446ze.We nees to acquire data register on rising edge of clock.''https://www.st.com/content/ccc/resource/technical/document/application_note/7a/88/df/e3/d3/36/40/29/DM00169730.pdf/files/DM00169730.pdf/jcr:content/translations/en.DM00169730.pdf''Based on above datasheet ( 1.2.1 Data reception (using DMA) ) , configurations made are as followsvoid DMA_Init(){ /* TIM1_CH1 : Stream 6 Channel 0 */ RCC->AHB1ENR |= RCC_AHB1ENR_DMA2EN; DMA2_Stream6->CR &= ~DMA_SxCR_EN; DMA2_Stream6->CR &= ~DMA_SxCR_CHSEL;       // Channel 0 selected  DMA2_Stream6->CR |= DMA_SxCR_MINC | DMA_SxCR_PL_1 | DMA_SxCR_CIRC | DMA_SxCR_TCIE;                  &n

Hi all,I am currently learning how to interface with a USB using an stm32f2 as a host.I am using the fatfs library and it is working quite well.I have a question relating how removing a USB from the system. Similar to Windows for example, they have an "eject" button so you can safely remove a USB.Is there a way to do this on an STM32 system so I don't corrupt the USB or is it not necessary?Currently I mount the drive, open a file and write to it, then close the file and unmount. Is there anything I should do after this prior to removing the USB?I have been testing this on the Nucleo F207ZG.Thanks for you help!

Hi,I'd be grateful for any suggestion what BT module supporting HID I should use to connect BT HID keyboard to the STM32. I see that many popular HC-XX modules support only SPP profile.There are some modules supporting HID profile but all the examples I found focus only on using them to implement the HID device (not to terminate the connection from the device).What I want to achieve:BT_HID_KB-------------------------------BT_HID_Host_Module------STM32So the BT_HID_Module I am looking for is supposed to have BT Host functionality.Thanks,Bogdan

Hello,I have a problem with I2C eeprom 24LC16b and also with 24LC65. Altough the internal buffer is 16 bytes I can sent at once only 15 bytes (14 characters + 1 null char) and the same is aslo for 24LC65 (Instead of 64 I can store only 63 chars at once = 62 chars + 1 null char). I use HAL drivers. All the initialization code is created by CubeMX. I tried with internall pull ups and also with external 4.7K pul-ups.Bellow is a snippet from my code inside main function.Bellow is also a screenshot from my serial (UART) program, where you can see results readed from my EEPROM 24LC16b when I store "12345678901234", "123456789012345", "1234567890123456". "12345678901234567", "123456789012345678", "1234567890123456789" respectively. We can see that when the length of the string is greater than 16 chars remaining characters go to the begining of the EEPROM buffer. That seems OK but where does go character 16 (second output bellow) - buffer is 16 bytes long)!? When I used 24LC65 the same occours