Skip to main content

Watch out for an out-of-date STM32 Standard Peripheral library

ST has newer versions of the STM32 standard peripheral library that aren't being released. If you search on the website you'll find v3.5.0, dated as released 11-March-2011. But, if you download the STM32 USB-FS_Device driver package you can see that this includes a much newer STM32 standard peripheral library, v3.6.1 dated 05-March-2012.

There are some quite important fixes between v3.5.0 and v3.6.1:


V3.6.1 / 05-March-2012
Main Changes

  • All source files: license disclaimer text update and add link to the License file on ST Internet.

V3.6.0 / 27-January-2012
Main Changes

  • All source files: update disclaimer to add reference to the new license agreement
  • stm32f10x_sdio.c
    • SDIO_SetPowerState() function: fix POWER register configuration, only one access (for read or write) is allowed
  • stm32f10x_usart.h/.c
    • Update procedure to check on overrun error interrupt pending bit, defines for the following flag are added:
    • USART_IT_ORE_RX: this flag is set if overrun error interrupt occurs and RXNEIE bit is set
    • USART_IT_ORE_ER: this flag is set if overrun error interrupt occurs and EIE bit is set
  • Remove IS_USART_PERIPH_FLAG macro (not used)
  • stm32f10x_rtc.c
    • Update RTC_GetCounter() function to fix issue when reading the RTC counter registers (CNTL & CNTH registers) and the counter rolls over
    • stm32f10x_flash.c
  • Flash keys moved from to stm32f10x.h file
  • stm32f10x_tim.c
    • TIM_UpdateRequestConfig(): correct function header's comment 
  • stm32f10x_exti.h
    • EXTI_InitTypeDef structure : for “EXTI_Trigger“ member, change “@ref EXTIMode_TypeDef”  by  “@ref EXTITrigger_TypeDef”
It would be nice if ST could release the latest STM32 peripheral library as a standalone package. I'm tempted to put up a github of the v3.6.1 library. The license appears to allow for that...

Comments

Popular posts from this blog

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...

Travelling on Spirit airlines out of Boston Logan airport? Here are some tips.

I attended CES 2017 in Las Vegas. Booking the trip late I ended up on Spirit airlines. It was both non-stop, making it six hours to Las Vegas from Boston, and affordable, less than $300 for a one way trip compared to around $700 with JetBlue. Here are some tips that might help you when travelling on Spirit from Boston Logan airport. Eat Spirit is located in the B-terminal, gates B-37 and 38, with its own TSA security checkpoint. While it does have restrooms and places to sit the food selection is limited to a single food stand. I'd recommend eating at the Legal C Bar (number 77 in the image below) prior to going through the terminal security checkpoint. The food and service there were great. Drink The water and other drinks are cheaper if you buy them at the food cart rather than on the flight. Seats The seats on Spirit don't recline. They do this to reduce weight, seat cost, seat maintenance costs, and so seats don't impact the free space of other passengers,...

Yocto recipe SRC_URI for a BitBucket / GitHub ssh git repository

This is a particularly geeky post but because Google searches didn't turn up any information I thought it would be helpful to document the issue and solution for others. I was writing  Yocto recipes that pulled from BitBucket git repositories in ssh form and ran into several issues getting a SRC_URI that worked. GitHub uses the same syntax for their ssh repositories. A BitBucket / GitHub git url, in ssh form, looks like: < username >@bitbucket.org:< account name >/< repository name >.git a more concrete example for a git repository in one of my BitBucket accounts looks like: git@bitbucket.org:cmorgan/somerepository.git Yocto recipes can pull from git repositories by setting the SRC_URI variable appropriately. Unfortunately you can't just do: SRC_URI = "git@bitbucket.org:cmorgan/somerepository.git You'll get errors because the Yocto won't know what kind of url this is. You need to specify the protocol for Yocto to k...