RM0394 pdf issues

[Kraal]

Posted on February 13, 2018 at 11:35

Hi, just nitpicking here but still...

The RM0394 (reference manual for STM32L4xxx) has a bad table of content, the entries go like this: 1, 2, 3, 4, 5, then restart 1, 2, 3, 4, 5, 6, 7, 8, then finally 1 2 3 ... as it should.

[waclawek.jan · Accepted solution]

Posted on February 13, 2018 at 12:05

Hey! I am

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

around here!

;)

Jan

[Kraal]

Posted on February 13, 2018 at 12:18

Thanks for the badge Jan !

I know that you like to point out inconsistencies across ST's documents, I just did not see that you already submitted this issue here.

[Khouloud GARSI]

Posted on February 14, 2018 at 16:25

Hello,

This documentation issue has been reported internally and will be fixed on the next release of the reference manual.

Thank you both for bringing this to our attention.

Khouloud.

[Khouloud GARSI]

Hello,

The table of contents is updated in the last published version of the reference manual.

Thanks again!

Link:

https://www.st.com/content/ccc/resource/technical/document/reference_manual/group0/b0/ac/3e/8f/6d/21/47/af/DM00151940/files/DM00151940.pdf/jcr:content/translations/en.DM00151940.pdf

Khouloud.

[waclawek.jan]

Thank you for letting us know.

JW

[Khouloud GARSI]

You're always welcome Jan !

Khouloud.

[Kraal]

2 years already !

Another issue with RM0394, this time regarding the LSE bypass functionality.

On page 185, chapter 6.2.6, the bits to be selected to enable the LSE bypass mode are stipulated to be in the register RCC_AHB1SMENR while in reality it is in the register RCC_BDCR. I believe it is an hyperlink mismatch.

Then on page 239, the explanation for the bit LSEBYP says : "Set and cleared by software to bypass oscillator in debug mode". I don't understand what is has to do with debug mode ? I believe it is a copy paste error, isn't it ?

Best regards,

Kraal

On a side note, I believe that if the documentation could also be on github and that the community could propose fix for such small errors, the documentation would become error free faster than what it is now.

Also we, engineers, would have a single place to look for the latest revision of said documentation (and execute a single fetch instead of going through all ST's website with all the unnecessary clicks in between).