Nucleo dev board default code

[BLynn.1]

I have a Nucleo-F446RE and C031C6. The default code that came on the board uses the blue button to change the LED blink pattern... Is this code available? It would be very helpful to be able to see how it works.

Thanks!!

[Tesla DeLorean]

Should be in the respective board examples in the CubeF4 and CubeC0 repositories.​

[FBL · Accepted solution]

Hello @BLynn.1​,

Here you can find related example for CubeC0. Upcoming repository will be available on Github as well.

STM32CubeC0 - STM32Cube MCU Package for STM32C0 series (HAL, Low-Layer APIs and CMSIS, File tsystem, RTOS - and examples running on ST boards) - STMicroelectronics

Same for F4, you can find example either on ST.COM or on Github STM32CubeF4/Projects/STM32446E-Nucleo/Examples/GPIO/GPIO_IOToggle at master · STMicroelectronics/STM32CubeF4 (github.com)

Hope this answers your question!

[BLynn.1]

Thank you!

[Cats]

Hello all,

Totally newbie with the Nucleo ST 446 board (and ST environment as a whole).

Playing around with the board and ST Link, I erased the stock firmware (the one that uses the blue button to adjust led blinking speed).

After that, I am unable to connect board with the Keil Studio (I was connecting normally before the erase).

I am able to select "build target" the nucleo board, but on the second selection "CONNECTED DEVICE" I have only the selection STM 32 ST LINK (while previously I had the option to select "nucleo board".

So I am unable to run / debug anything.

I suspect that the stock firmware was the one that provided this option...

Does anybody can provide me with the original/stock .bin file of the NUCLEO ST446RE BOARD? 

I tried the above github repositories with no luck...

Thank you all

[Tesla DeLorean]

What else did you do?

I'm not sure Keil identifies as anything other than a "ST-LINK/V2-1" type connection. The STM32 Cube Programmer might be more specific.

Either way, if attached as an ST-LINK, you should be able to connect and program.

Check "Connect Under Reset" option with Keil's Debug Configuration Panes.

Similar, but LED blinking

STM32Cube_FW_F4_V1.27.1\Projects\STM32446E-Nucleo\Examples\GPIO\GPIO_IOToggle

[Cats]

Dear Tesla,

Thanks for reply.

This is what I was thinking to do.

I am still able to flash my Nucleo by using the STM32 ST Link utility.

I just need the ORIGINAL .bin file that the NUCLEO board was equipped when left the factory.

I believe that afterwards the connectivity with the Keil will return to its original state.   

But I am unable to find it...

[Cats]

"what else did you do"?

Nice catch!

Except of erasing the main board chip, I also (I didn't remember it) I downgraded the firmware version of the ST LINK from v45 to v33. 

I discovered it just now. 

After I upgraded the STLINK firmware back to the latest version (...v45...) the KEIL environment was seeing again the "CONNECTED DEVICE" as NUCLEO and not as ST LINK.

Afterwards I flashed successfully the example/projects you pointed me out.

 Of course it is not the original firmware (with the blue button function), it is only an LED blinking, but this is no important.

I have again connectivity.

I am back able to run/debug etc

Thank you for your assistance

[Tesla DeLorean]

Well that's good. The firmware on the NUCLEO-F446RE shouldn't have any impact to the reporting on the PC side. It can block access if it shuts down the debug pins in a number of ways, but Connect-Under-Reset or BOOT0=HIGH should recover those.

I don't have a fresh NUCLEO-F446RE to hand

[Cats]

"...The firmware on the NUCLEO-F446RE shouldn't have any impact to the reporting on the PC side..."

Correct.

Now that I am thinking of it more cool-headedness I recognize this too.

I was frustrated yesterday, unable to think clear!

Thank you once again. You 've been really helpful to "unstuck" me!