Solved

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

Hello, I'm using the STM32746G Discovery Board to familiarize myself with the ST environment. Now I simply wanted to store a 32Bit value in the RAM, and had several problems with the Cube BSP drivers. I tested the functions with the following code: #define SDRAM_OFFSET ((uint32_t)0xC0100000)   for(uint32_t i=0; i<0x10010; i++){ BSP_SDRAM_WriteData(SDRAM_OFFSET+i*4,(uint32_t *)&i,1); } for(uint32_t i=0; i<0x10010; i++){ testarray[i]= 0; } for(uint32_t i=0; i<0x10010; i++){ if(SDRAM_OK != BSP_SDRAM_ReadData(SDRAM_OFFSET+i*4,(uint32_t *)(&testarray[i]),1)){ testarray[i] = 111111; } }In the debugger it then looks like this:Sometimes the transfer works. Sometimes the higher bits are incorrect.How do I use the function to make it work? Further I could not find out which SD-RAM area is used by the LCD driver. Which area can I overwrite without worrying about disturbing the display functions? Unfortunately I could not read this out of the code.

Dear all,I have a board with only the STM32F765VIT6 and I program through the stlink with a power supply of 3.3V (.At start of program i tried HAL_PWR_EnterSTANDBYMode() to get 3.5uA with success if before i disable overdrive with HAL_PWREx_DisableOverDrive()HAL_PWR_EnterSTOPMode(POR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFI) to get 200uA without success whatever i try to disable (Prefetch, overclocking mode with underdrive, voltage regulator)Like i have any connected pin, i did not configure pin to analog input like adviced in AN4749.I have got still 5mA, any default configuration help will be pleased.Thanks,

Hello,I wonder if I use the internal pullup resistor on an STM32F4 on an open-drain output, if the MCU is reset with the line NVIC_SystemReset(), does the internal pullup resistor with open drain output will still be seen by another IC connected to this pin ? Will it still be configured as open drain with pullup during and after reset ?Thank you

I receive some data from a terminal. Say I send 1234 on the terminal.I set a break point onvoid EP3_OUT_Callback(void){ packet_receive = 1; Receive_length = GetEPRxCount(ENDP3); PMAToUserBufferCopy((unsigned char*)Receive_Buffer, ENDP3_RXADDR, Receive_length);}But I see that every char copied on the first index of the buffer.I see Receive_Buffer[0] = 1Receive_Buffer[0] = 2Receive_Buffer[0] = 3Receive_Buffer[0] = 4Also in PMAToUserBufferCopy I see the first argument's address is incremented.What do I miss?

I am looking at the code here that has the algorithm for producing the device serial number reported when the MCU is in USB DFU mode.https://github.com/libopencm3/libopencm3/blob/master/lib/stm32/desig.cThe document they reference there, https://my.st.com/52d187b7, is now a dead link. Does anyone have the name of the document and its current location?

I am trying to initialize my external SRAM before the main loop runs. Using the STCubeMX it generated the code for me to have me FMC controller initialized after Hal_init() and Hal_GPIO_Init() in Main.c. However, I need the SRAM to be initialized before this. Doing some research I found that there is a SystemInit_ExtMemCtl() function inside System_init in STM32F4xx.c but I do not seem to have this function in the L4. Any guidance or example for doing this would be greatly appreciated!

Hello, we're using the microcontroller STM32F302C8 and we have a problem with the PLL.The problem is when we enables the PLL the microcontroller is reset. We have made several tests using HSI and HSE, but always the same result, a reset after to enable the PLL.If we use the Sysclock directly from HSI or HSE the microcontroller works fine.We check this with several boards and we're using the SDK 19.1 and 1.10.0 with both options HAL and LL.Does anyone know what the problem could be?Thanks & regards

How can i forward data which i received at my COM Port via USB FS to a UART of my Choice?I already send data to UART5 and i measured it with an osci and its workinghar buffer[] = "TEST"; HAL_UART_Transmit(&huart5, buffer, sizeof(buffer), HAL_MAX_DELAY);So How can i forward data from VCP received in a Terminal to any UART?

As of Monday 2019-01-14 my Atollic 9.1.0 IDE has stopped working with Microsoft Devops as the cloud repo. I use the Microsoft TEE Eclipse plugin from Github, latest version. It's worked very well for the last three months, uploads, downloads, etc. Atollic projects are mapped through workspaces to coresponding Devops project and repo.The TEE plugin in the Atollic IDE no longer connects to the cloud using access token, although I can login to Azure using the generated token from Eclipse/TEE. Does anyone else use this particular repo setup, and is their cloud connection still working? I suspect corporate IT has changed cloud settings regarding access tokens to authenticate to the Azure cloud. IRequests to the company devops admin are unanswered. I'm hoping some other STM32/Atollic/Devops user can confirm it's my problem and not something Microsoft or Eclipse related. Jack Peacock

I am using x-nucleo-nfc03a1 on the nucelo-f446re board and i can't figure out why i keep getting a NAK value of 04 when trying to use sendrecv function. cr95hf's is always response: 90 4 4 24 0 0.0A is defined in documentation as ACK and 00 as NAK and everything else falls under NAK, but i can't find any further specifications what might 04 or any other error mean.

Hey Guys,I have designed a custom board with the STM32F429ZIT6 which I programm with the STLink debugger together with TrueStudio. So far everything seems to work except that when I don't use a debugging session I have to manually make a reset on NRST pin or otherwise the processor will not start it's normal program execution. I have to do this every time power get's cycled.I have one 4,7uF cap for overall buffering and then 10nF and 100nF at each Vdd and an extra ferrite bead for the Vdda pin but with 1µF and 10nF as a decooupling. I did not implemnt a 100nF cap from NRST to ground for short ESD burst but I doubt that this is the cause for the problem since after the manual reset everything works fine. Do I maybe need a reliable power cycling with an external power supervisor chip doing the manual reset, or did I do something comepletely wrong?My controller runs with 3,3V.best regardsBenjamin

Good afternoon, I would like to share an issue I’m facing with a stm8s105c4.A feature of our main application is to calculate a CRC of the entire program in the flash. Unfortunately, when I read flash data from addresses close to the instruction in execution, the data read it isn’t always correct.I’ve been able to reproduce the issue in this small program: main() { unsigned char* p_address; unsigned char dataRead; volatile dbg;   /* Loop and read the registers*/ for (p_address = (unsigned char*)0x80ce; ((unsigned int)p_address) < 0x80FF; p_address++) { dataRead = *p_address; dbg++; } dataRead++; }In this case, when p_address points to 0x80dc, this is what we can observe in the dissasembly and the core registers:      1)      This set the address we want to read in X0x80d7 <main+9>            0x1E04       &nb

Solved: The problem was an improper reading, the BKSRAM-clock was not initialized when reading back the report. Updating with "correct" code for posterity.I'm writing a (better) hard-fault handler for my STM32f207zg and want to do the following:Have a horrible crashJump into my (C) fault handlerSave various registers (CFSR, HFSR, LR, PC, ...) in the backup SRAMResetWhen back in main(), check if the watchdog reset the systemFetch the "crash report" saved in the SRAMDump it on CAN1,2,4,5,7 is easy, but I'm having problems with saving/restoring from the SRAM.The hardfault-handler calls the function fault_bksram_init() after filling up the fault_crash_t structure with data. It then calls fault_write_crash() in order to write the "report" to the SRAM. I can see using my debugger that the data is actually written to the address defined in BKPSRAM_BASE; however, after doing a reset using the debugger the memory at BKPSRAM_BASE is wiped with&nb

PWM1 control has block address F8 but i have access only to first 252 bytes (area 1 and 2)63blocks. Response from reader "Statusbyte:...0x95 Reader: ISO-Error ISO-Error = 0x10

We are bringing up a new board and having troubles establishing SWD connection, I was reaching out seeking help with this.Target - STM32F091RCICSP - ST-Link/V2IDE - TrueSTUDIOThis is our first use of the ST-Link outside of Nucleo-64 board development and I was thinking it may be best to start there:Board - NUCLEO-F091RCWhen I hook the Nucleo-F091RC up to the external ST-Link/V2, I use the following wiring & apply 3.3V -Config:CN2 - Jumpers RemovedVdd - 3.3V (CN6.4) Board Wiring:Vdd - CN6.2Gnd - CN6.6SWDIO - CN7.13 (PA13)SWCLK - CN7.15 (PA14)SWO - CN10.31 (PB3)NRST - CN7.14ICSP Wiring:Vdd - p1Gnd - p4 SWDIO - p7SWCLK - p9SWO - p13NRST - p15When I launch an existing project that works using the onboard ST-Link it now reports "a problem occurred", see attached. What is the issue here?Hardware Setup: Error Message: Debugger Config:

Requirements:1)     Need all the HRTIM output pins (PC6, PC7, PC8, PA8, PA9, PA10, PA11, PA12, PG6 & PG7) for Power Supply design, where many are typically used for USB Full Speed serial OTG_FS_XXXX pins (PA9, PA10, PA11, PA12, PA4)…Are following Assumptions true, if No, why? (Details please)2)     Only possible way to retain USB port serial Full Speed operation (don’t want / need ULPI interface: design devoid of external High Speed PHY, as design will also need these pins mapped to alternate functions). Therefore, just use USB OTG_HS_XXXX pins (PB12, PB13, PB14, PB15, PA4), they will function identical to OTG_FS_XXXX pins above when uC in OTG_HS1 mode (RM0433 figure 746)?a.      The USB OTG_HS_XXXX pins may be used / connected to existing external Full Speed serial USB circuit (identical to OTG_FS_XXXX pins) and may be programmed to function properly at USB serial Full Speed?b.    &