[Dprglist] NUCLEO STM32 L476RG - need suggestion of development environment to use

[Thalanayar Muthukumar]

It is just my hypothesis Chris. 

Regards.
- Kumar

Sent from my iPhone

> On Oct 29, 2021, at 10:32 AM, Chris N <netterchris at gmail.com> wrote:
> 
> 
> Is that your hypothesis or are you saying it now works after you reversed this?
> 
> I still believe it's a case of PlatformIO unfortunately not fully supporting your board.  I'm actually having the same issue.  I have 4 different STM32 boards.  2 of them are Nucleo boards with built-in programmer/debugger and the other 2 are "blue pill" and "black pill" type boards, with a separate USB debug/program dongle.   The latter 2 work fine.  The Nucleo boards are not.   
> 
> I'm not sure if it's because of the differences in the MCU, or because of differences in the programmer (the nucleo boards incorporate ST-LINK V3, the external programmer is a V2...)
> 
> I did rule out that OpenOCD.exe, the utility which PlatformIO uses for programming and debugging, is the issue.  STM32CubeIDE by default uses the "st-link" utility.  If I configure STM32CubeIDE to use openocd.exe, it still works.  Hence openocd.exe is not the culprit, but perhaps how platformio uses / configures it.
> 
> Although I have a lot of praise for PlatformIO, it does lack/ a little when it comes to programming/debugging support when compared to something like STM32CubeIDE.
> 
> 
> 
>> On Wed, Oct 27, 2021 at 4:44 PM Thalanayar Muthukumar <tnkumar at gmail.com> wrote:
>> I think the issue is that I had made my STM32 micropython based and not Arduino based.
>> 
>>> On Wed, Oct 27, 2021 at 2:47 PM Chris N <netterchris at gmail.com> wrote:
>>> Some boards are better supported than others in Platform IO.  Sometimes you have to tell it explicitly how to talk to your board for the purpose of downloading code and debugging code (which in your case would be via the J-Link JTAG debug interface via USB...)
>>> 
>>> Please attach your platformio.ini file
>>> 
>>> 
>>>> On Wed, Oct 27, 2021 at 1:42 PM Thalanayar Muthukumar <tnkumar at gmail.com> wrote:
>>>> 
>>>>> I just attempted VSCode + PlatformIO + Arduino Framework with my NUCLEO STM32L476RG and got this error.
>>>>> I guess there is some additional configuration I need to do to communicate with my board.
>>>>> 
>>>>> Regards.
>>>>> - Kumar
>>>>> 
>>>>> <image.png>
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Sat, Oct 23, 2021 at 2:22 PM Chris N <netterchris at gmail.com> wrote:
>>>>>> 
>>>>>> What did you use for "Blinky" ?  Was that pre-programmed?   
>>>>>> 
>>>>>> You mentioned both micropython and STM32CubeIDE - I think you want to first decide what language you want to use - Python or C/C++.   Some IDEs are good at both (VS Code), but some IDEs are better than others at working with micropython or circuitpython boards.
>>>>>> 
>>>>>> I would highly recommend VS Code + Platform IO + Arduino Framework + FreeRTOS.
>>>>>> 1) Install Visual Studio Code
>>>>>> 2) Install the Platform IO plug-in + any other plugins you find useful
>>>>>> 3) Create a project via the Platform IO GUI and select your board + Arduino framework
>>>>>> 4) Add libraries (such as FreeRTOS if you want an RTOS, or for OLED display, etc. etc)
>>>>>> 
>>>>>> It's a decent trade-off between ease of use and giving you access to the features that the STM32 MCU has to offer.  Although I really like the STM32CubeIE (see below), for me, the most compelling reason to use PlatformIO+Arduino is the fact that I can pull in just about any library that has ever been created for Arduino-compatible boards.  Plus, the VS Code editor is much better than Eclipse.
>>>>>> 
>>>>>> If you need more fine-grained control over how you use your STM32 MCU, then you would want to use the STM32CubeIDE.   It is slightly better at debugging and the APIs that are provided as part of this give you more control over how all the various peripherals are used.   There is a wizard sort of thing that helps you get the peripherals initialized, so you don't need to know all the ins and outs at that level, but taking advantage of the APIs that are provided is certainly harder than working inside the Arduino framework.
>>>>>> 
>>>>>> Chris.
>>>>>> 
>>>>>>> On Sat, Oct 23, 2021 at 12:44 AM Thalanayar Muthukumar via DPRGlist <dprglist at lists.dprg.org> wrote:
>>>>>>> https://www.youtube.com/watch?v=VNPOWBemGqU
>>>>>>> 
>>>>>>> Got my NUCLEO L476RG today and got my first Blinky work on it.
>>>>>>> I thought of starting with STM32CubeIDE and micropython, but could not figure out how to use these environments.
>>>>>>> Then, I came across mbed.org and was able to get the cpp program for blinky working.
>>>>>>> 
>>>>>>> What do people use as their development environment for the STM32 boards?
>>>>>>> Need suggestions on what is best to use to get the best experience with the STM32.
>>>>>>> 
>>>>>>> Every new chip has its own development environment, startup challenges that one needs to go through ...
>>>>>>> 
>>>>>>> Regards.
>>>>>>> - Kumar
>>>>>>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dprg.org/pipermail/dprglist-dprg.org/attachments/20211029/f7e894e3/attachment.html>