cancel
Showing results for 
Search instead for 
Did you mean: 

STM32L162

David Guzuman
Associate II
Posted on January 24, 2018 at 20:29

Hi,

What is a start point for using STM32L162?

17 REPLIES 17
Posted on January 25, 2018 at 08:09

Do you have custom board? I cannot see any from the Disco/Nucleo collection.

Download STM32CubeMX, think about IDE you want to use for the development.

Depending the background you have (C, ARM or 8 bits) there are many ways to follow....

Andrew Neil
Chief II
Posted on January 25, 2018 at 10:00

Prerequisites - any microcontroller:

  • A good understanding of 'C' programming in an embedded microcontroller context
  • A basic understanding of electronics, including ability to read & understand schematics (circuit diagrams)
  • The ability to think logically, analyse a problem, and devise a solution
  • Google

For a particular chip, you will need:

  • A suitable toolchain & IDE
  • A development board

    I strongly suggest that you get a genuine ST board (Nucleos are cheap) - that will come with full documentation and support, and ready-to-go examples
  • Study the device datasheet
  • Study the device User Manual
  • Browse the Product Page on the website - look at the Application Notes and other support available

ST have a load of training & tutorial stuff on the web, including YouTube

http://www.st.com/content/st_com/en/support/learning/mcu-training-courses.html

 

http://www.st.com/content/st_com/en/support/learning/video-page.html?page=13

 

https://www.youtube.com/playlist?list=PLnMKNibPkDnF97QnUOFGirl1q0G_4VdDc

 

https://www.youtube.com/user/STonlineMedia

 

EDIT

General microcontroller 'Getting Started' tips for beginners:

http://www.avrfreaks.net/comment/1138166#comment

 

http://www.avrfreaks.net/comment/2079906#comment

 
Posted on January 25, 2018 at 10:09

And a lot of free time if this is not a part of your job;)

Posted on January 25, 2018 at 10:21

Neil.Andrew wrote:

ST have a load of training & tutorial stuff on the web

And there is a vast amount of 3rd-party stuff.

in fact, I would venture to suggest that the STM32 is probably the most widely supported of all Cortex-M by 3rd-party stuff ... ?

eg

http://stm32f4-discovery.net/

http://www2.keil.com/mdk5/learn

You should certainly have a copy of Joseph Yiu's Definitive Guide to the Cortex-M3:

https://www.elsevier.com/books/the-definitive-guide-to-arm-cortex-m3-and-cortex-m4-processors/yiu/978-0-12-408082-9

https://wordery.com/jackets/e0f11161/m/97801240808jpg

Posted on January 25, 2018 at 10:26

Great book. But I think we spend substantial part of our job on peripherals setup which is not described thoroughly here because it depend on actual vendor.

Posted on January 25, 2018 at 16:30

>>

Hi, What is a start point for using STM32L162?

Would rather depend on where you're coming from. Some context might be helpful, and your profile is empty.

A STM32L152-DISCO or EVAL board might provide a way to get up to speed on the L1 series. Really depends on what you're attempting to do, and the experiences you're working off.

Tips, buy me a coffee, or three.. PayPal Venmo Up vote any posts that you find helpful, it shows what's working..
Posted on January 25, 2018 at 16:27

+1 on Joseph Yiu's books, complement ARM's TRM with an alternate perspective.

Evidence suggests a lot of users here have minimal knowledge about how micro-controllers work, or how data is represented in memory, helps to build your house on a solid foundation.

Tips, buy me a coffee, or three.. PayPal Venmo Up vote any posts that you find helpful, it shows what's working..
Posted on January 25, 2018 at 16:35

And critical thinking / troubleshooting skills are important. + Patience.

If someone wants quick results without pain should use the arduino + copy&paste replication approach. It's nice to help someone who is involved, not waiting for a solution. But we touch the Motivation here....

Posted on January 25, 2018 at 16:38

Bogdan Golab wrote:

 we spend substantial part of our job on peripherals setup which is not described thoroughly here because it depend on actual vendor.

Yes, that is true.

This book describes the generic Core features - it needs to be used in conjunction with the specific ST documentation & resources mentioned earlier.