[STM32F2] issue with CAN-HAL interrupt receivng

[christoph2399]

Posted on August 30, 2016 at 09:43

based on stm32cubemx with library 1.4.0 for stm32f205

with interrupt receiving  the fifonumber within the struct 

CanRxMsgTypeDef

is not set by the function

CAN_Receive_IT()

in

 stm32f2xx_hal_can.c

if the user/application does not care about the fifo it makes no big deal.patch  for  stm32f2xx_hal_can.c

  * @version V1.1.3

  * @date    29-June-2016add following in stm32f2xx_hal_can.c @ line #1346

hcan->pRxMsg->FIFONumber = FIFONumber;

[Walid FTITI_O]

Posted on September 01, 2016 at 15:31

Hi d-chris,

Yes you are right. This already reported in this [DEAD LINK /public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Configure%20CAN%20to%20receive%20in%20both%20FIFOs&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B&currentviews=53]thread. I report it to be fixed.-Hannibal-

[valentin]

Posted on December 07, 2016 at 04:43

FTITI.Walid

‌:

Great, thanks. I was just about to report this again for the F2 series.

I reported the same issue for the F3 library a while ago and thought it would be fixed by now.

https://community.st.com/0D50X00009XkeqISAR

Can you please make sure this gets fixed for all mcu series?

Thanks!

[Tesla DeLorean]

Posted on December 07, 2016 at 07:04

There seem to be a crate load of these DEAD LINK markers, how should we go about fixing and identifying these?

[Walid FTITI_O]

Posted on December 07, 2016 at 09:53

Hi Clive, 

This deak link issue in the new platform is reported and it is under investigation.

-Walid F-

[Walid FTITI_O]

Posted on December 07, 2016 at 12:19

Hi

Roehrig.Valentin

,

I confirm that the same issue exist in this 1.4.0 Cube version/ 1.1.3 driver version. I report it to be fixed in the next version .

Thanks for the contribution.

-Walid F-