'L4 Cube - clearing OTG_GINTSTS bits

waclawek.jan · ‎2016-06-15

Posted on June 15, 2016 at 17:31

According to RM0351 Rev.4, all OTG_GINTSTS (interrupt status register) bits are rc_w1 (except those which are read-only or reserved). However, the macro supposed to be used for clearing these bits in [STM32Cube_FW_L4_V1.5.0]\Drivers\STM32L4xx_HAL_Driver\Inc\stm32l4xx_hal_pcd.h goes:

#define __HAL_PCD_CLEAR_FLAG(__HANDLE__, __INTERRUPT__) (((__HANDLE__)->Instance->GINTSTS) &= (__INTERRUPT__))

Not a hard bug, but IMO the RMW is redundant.

Am I overlooking something?

JW

waclawek.jan · ‎2017-06-02

Posted on June 02, 2017 at 11:06

Any news?

Meantime, things got worse. I am mostly interested in answer on question nr.4 the mysterious bits in DOEPINT.

Comparing old and new (v1.8) CubeL4:

And of course, not a iota of the Core ID register, or bits 5 and 15 in DOEPINT, in RM0351, as of now rev.5.

Can please this be resolved in less than a few years?

Thanks,

Jan Waclawek

Amel NASRI · ‎2017-06-02

Posted on June 02, 2017 at 16:23

Fixed in RM0351 Rev5
Reported for other remaining reference manuals

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Amel NASRI · ‎2017-06-02

Posted on June 02, 2017 at 16:43

Alreadu updated:

INEPNE is â€œrâ€� (read only), B2BSETUP is â€œrc_w1â€�.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Amel NASRI · ‎2017-06-02

Posted on June 02, 2017 at 16:45

Bits 5 and 15 of DOEPINT shouldn't be reserved ==> to be confirmed and description of bits will be provided soon

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Amel NASRI · ‎2017-06-06

Posted on June 06, 2017 at 14:23

Issue fixed since the version 1.0 of STM32CubeF4 package adding this call:

/* Get hclk frequency value */
 hclk = HAL_RCC_GetHCLKFreq();�?�?

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Amel NASRI · ‎2017-06-06

Posted on June 06, 2017 at 14:58

This error is already tracked internally, but it seems fix not yet applied. I will check this.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Amel NASRI · ‎2017-06-06

Posted on June 06, 2017 at 15:17

The context seems to be missing, as if there is a post lost in this discussion.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

waclawek.jan · ‎2017-06-06

Posted on June 06, 2017 at 15:43

In attachment the saved content of this thread from the old forum in MHTML format, together with Tsuneo's post.

Jan

________________

Attachments :

Forum - 'L4 Cube - clearing OTG_GINTSTS bits - STMicroelectronics.mht : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HycU&d=%2Fa%2F0X0000000bAA%2FdzUVxWWkDMfySkGWbYO6Qwl7_sYoRA4zIRRXWJ1ATnk&asPdf=false

waclawek.jan · ‎2017-06-06

Posted on June 06, 2017 at 15:52

And the post from

to_deletest

mentioned in my post previous to Tsuneo's

.

Jan

Amel NASRI · ‎2017-06-07

Posted on June 07, 2017 at 11:24

Thanks Jan.

That's strange how post got lost.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.