Spark Logic

Info Nucle STM32F103

Drakelive Tue Sep 15, 2015 12:25 am

Hi

I tried the example Blink on my Nucleo STM32F103 but I had problems.

Blink example code compiles correctly, the Nuclleo board is updated (falshing) but the LED not blink.
I tried to use the port PA5 and 13 but led is still not blinking.
I also tried to change the port and randomly to choose one of the available pin on the Morpho connectors , the result is the same, the LED doesn’t blink.

On the forum I read that some cards to function properly, they must be amended because of the Crystal disconnected from STMF103.
The serial of my core is: MB1136 C-01 (Rev. C). I must follow the guidance: Nucleo_F103RB_hardware_preparation.pdf ???

If I run these changes can I continue to use my Nucleo board with mbed?

Regard
Drake.

Replies

madias Tue Sep 15, 2015 7:17 am

I think there is a typo about the serial number in the PDF. So this is the right answer:
There are two possible default configurations of the HSE pins depending on the version of NUCLEO board hardware.
The board version MB1136 C-01 or MB1136 C-02 is mentioned on sticker placed on bottom side of the PCB.
The board marking MB1136 C-01 corresponds to a board, configured for HSE not used.
The board marking MB1136 C-02 (or higher) corresponds to a board, configured to use ST- LINK MCO as clock input.
But anyway:
On the forum I read that some cards to function properly, they must be amended because of the Crystal disconnected from STMF103.
The serial of my core is: MB1136 C-01 (Rev. C). I must follow the guidance: Nucleo_F103RB_hardware_preparation.pdf ???
Yes.
If I run these changes can I continue to use my Nucleo board with mbed?
Yes. With the mod you have an additional HSE. As I know mbed uses the (inaccurate) internal OSC so this modification wont harm anything with mbed. As every other board we are using with STM32duino has an external quartz, I decided to use it also on the nucleo board (Otherwise we fall back into nasty compatibility issues), because the workload is minimal (two soldering points).
Only god knows, why ST didn’t fit the 8MHZ quartz.

Everything you asked is written in the UM1724 User manual of the nucleo board. Please read section: 5.7 “OSC clock”

michael_l Tue Sep 15, 2015 10:30 am

You many want to check my thread about the same thing: viewtopic.php?f=3&t=512&start=20

I only soldered SB16 and SB50 and it works. There’s also info on how to modify boards.cpp to get output of ‘Serial’ into Arduino monitor. By default Serial2 goes into serial monitor.

Drakelive Wed Sep 16, 2015 8:19 am

michael_l wrote:You many want to check my thread about the same thing: viewtopic.php?f=3&t=512&start=20

I only soldered SB16 and SB50 and it works. There’s also info on how to modify boards.cpp to get output of ‘Serial’ into Arduino monitor. By default Serial2 goes into serial monitor.

Drakelive Thu Sep 24, 2015 1:57 pm

Hi

Following your advice I soldered the SB16 and SB50 (only these two) and I checked the proper functioning of Blink with my ST Nucleo STM32F103.
It works perfectly. I am happy because the blink working properly, also on a CZ Mini board , I talked about this in the tread: http://www.stm32duino.com/viewtopic.php?f=28&t=295

Last night I tried a test without STM32duino but using the CORE written by Andy Sze : https://github.com/MakerLabMe/STM32_Arduino_Cores
I tried the Blink and discovered that on CZ Mini board works perfectly but does not work on my ST Nucleo STM32F103

I understand that here do not talk about other CORE but I just hope to be helped to find the right way.
There are big differences between a STM32F103RB (ST Nucleo) and a STM32F103ZE (CZ Mini)? Only the amount of flash memory?

I fear that there are still problems on the Clock.
I soldered only SB16 and SB50, but the guide Nucleo_F103RB_hardware_preparation.pdf, also recommended to remove the resistors SB55 and SB54 which I have not done. Perhaps this is the problems? A What are these resistors?
Perhaps the two CORE have a different way to set the clock? In this case there are files where I can go and find the source code?

Thank you
Drake

madias Thu Sep 24, 2015 3:54 pm

Everything you asked is written in the UM1724 User manual of the nucleo board. Please read section: 5.7 “OSC clock”
SB54, SB55 (X3 crystal)
OFF X3, C33, C34, R35 and R37 provide a clock as shown in Chapter 7: Electrical schematics PF0/PD0/PH0, PF1/PD1/PH1 are disconnected from CN7.

ON PF0/PD0/PH0, PF1/PD1/PH1 are connected to CN12. (R35, R37 and SB50 must not be fitted).

Personally I wont use the MakerLabMe core, it’s really old and not complete.
Edit: do you use the pin number (like 33) on nucleo or the real pin name (like PA15) for the not working blink example?

madias Thu Sep 24, 2015 4:03 pm

There are big differences between a STM32F103RB (ST Nucleo) and a STM32F103ZE (CZ Mini)? Only the amount of flash memory?
I think there are many differences, like pin numbers, additional HW on CZ, you can compare the “variant” folders: The generic generic_stm32f103z and the nucleo. The next thing: Is using MakerLabMe the same upload routines? Nucleo on stm32duino is ST-link and your ZE board?

Drakelive Mon Sep 28, 2015 5:02 pm

Hi madias

I downloaded and read the latest version (August 4, 2015) on the site ST : http://www.st.com/web/catalog/tools/FM1 … oF103RB-pr
In the chapter “5.6.1 OSC clock supply” in the page 22 describes four possible ways to enable the right clock but only 2 represent valuable opportunities:

1) MCO from ST-LINK
2) HSE oscillator on-board from X3 crystal but it requires the addition of a new 8MHz crystal

I admit to having made a part of the procedure 1 … I should have read more. I believe that the procedure 2 is more complete but requires the addition of a crystal that does not possess now. This week study documents ST, to deepen this topic….

madias wrote: ….. Is using MakerLabMe the same upload routines? Nucleo on stm32duino is ST-link and your ZE board?

madias Tue Sep 29, 2015 7:46 pm

Drakelive wrote:
I admit to having made a part of the procedure 1 … I should have read more. I believe that the procedure 2 is more complete but requires the addition of a crystal that does not possess now. This week study documents ST, to deepen this topic….

Drakelive Thu Oct 01, 2015 12:15 pm

madias wrote:Drakelive wrote:
I admit to having made a part of the procedure 1 … I should have read more. I believe that the procedure 2 is more complete but requires the addition of a crystal that does not possess now. This week study documents ST, to deepen this topic….

madias Thu Oct 01, 2015 2:18 pm

I also bought the external programmer of ST
Is this original ST Link also “drag & drop”? (I think only the nucleo has the ST-Link 2.1 (mind the “2.1”, all 2.0 are not d&d able!))
This is the really funny part of it, because I can use every computer without installing anything and upload the *.bin via “drag&drop”
The “CZ mini” series are well made in my opinion, I really love the board in my post above.
Next drawback of the nucleo: there is no pin description on the PCB itself :) (And the Arduino style numbers (D0-13, A0-A5) makes only sense for MCU’s with very less count of pins, for STM32 I always use real names, like “PA4” or “PC3” just to be compatible with other STM32 boards)

Drakelive Fri Oct 02, 2015 12:06 pm

madias wrote:I also bought the external programmer of ST
Is this original ST Link also “drag & drop”? (I think only the nucleo has the ST-Link 2.1 (mind the “2.1”, all 2.0 are not d&d able!))
This is the really funny part of it, because I can use every computer without installing anything and upload the *.bin via “drag&drop”
The “CZ mini” series are well made in my opinion, I really love the board in my post above.
Next drawback of the nucleo: there is no pin description on the PCB itself :) (And the Arduino style numbers (D0-13, A0-A5) makes only sense for MCU’s with very less count of pins, for STM32 I always use real names, like “PA4” or “PC3” just to be compatible with other STM32 boards)

Sign in to reply