Solved

Posted on May 02, 2017 at 23:46SPC560B40x how to get the programmers reference or what ever they call the long form documentation for these chips. This is not the power arch manual but the how to use the CAN controller ADC ect?

Posted on February 23, 2017 at 11:49We are using the NFC03A1 board with Nucleo F103RB.In the function :int8_t PCD_ProtocolSelect(const uint8_t Length,const uint8_t Protocol,const uint8_t *Parameters,uint8_t *pResponse)There is a buffer DataToSend[SELECT_BUFFER_SIZE] where SELECT_BUFFER_SIZE  is 6.Then we fit the buffer with datas depending on the Lenght argument... until '3 + Length - 1'In the function : ISO14443A_ConfigFDTforAnticollision(), we can read :if( IcVers >= QJE)   NbParam = 6; else   NbParam = 4; status = PCD_ProtocolSelect((NbParam+1),PCD_PROTOCOL_ISO14443A,ProtocolSelectParameters,pDataRead);... and we got a buffer overflow!We solved the problem with :&sharpdefine SELECT_BUFFER_SIZE 10#nfc03a1

Posted on April 21, 2017 at 21:39 Hi, I am trying to configure the SPI moduleon the SPC570S40E1 microcontroller to communicate with an external device. The devicerequiresmessage length of 40 bits.I would like to know if I am setting up the function for exchanging data correctly. The issue I am seeing currently is right after pushing theset of frames( 16,16, 8 bits) to transfer the second message,the EOQFand the TXRXs bits in the status registers remain set even after clearing the EOQF bit. You can see the the second time I am calling the Transmit_DSPI0 in the DSPI_0_Exchange function in the code below. Here is the source code. // SPI driver #include 'SPI.h' #include 'STM.h' void Initialize_DSPI0(void) { // Configure DSPI0 Module Configuration Register ( DSPI0_MCR ) // MSTR - 1 , Master mode // CONT_SCKE - 0 , Continuous SCK disabled // DCONF - 00 , SPI // FRZ - 0 , Do not halt serial transfers in debug mode // MTFE - 0 , Modified Timing Format disabled // ROOE - 0 ,

Posted on April 26, 2017 at 10:37The 'SPC560Bxx OSAL Component RLA' 1.0.201704140929 doesn't work with C++ since the extern 'C'-block isn't closed in osal.h and systimer.h#spc5studio #c++

Posted on April 29, 2017 at 15:26Hi,I connect to the SPWF01 via IPv4 and a port forwarding in my router. It works fine, as long I have a IPv4 router / internet connection. When I have a IPv6 connection and DS-Lite it doesn't work. So, is there a possibility to update the SPWF01 for IPv6?Best regards,Florian

Posted on March 27, 2017 at 18:35Hello All,I had been using stm32CubeMX v4.08 with w/wo freeRtos on stm32F103CB series mcu successfully , until recently when i upgraded cubeMx to version 4.20. I am totally stuck since then, since i have so got used to using HAL abstraction...Calling systemClockConfig() in main() .. causes HAL_Timeout - causing function Error_Handler to be called in the following line..if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)  {    Error_Handler();  }on commenting out/* Configure the system clock *///  SystemClock_Config(); ..or..//Error_Handler();the cpu runs but presumably on the systemInit()'s reset default HSI clock..I assume its a bug in hal_rcc drivers...Can you please suggest some way to get out of this....RegardsAnish.

Posted on April 28, 2017 at 01:42Hi, I'm writing an application on an STM32L052 that uses the UART (115200-N81), and I need to use the Bootloader for code upgrades.   If run the Bootloader using the BOOT0 pin, the UART initializes fine and I can upload code at any baud.   However if I jump to the Bootloader code from my application, the Bootloader isn't initializing the UART correctly, and I get framing-errors transmitted out from the CPU.   From the scope traces (good and bad are attached), I can see that at any baud rate (115200-E81 shown), the Tx signal is switched to '0' between each byte instead of staying high, this causes a framing error.   It almost seems as though the stop-bit is missing or inverted.    I'm guessing that in my application's use of the serial port, something is left in a register somewhere that doesn't get initialized in the Bootloader code.   Since I cannot modify the Bootloader code, I need to

Posted on April 27, 2017 at 14:46Hi everyone,I turn to you in complete despair. I thought I would start tonight with My Nucleo, but couldn't even get past the Installation of the CubeMX software. When I double click on the app (SetupSTM32CubeMX-4.20.1) or open it via left click and open, I get the message: â€œSetupSTM32CubeMX-4.20.1â€� is an application downloaded from the Internet. Are you sure you want to open it?'as usual. But after clicking on open, nothing happens. I also tried to execute it via terminal as suggested by another post, but get:Jean-Marcs-MacBook-Pro-2:A Joeme$ java -jar SetupSTM32CubeMX-4.20.1.appInvalid or corrupt jarfile SetupSTM32CubeMX-4.20.1.appDoes someone know how to solve this? Thank you in advance!

Posted on March 14, 2017 at 08:18I think the new issue seems to have a problem with source generation.When choosing the HSE, create the source as follows :  RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;To operate normally, the source must be changed as follows :  RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE;check, please.

Posted on March 22, 2017 at 23:04When I generate code for STM32L151CBTx (FW v1.6.0) using CubeMX it enables MCI clock (RCC_ORCILLATORTYPE_MSI) in SystemClock_Config even if only HSI is enabled in the CubeMX clock configuration UI. Similar problem does not exist for other chip versions e.g. L152CBTx.This misconfiguration causes HAL_RCC_OscConfig to fail.#cubemx-bug

Posted on March 16, 2017 at 10:47 Hi, I found a bug in the new version of CubeMX. In this case, even if HSI is not used it is enabled (line 1) but not activated: RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE |RCC_OSCILLATORTYPE_LSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; RCC_OscInitStruct.LSEState = RCC_LSE_ON; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_NONE; if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK) { Error_Handler(); }�?�?�?�?�?�?�?�?�? thus causing HAL_RCC_OscConfig() to fail. I attached .ioc file. BR, Andrea #bug #cube #clock

Posted on March 11, 2017 at 06:05I migrate my stm32f103ve project from 4.19 to 4.20. but after migrate my project dosen't work.

Posted on March 27, 2017 at 01:42Possible bug in CubeMX 4.20.0?Using Nucleo 303ZE board, and Atollic 7.1.1Build dead simple default project, except in RCC, set High Speed Clock to 'BYPASS Clock Source', and select HSE as input to PLL.In main.c you'll have this routine:void SystemClock_Config(void){RCC_OscInitTypeDef RCC_OscInitStruct; RCC_ClkInitTypeDef RCC_ClkInitStruct;/**Initializes the CPU, AHB and APB busses clocks */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE; RCC_OscInitStruct.HSEState = RCC_HSE_BYPASS; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE; RCC_OscInitStruct.PLL.PLLMUL = RCC_PLL_MUL2; RCC_OscInitStruct.PLL.PREDIV = RCC_PREDIV_DIV1; if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK) { Error_Handler(); },,, etc,Results in bad return from HAL_RCC_OscConfig() and call to Error_Handler().If you change this line:RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OS

Posted on March 13, 2017 at 15:52 1. Faulty code generation STMCube Generates to following code in the function: void SystemClock_Config(void) RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;�? this results that the SystemClock_Config function always enters the Error_Handler HSE Clock is used as main clock. By removing the RCC_OSCILATORTYPE_HSI define code functions normally 2. Non working code USB MSC Code generated for USB MSC stops working after the usb command USB Set Configuration Request Device Manager reports Error Code 10 (can't start device) The usb analyzer tool of wireshark shows no communication after host sends Set Configuration Request. Problem observed from at least STM32CubeMX V4.18+ Changing driver versions does not solve the isuue Tested on STM32446e-Eval and STM23F446ZC PC: Windows 10 Toolchain: KEIL µVsion V5 #stm32cube-bug #bug-stm32cubemx

Posted on April 03, 2017 at 18:07Hey, I just updated my version of STM32CubeMX to 4.20 and now when I generate a project for the STM32F401VCTX using only the RCC-> HSE (A crystal not the internal clock) it gets stuck in SystemClock_Cofig(void). I was able to find that the issue was because for some reason the new cubeMX now uses:    RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSE;instead of:    RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE;even though only the HSE clock is used. For this reason it gets stuck in the Error Handler. This problem was not there in the previous versions of cube. Please look into this and fix this issue.Thank you#stmcubemx-4.20 #hse #rcc #hsi

Posted on April 25, 2017 at 12:21 I have the following structs (from a library I'm using) with some fields and I would like to assign with OR operation a new value. But I'm debugging and I can't see how anything is writing there: typedef struct { TIM_TypeDef *Instance; /*!< Register base address */ TIM_Base_InitTypeDef Init; /*!< TIM Time Base required parameters */ HAL_TIM_ActiveChannel Channel; /*!< Active channel */ DMA_HandleTypeDef *hdma[7]; /*!< DMA Handlers array This array is accessed by a @ref DMA_Handle_index */ HAL_LockTypeDef Lock; /*!< Locking object */ __IO HAL_TIM_StateTypeDef State; /*!< TIM operation state */ }TIM_HandleTypeDef; typedef struct { __IO uint32_t CR1; /*!< TIM control register 1, Address offset: 0x00 */ __IO uint32_t CR2; /*!< TIM control register 2, Address offset: 0x04 */ __IO uint32_t SMCR; /*!< TIM slave mode control register, Address offset: 0x08 */ __IO uint32_t DIER; /*!< TIM DMA/interrupt enable register,

Posted on April 25, 2017 at 09:42I configured TIM7 as time base timer using HAL_TIM libs as indicated in this post: https://community.st.com/0D50X00009XkYJ6SANAt interruption callback I increase a counter var in order to get multiples of 100us timings for different tasks. But first I started trying and testing with toggle led every 500ms (I know is a low freq but i need to see it with my eyes). The fact is that when app runs in debug mode, it seems to start correctly: every 100 counts of cnt register one interruption is activated and counter increases unity. This ocurres until counter reaches once 11 or 12, but the number of the last attended interruption is about 12. After this, cnt counter runs and restarts correctly. But no interruption is activated, thread didn't pass to the irqhandler neither elapsedtimeinterruption callback.Which could be the cause of this behavior?Could be the cause on HAL library that is disabling updates or interruptions? 

Posted on April 24, 2017 at 17:15I was trying to get Simulink to communicate to a sensor using SPI, but I encountered the following issue:When opening the parameter screen of the SPI block by double clicking on it, the ''Type_SPI'' field contains ''No_Configuration_Type'' instead of ''Full_duplex''. This does not happen with any of the three other modes for this field (Half_Duplex, Receive_Only and Transmit_Only).Due to this bug it is not possible to configure the SPI peripheral as full duplex.This happens in all SPI ports.This specifically has to do with the ''SPI1.Direction=SPI_DIRECTION_1LINE'' rule of the .ioc file.If this value is set to SPI_DIRECTION_2LINES (as required for full duplex config), simulink will parse it as any other invalid value. The SPI_DIRECTION_1LINE value will be parsed correctly as half duplex.This seems like a bug in the processing of the .ioc file, any ideas? Application versions:Matlab r2016b (with all the required toolboxes)STM32CubeMX 4.20.1 with STM32F4

Posted on April 26, 2017 at 04:42I using STM32CubeMx generate code for STM32F412 USB CDC mode, but it's not work. However, I using STM32F072 MCU that it's work now.Could anyone tell me what happened? 

Posted on April 12, 2017 at 20:48Hi,I have noticed that it is not possible to have multiple ACI_GATT_WRITE_CHAR_VALUE per connection event.I have set up the following connection: connection interval of 40ms and connection event length of 21.875ms (the maximum I can while continuing to advertise in parallel).Using a sniffing tool, I see that what is happening is the following:- Master -> Slave : Write Request- Wait for 40ms (next connection interval)- Slave -> Master : Write Response- Wait for 40ms (next connection interval)- Master -> Slave : Write Request- etc.Is that a normal behavior? Why isn't it possible to have the Write response inside the same connection event, and more write reqests?Note that if I use ACI_GATT_WRITE_WITHOUT_RESP (Write command), I don't face the issue, and it's possible to send multiple ones inside the same connection event (around every 700us)Thanks for your help.Christian#bluenrg-ms

Posted on April 26, 2017 at 16:18Hi all,I found my call HAL_UART_Receive() doesn't timeout.  Do you have any suggestion what I forget configure?In CubeMX, I add uart2 and tim2 and I add my timer callback as this./* USER CODE BEGIN 4 */void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim){ sprintf(aTxBuffer,'\r\nSTM32CubeMX rocks %d times \t', ++nbtime); HAL_UART_Transmit(&huart2,(uint8_t *) aTxBuffer, strlen(aTxBuffer), 5000); //printf('input:\r\n'); HAL_UART_Receive(&huart2,(uint8_t *) aRxBuffer, 10, 500); HAL_UART_Transmit(&huart2,(uint8_t *) ack, 11, 5000);}/* USER CODE END 4 */If I input 10 characters, the code works well.  However, if I don't input any thing,  HAL_UART_Receive() will not return. I believe it should return in 5000 ms. Do you have any idea about this?PS: I'm using STM32L072. #hal_uart_receive() #uart

Posted on April 26, 2017 at 12:22[STM32Cube_FW_F4_V1.15.0]\Drivers\CMSIS\Device\ST\STM32F4xx\Include\stm32f4*.h:#define USART_CR1_TXEIE               USART_CR1_TXEIE_Msk                      /*!<PE Interrupt Enable                    */The comment is misleading (I know, copy/paste error).JW

Posted on April 11, 2017 at 11:42Hi There , We are currently working on a project using an EEPROM to store sporadic data. The eeprom is a 24AA512 with 512kbits memory, from Microchip.We use it to store datalogging data from our application. The problem is that we sometimes also need to store only 3-4 bytes data and that this eeprom does page or byte write operations identically, meanning that a full page of 128bytes is refreshed even if I choose to write only one byte in a page area, reducing the endurance of the full page of one cycle everytime. This might cause a problem in our application.Could anybody tell me if that is the case too in chips of ST , as the M24512 or M95512 for example? does every single byte write means that the full page has to be refreshed? That point doesn't seem to be clearly defined in the datasheet...thanks in advance for any help.Eric#endurance #byte-write #page-write #eeprom

Posted on April 21, 2017 at 09:35I have generated a project for an STM32F103C8T6 using CubeMX 4.20.1.I am using i with the 1.4.0 of the STM32CubeF1 library.I am using the unmodified generated code to send out data in the main loop.The CubeMX configuration is the following for the pins:I2C on PB-7 SPI on the PB3-5 (MISO is unused). The generated GPIO initialization code looks ok for me.If the I2C1 module is enabled there is not any output on the MOSI line even if sending non 0xFF data:I have narrowed down the source problem to the __HAL_RCC_I2C1_CLK_ENABLE in the HAL_I2C_MspInit.If I remove that the MOSI output will work as expected. (Of course in this way the I2C peripherial will not work):I have already checked the errata, but have not found any relevant. The generated codes seems to do what they supposed to, but I am not really sure where to look for the problem source.Any help would be deeply appreciated!#spi #cube-mx #stm32 #i2c #stm32f103

Posted on April 26, 2017 at 10:44   Hi,I am newbie in System Workshop for STM32. I tried write simple example - LED blink. It works fine.  Now I want to test the same program, but with a timer interrupt.  In file ''stm32f4xx_hal_conf.h''  I enable HAL_TIM_MODULE    #define HAL_TIM_MODULE_ENABLED  It appeared errors:      in file ''stm32f4xx_hal_tim.h''   in file: stm32f407xx.h  I use STM32F407-Discovery board. I use HAL_Driver ver 1.7.1.  What is wrong ?  Pekub