Error no debug probe detected

Arduino for STM32 Everything relating to using STM32 boards with the Arduino IDE and alternatives Error when running STM32_Programmer_CLI Post by henninb » Sun Feb 28, 2021 1:33 pm Hi, I am running Arch Linux and I am trying to use the STM32_Programmer_CLI, but when I try I get an error (see below). Can […]

Содержание

  1. Arduino for STM32
  2. Error when running STM32_Programmer_CLI
  3. Error no debug probe detected
  4. Error no debug probe detected
  5. Kelvin-Solo / gist:8026068cde48f2eb52eac5d152f2c76b
  6. Footer
  7. nRF52832 custom board, chip not getting detected

Arduino for STM32

Everything relating to using STM32 boards with the Arduino IDE and alternatives

Error when running STM32_Programmer_CLI

Post by henninb » Sun Feb 28, 2021 1:33 pm

Hi, I am running Arch Linux and I am trying to use the STM32_Programmer_CLI, but when I try I get an error (see below). Can some please provide some direction or thoughts. I can connect to the device via the JAVA front end application. My STM32F103C device is connected physically with and FDTI UART. Thank you.

Error: No debug probe detected.

Just as the error message states: The FTDI adapter is not a ( ST-Link ) debug probe.

The FTDI is opened as a serial port on the Linux side and also when connected to the STM32F103C, I assume it is connected to RX and TX pins. So for STM32_Programmer_CLI you must give the serial port on Arch Linux that is opened for the FTDI adapter.

In order to program the chip using he serial interface it must also be in onchip bootloader mode using BOOT0 when it resets.

The SWD connect is used when you connect a ST-Link debug adapter to the SWD pins on the board. In this case the BOO0 is not need, the SWD interface can program the chip without going through the bootloader.

It is possible to use the FTDI as a SWD interface using programs like OpenOCD, and then connect to the SWCLK and SWIO pins on the STM32F103C, but I dont think that STM32_Programmer_CLI, OpenOCD can handle the programming of the chip flash.

Источник

Error no debug probe detected

As in the other Blue Pill thread, did you change the upload type to type one with ‘serial’ in it? I believe the default is to use the ‘SWD’ method (the ST-Link dongle) which won’t work and neither will the ‘DFU’ method on the STM32 Blue Pill PCB.

Again. in the Wiki.

I’ve recently bought the F303CC and tried to upload, but received a «No debug probe detected» message (see below). My board and ‘upload settings’, etc as exactly as per Khalid’s youtube video. Any ideas?

Sketch uses 169284 bytes (64%) of program storage space. Maximum is 262144 bytes.
Global variables use 12360 bytes (30%) of dynamic memory, leaving 28600 bytes for local variables. Maximum is 40960 bytes

Error: No debug probe detected.

Thank you both for your patience with numptys like me. Dave’s suggestion was the one that worked

Relooked at the wiki and it’s def there for the STMduino method of flashing (wiki refers to F103, but works the same for F303). Shows my level of knowledge (I was previously using the Arduino_STM32 method previously)

Ok, now it’s my turn back in upgrade ‘hell’:
I’ve been trying to upgrade one of my BluePill controllers to Version 4.21.d3 (The controller works ok under 3.16n, but of course, I can’t ever stop there)
I installed the STM32 Cube Programmer v2.5.0 and believe I’ve been following the Wiki to the letter.
My Arduino ‘tools’ menu matches the Wiki example

Error message from Arduino is:

Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again.

——————————————-
Any suggestions? I’ve seen references to uploading the Blue Pill via software other than Arduino, but the process is beyond my current skill level.
I’ve also tried Khalid’s suggestion in previous post https://onstep.groups.io/g/main/message/27389, but I got the error message ‘Failed to init device’. Could my CP2102 be the culprit? The led flashes, and Win10 Device Manager says it’s connected.
Fortunately, my original 3.16n install still works, so I haven’t totally bricked it, yet. Not for a lack of trying.

Ok, now it’s my turn back in upgrade ‘hell’:
I’ve been trying to upgrade one of my BluePill controllers to Version 4.21.d3 (The controller works ok under 3.16n, but of course, I can’t ever stop there)
I installed the STM32 Cube Programmer v2.5.0 and believe I’ve been following the Wiki to the letter.
My Arduino ‘tools’ menu matches the Wiki example

Источник

Error no debug probe detected

As in the other Blue Pill thread, did you change the upload type to type one with ‘serial’ in it? I believe the default is to use the ‘SWD’ method (the ST-Link dongle) which won’t work and neither will the ‘DFU’ method on the STM32 Blue Pill PCB.

Again. in the Wiki.

I’ve recently bought the F303CC and tried to upload, but received a «No debug probe detected» message (see below). My board and ‘upload settings’, etc as exactly as per Khalid’s youtube video. Any ideas?

Sketch uses 169284 bytes (64%) of program storage space. Maximum is 262144 bytes.
Global variables use 12360 bytes (30%) of dynamic memory, leaving 28600 bytes for local variables. Maximum is 40960 bytes

Error: No debug probe detected.

Thank you both for your patience with numptys like me. Dave’s suggestion was the one that worked

Relooked at the wiki and it’s def there for the STMduino method of flashing (wiki refers to F103, but works the same for F303). Shows my level of knowledge (I was previously using the Arduino_STM32 method previously)

Ok, now it’s my turn back in upgrade ‘hell’:
I’ve been trying to upgrade one of my BluePill controllers to Version 4.21.d3 (The controller works ok under 3.16n, but of course, I can’t ever stop there)
I installed the STM32 Cube Programmer v2.5.0 and believe I’ve been following the Wiki to the letter.
My Arduino ‘tools’ menu matches the Wiki example

Error message from Arduino is:

Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again.

——————————————-
Any suggestions? I’ve seen references to uploading the Blue Pill via software other than Arduino, but the process is beyond my current skill level.
I’ve also tried Khalid’s suggestion in previous post https://onstep.groups.io/g/main/message/27389, but I got the error message ‘Failed to init device’. Could my CP2102 be the culprit? The led flashes, and Win10 Device Manager says it’s connected.
Fortunately, my original 3.16n install still works, so I haven’t totally bricked it, yet. Not for a lack of trying.

Ok, now it’s my turn back in upgrade ‘hell’:
I’ve been trying to upgrade one of my BluePill controllers to Version 4.21.d3 (The controller works ok under 3.16n, but of course, I can’t ever stop there)
I installed the STM32 Cube Programmer v2.5.0 and believe I’ve been following the Wiki to the letter.
My Arduino ‘tools’ menu matches the Wiki example

Источник

Kelvin-Solo / gist:8026068cde48f2eb52eac5d152f2c76b

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

Sketch uses 14168 bytes (21%) of program storage space. Maximum is 65536 bytes.
Global variables use 920 bytes (4%) of dynamic memory, leaving 19560 bytes for local variables. Maximum is 20480 bytes.
——————————————————————-
STM32CubeProgrammer v2.6.0
——————————————————————-
Error: No debug probe detected.
Error: No debug probe detected.

Am supposed to set up as directed in https://github.com/stm32duino/wiki/wiki/Upload-methods.
I have done everything till the Arduino Integration part. I don’t understand how to proceed from there.
I am supposed to use the script in https://github.com/stm32duino/Arduino_Tools/blob/master/linux/stm32CubeProg.sh but I am not sure how to use it since am using the Arduino Upload button.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

nRF52832 custom board, chip not getting detected

I am trying to design my custom board using nRF52832. I am using Segger jLink Mini EDU to connect/debug the chip/board.
I took Thingy:52 as reference and designed my board. Here are my details about board.

1) I verified voltages at rhe 52832 level and found ever thing is OK, pin48, 36, 13 are at 3.3 volts.
2) used both 32MHz and 32.768 KHz crystals.
3) I connected SWDIO and SWDCLK pins from 52832 to the Jlink Mini.

I am using nRFconnect V2.5.0 and Programmer Experimental to connect the board. When I tried to select the device, I could only get debug probe, no serial port was detected. I am using a fresh board here.

Can anyone let me know, what could be my problem?
Do I need to use any other SW/tool to get my board detected?
Will there be any problem in my board? if so, can anyone suggest any debug points ?

I can share my schematic, if needed.

Are you trying to upload using a serial bootloader or just flash using the SWO lines? Either way I would just try uploading one of the sample programs using the JLink to ensure the device is communicating correctly.

Your Jlink Mini probably does not support the serial port. It would also need additional wires to the NRF chip (RX and TX for the UART).

Speaking of wires: You need VCC (might be called VRef on the JLink) and GND in order to be able to talk to the NRF chip via SWD.

my JLink does support SWD. I connected SWDIO and SWDCLK pins from JLink to the nRF52832.

I followed the diagram explained in the thread,

to connect jLInk to the custom board.

Do I additionally need to connect serial port from custom board to flash boot loader to make it detected via SWD by JLink?

Your choice of software seems weired, just use either the nrfjprog command line tool or nRFGo studio. Both support programming via SWD.

You can also use the JLInk Commander to manually check wether it can connect to the target MCU. I use this when I’m suspecting cabling problems.

Serial Wire Debug (SWD) has nothing to do with Serial COM port (UART) and to program an nRF52 device you need SWD (a serial port is an optional feature). With external programmers like yours, you won’t see «Serial port: COMx» listed in the nRF Connected apps. The latest version of nRF Connect Programmer should support JLink EDU Mini anyway, although we haven’t tested this specific programmer.

  1. Do you have problems programming or are you just wondering why you don’t get a serial port?
  2. Do you get any error messages in the Log window?
  3. Can you confirm that you have connected VDD and GND on your board to VTref and GND on the JLINK EDU?

If you are having problems programming, I suggest that you try nrfjprog as Turbo J mentioned, just to rule out any issues with nRF Connect Programmer.

Источник

henninb

Posts: 2
Joined: Sun Feb 28, 2021 1:27 pm

Error when running STM32_Programmer_CLI

Hi, I am running Arch Linux and I am trying to use the STM32_Programmer_CLI, but when I try I get an error (see below). Can some please provide some direction or thoughts. I can connect to the device via the JAVA front end application. My STM32F103C device is connected physically with and FDTI UART. Thank you.

❯ STM32_Programmer_CLI —connect port=SWD
——————————————————————-
STM32CubeProgrammer v2.6.0
——————————————————————-

Error: No debug probe detected.

by mlundin » Sun Feb 28, 2021 3:12 pm

Just as the error message states: The FTDI adapter is not a ( ST-Link ) debug probe.

The FTDI is opened as a serial port on the Linux side and also when connected to the STM32F103C, I assume it is connected to RX and TX pins. So for STM32_Programmer_CLI you must give the serial port on Arch Linux that is opened for the FTDI adapter.

In order to program the chip using he serial interface it must also be in onchip bootloader mode using BOOT0 when it resets.

The SWD connect is used when you connect a ST-Link debug adapter to the SWD pins on the board. In this case the BOO0 is not need, the SWD interface can program the chip without going through the bootloader.

It is possible to use the FTDI as a SWD interface using programs like OpenOCD, and then connect to the SWCLK and SWIO pins on the STM32F103C, but I dont think that STM32_Programmer_CLI, OpenOCD can handle the programming of the chip flash.

Go to full post

mlundin

Posts: 94
Joined: Wed Nov 04, 2020 1:20 pm

Answers: 6

Location: Sweden

Re: Error when running STM32_Programmer_CLI

Post

by mlundin » Sun Feb 28, 2021 3:12 pm

Just as the error message states: The FTDI adapter is not a ( ST-Link ) debug probe.

The FTDI is opened as a serial port on the Linux side and also when connected to the STM32F103C, I assume it is connected to RX and TX pins. So for STM32_Programmer_CLI you must give the serial port on Arch Linux that is opened for the FTDI adapter.

In order to program the chip using he serial interface it must also be in onchip bootloader mode using BOOT0 when it resets.

The SWD connect is used when you connect a ST-Link debug adapter to the SWD pins on the board. In this case the BOO0 is not need, the SWD interface can program the chip without going through the bootloader.

It is possible to use the FTDI as a SWD interface using programs like OpenOCD, and then connect to the SWCLK and SWIO pins on the STM32F103C, but I dont think that STM32_Programmer_CLI, OpenOCD can handle the programming of the chip flash.

henninb

Posts: 2
Joined: Sun Feb 28, 2021 1:27 pm


Hi All

I’ve recently bought the F303CC and tried to upload, but received a «No debug probe detected» message (see below). My board and ‘upload settings’, etc as exactly as per Khalid’s youtube video. Any ideas?

Sketch uses 169284 bytes (64%) of program storage space. Maximum is 262144 bytes.
Global variables use 12360 bytes (30%) of dynamic memory, leaving 28600 bytes for local variables. Maximum is 40960 bytes

. ——————————————————————- STM32CubeProgrammer v2.5.0 ——————————————————————-

Error: No debug probe detected.

Thx
Scott


Khalid Baheyeldin

On Tue, Nov 10, 2020 at 03:23 PM, <scott.farndell@…> wrote:

STM32CubeProgrammer v2.5.0

Error: No debug probe detected.

I don’t use STM32CubeProgrammer.
Instead, I use stm32flash, and it works like this:

stm32flash -g 0x8000000 -b 115200 -w OnStep.ino.bin /dev/ttyUSB0

On Windows replace /dev/ttyUSB0 with COM9 or whatever port number.

If this is something you can do, then go ahead and try it.
Otherwise, wait until someone who uses Windows and STM32CubeProgrammer
answers Robert Utecht in the other thread.


As in the other Blue Pill thread, did you change the upload type to type one with ‘serial’ in it? I believe the default is to use the ‘SWD’ method (the ST-Link dongle) which won’t work and neither will the ‘DFU’ method on the STM32 Blue Pill PCB.

Again… in the Wiki.


toggle quoted message

Show quoted text

On 2020-11-10 3:23 p.m., scott.farndell@… wrote:

Hi All

I’ve recently bought the F303CC and tried to upload, but received a «No debug probe detected» message (see below). My board and ‘upload settings’, etc as exactly as per Khalid’s youtube video. Any ideas?

Sketch uses 169284 bytes (64%) of program storage space. Maximum is 262144 bytes.
Global variables use 12360 bytes (30%) of dynamic memory, leaving 28600 bytes for local variables. Maximum is 40960 bytes

. ——————————————————————-
STM32CubeProgrammer v2.5.0 ——————————————————————-

Error: No debug probe detected.

Thx
Scott


Thank you both for your patience with numptys like me. Dave’s suggestion was the one that worked

Relooked at the wiki and it’s def there for the STMduino method of flashing (wiki refers to F103, but works the same for F303). Shows my level of knowledge (I was previously using the Arduino_STM32 method previously)  


STM32Cube works with the ST-Link and the cheap ST=Link V2 copies. You can export a raw binary file from the Arduino IDE and up load it to the F303 or APMF103CB. 


Ok, now it’s my turn back in upgrade ‘hell’:
I’ve been trying to upgrade one of my BluePill controllers to Version 4.21.d3  (The controller works ok under 3.16n, but of course, I can’t ever stop there)
I installed the STM32 Cube Programmer v2.5.0 and believe I’ve been following the Wiki to the letter.
My Arduino ‘tools’ menu matches the Wiki example

Error message from Arduino is:

Sketch uses 118472 bytes (90%) of program storage space. Maximum is 131072 bytes.

Global variables use 11412 bytes (55%) of dynamic memory, leaving 9068 bytes for local variables. Maximum is 20480 bytes.

C:UsersrnshaAppDataLocalArduino15packagesSTM32toolsSTM32Tools1.4.0/tools/win/stm32CubeProg.bat 1 C:UsersrnshaAppDataLocalTemparduino_build_333386/OnStep.ino.bin COM5 -s 

      ——————————————————————-

                       STM32CubeProgrammer v2.5.0                  

      ——————————————————————-

Serial Port COM5 is successfully opened.

Port configuration: parity = even, baudrate = 115200, data-bit = 8,

                     stop-bit = 1.0, flow-control = off

Timeout error occured while waiting for acknowledgement.

Timeout error occured while waiting for acknowledgement.

Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again… 

——————————————-
Any suggestions?  I’ve seen references to uploading the Blue Pill via software other than Arduino, but the process is beyond my current skill level.  
I’ve also tried Khalid’s suggestion in previous post https://onstep.groups.io/g/main/message/27389, but I got the error message ‘Failed to init device’.  Could my CP2102 be the culprit? The led flashes, and Win10 Device Manager says it’s connected.
Fortunately, my original 3.16n install still works, so I haven’t totally bricked it, yet.  Not for a lack of trying…


I immediately notice that the the sketch size says ‘118472 bytes (90%)’ and maximum 131072. That is not correct for an STM32F303CC… they all have 256KB so something in the board settings is incorrect.


toggle quoted message

Show quoted text

On 2020-11-15 1:21 p.m., Richard Shagam wrote:

Ok, now it’s my turn back in upgrade ‘hell’:
I’ve been trying to upgrade one of my BluePill controllers to Version 4.21.d3  (The controller works ok under 3.16n, but of course, I can’t ever stop there)
I installed the STM32 Cube Programmer v2.5.0 and believe I’ve been following the Wiki to the letter.
My Arduino ‘tools’ menu matches the Wiki example

Error message from Arduino is:
Sketch uses 118472 bytes (90%) of program storage space. Maximum is 131072 bytes.
Global variables use 11412 bytes (55%) of dynamic memory, leaving 9068 bytes for local variables. Maximum is 20480 bytes.
C:UsersrnshaAppDataLocalArduino15packagesSTM32toolsSTM32Tools1.4.0/tools/win/stm32CubeProg.bat 1 C:UsersrnshaAppDataLocalTemparduino_build_333386/OnStep.ino.bin COM5 -s
——————————————————————-
                       STM32CubeProgrammer v2.5.0
——————————————————————-
Serial Port COM5 is successfully opened.
Port configuration: parity = even, baudrate = 115200, data-bit = 8,
                     stop-bit = 1.0, flow-control = off
Timeout error occured while waiting for acknowledgement.
Timeout error occured while waiting for acknowledgement.
Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again…

——————————————-
Any suggestions?  I’ve seen references to uploading the Blue Pill via software other than Arduino, but the process is beyond my current skill level.
I’ve also tried Khalid’s suggestion in previous post https://onstep.groups.io/g/main/message/27389, <https://onstep.groups.io/g/main/message/27389,> but I got the error message ‘Failed to init device’.  Could my CP2102 be the culprit? The led flashes, and Win10 Device Manager says it’s connected.
Fortunately, my original 3.16n install still works, so I haven’t totally bricked it, yet.  Not for a lack of trying…


Khalid Baheyeldin

On Sun, Nov 15, 2020 at 01:21 PM, Richard Shagam wrote:

Serial Port COM5 is successfully opened.

Port configuration: parity = even, baudrate = 115200, data-bit = 8,

                     stop-bit = 1.0, flow-control = off

Timeout error occured while waiting for acknowledgement.

Timeout error occured while waiting for acknowledgement.

Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again… 

Richard,

Did you power off the controller, switch the Flash/Run switch to the Flash position, power on, then insert the USB into the PC?
If you forgot to do that, then the Blue Pill will not be in flash mode and STM32CubeProg will not flash it.


On Sun, Nov 15, 2020 at 02:58 PM, Khalid Baheyeldin wrote:

Did you power off the controller, switch the Flash/Run switch to the Flash position, power on, then insert the USB into the PC?
If you forgot to do that, then the Blue Pill will not be in flash mode and STM32CubeProg will not flash it.

Khalid:  Yes, I did all of that.  I even just verified it again, getting the same result
Dave:  I’m using the STM32F103C8T6 ARM STM32, which I’m pretty sure I purchased on Ebay here: https://www.ebay.com/itm/232564766661  (This chip successfully runs ver. 3.16n)
And here is my ‘tools’ drop down menu from Arduino


You’ve posted in a thread about the STM32F303CC and nowhere before this did you mention that you were actually talking about «Blue Pill Classic» so I’m not going to apologize for that.

Just to double check… after you change the switch to the Flash position you do turn on the main power to the PCB and then plug in the USB cable from the CP2102? I admit that more than a few times I have forgotten to turn on the main power and only realized it after I got an upload failure.

If the sequence is being performed correctly, then there could be something wrong with either the switch or its three-wire connection to the BOOT0 header. Maybe it has come loose and needs to be reseated or has been reseated but over the wrong pins? Try removing it at the STM32 and go back to using the original jumper, just to eliminate that possibility.

It seems that your CP2102 is working, at least the end that connects to the PC, but could be a problem with the soldering so its not reliably connecting to the PCB. If you didn’t stabilize the CP2102 with the PCB by injecting non-conductive glue (hot melt glue was suggested) between them, perhaps a marginal connection has gone bad due to flexing. Since your 3.16 software still works, can you connect to it over the USB (use the IDE serial monitor without trying to upload anything), issue a simple command like :GU# and get a response?


toggle quoted message

Show quoted text

On 2020-11-16 10:02 a.m., Richard Shagam wrote:

On Sun, Nov 15, 2020 at 02:58 PM, Khalid Baheyeldin wrote:

Did you power off the controller, switch the Flash/Run switch to
the Flash position, power on, then insert the USB into the PC?
If you forgot to do that, then the Blue Pill will not be in flash
mode and STM32CubeProg will not flash it.

Khalid:  Yes, I did all of that.  I even just verified it again, getting the same result
Dave:  I’m using the STM32F103C8T6 ARM STM32, which I’m pretty sure I purchased on Ebay here: https://www.ebay.com/itm/232564766661 <https://www.ebay.com/itm/232564766661> (This chip successfully runs ver. 3.16n)
And here is my ‘tools’ drop down menu from Arduino


Khalid Baheyeldin

Richard,

After you verify that the CP2102 is working (the :GU# command that Dave mentioned),
you may want to try STM32Flash.

If so, then do this:

Download stm32flash for Windows.

Then select Sketch -> Export Compiled Binary.

After this completes, you will find a file in the OnStep directory:

For example:

OnStep.ino.PILL_F103XX.bin

Then you use stm32flash like so, from a command prompt:

cd YourOnStepDirectory
stm32flash -g 0x8000000 -b 115200 -w OnStep.ino.PILL_F103XX.bin COM5

See if that makes any difference.


Dave,
Sorry if I misled you re: the Blue Pill chip I’ve been using—all these part numbers look the same after awhile.  I found the problem—it does appear to be a loose connection between the CP2102 board and PC board—always something dumb!  I was able to upload version 4.21d successfully by placing my thumb on the chip.  Otherwise, all appears to work find.  So lesson learned:  anyone having upload problems should probably check that first.  Now to get out the soldering iron…
Thanks for the guidance.  


Hey, great that you found it. Debugging these things is just a matter of being methodical. And easier if you know it was working at one time… just follow the paths and check everything that could go wrong (because it usually does sooner or later).


toggle quoted message

Show quoted text

On 2020-11-16 3:13 p.m., Richard Shagam wrote:

Dave,
Sorry if I misled you re: the Blue Pill chip I’ve been using—all these part numbers look the same after awhile.  I found the problem—it does appear to be a loose connection between the CP2102 board and PC board—always something dumb!  I was able to upload version 4.21d successfully by placing my thumb on the chip.  Otherwise, all appears to work find.  So lesson learned: anyone having upload problems should probably check that first. Now to get out the soldering iron…
Thanks for the guidance.


I’m getting exactly same, have you managed to solve this issue.


thought it was just me, the flash success seems to be extremely random with arduino ide, takes a lot of atte,pts, reconnecting the cables, flicking the power.And once in a while, it just works..

Topic: Yet another DIY GPSDO — yes, another one  (Read 100787 times)

0 Members and 3 Guests are viewing this topic.

Where I am having trouble is 1) mounting the parts properly (the OCXO has oddball pin spacing) and 2) the software/firmware aspects.

I suggest you check the other forums here on EEVblog and ask for help on specific points where you are having trouble.

For mounting the parts: https://www.eevblog.com/forum/beginners/
Also check the pictures posted by enut11. You can copy what he did to mount the (5 pins) OCXO on a perfboard.

For the Arduino IDE, programming and flashing the MCU: https://www.eevblog.com/forum/microcontrollers/ or the excellent Arduino forum: https://forum.arduino.cc/


Logged

The following users thanked this post: enut11


Hey @bob91343. I understand your situation. I too grew up with analog electronics and struggle with all this digital stuff. However, we now live in a digital age so have to manage it in some way. There’s lots of help on this Forum and all you need do is follow the advice, step by step, at your own pace.
enut11

@AndrewBCN, here is my powered-up GPSDO project. Added the LED as suggested (bottom left micro board) but there is still some wiring to do.
I am powering it all from a 12v SMPS plugpak into a 7805 5v regulator. The regulator directly powers the OCXO and there is a 5v takeoff to the micro board.
The small heatsink under the 7805 seems adequate for now and runs a little hotter than the OCXO.

« Last Edit: October 13, 2021, 07:09:17 pm by enut11 »


Logged

an electronics nut from wayback…

The following users thanked this post: AndrewBCN


@AndrewBCN
Some questions on the circuit. I intend to only use the modules above.
1) is Vocxo redundant?
2) What is the purpose of the 2.5v bias on STM pin26?
3) C4/C5 look to be part of a filter. Is the 10uF value critical? I have 22uF on hand.
enut11

« Last Edit: October 14, 2021, 01:24:06 am by enut11 »


Logged

an electronics nut from wayback…



@AndrewBCN, here is my powered-up GPSDO project. Added the LED as suggested (bottom left micro board) but there is still some wiring to do.
I am powering it all from a 12v SMPS plugpak into a 7805 5v regulator. The regulator directly powers the OCXO and there is a 5v takeoff to the micro board.
The small heatsink under the 7805 seems adequate for now and runs a little hotter than the OCXO.

Looking good.  :-+ Thanks for the pics, btw.


Logged


@AndrewBCN
Some questions on the circuit. I intend to only use the modules above.
1) is Vocxo redundant?
2) What is the purpose of the 2.5v bias in STM pin26?
3) C4/C5 look to be part of a filter. Is the 10uF value critical? I have 22uF on hand.
enut11

1) Vocxo is only used if you are using an optional INA219 current sensor to measure the power consumption of the OCXO, you can ignore it in your case.
2) That’s explained in the schematic version 0.6. Actually that’s an input to the ADC channel 0, we just measure Vcc divided by 2. IIRC it’s also optional.  :)
3) C4 and C5 are used to filter the PWM output of the STM32 to generate Vctl. In your case you have the choice of using the MCP4725 DAC or this simple PWM. I suggest you use the PWM. And no the value of C4/C5 is not critical, 22uF should work fine.

Why the PWM and not the DAC? The PWM is 16 bit and the DAC is 12 bit resolution.


Logged

The following users thanked this post: enut11


Thanks. In that case I do not need the 4725 DAC so I will unplug it and save a bit of power. Also, I will not use the 4.7K/4.7K divider to pin 26 of STM micro

The 7805 was getting too hot with the small heatsink so I interfaced a programmable pre-regulator, here showing ~8.5v/220mA

Easy part done (all the wiring), now the hard part — loading the control program  >:D

Do I need to unplug the micro from the PCB in order to program it via USB C?

« Last Edit: October 14, 2021, 06:47:21 am by enut11 »


Logged

an electronics nut from wayback…

The following users thanked this post: AndrewBCN


Thanks. In that case I do not need the 4725 DAC so I will unplug it and save a bit of power. Also, I will not use the 4.7K/4.7K divider to pin 26 of STM micro

The 7805 was getting too hot with the small heatsink so I interfaced a programmable pre-regulator, here showing ~8.5v/220mA

Easy part done (all the wiring), now the hard part — loading the control program  >:D

Do I need to unplug the micro from the PCB in order to program it via USB C?

Looking very good.  :-+ In principle, you can program the STM32 Black Pill in-circuit and run the firmware while always connected to your PC — and read the status messages on the Arduino IDE Serial Monitor (see my post on the first page of this thread). This is actually almost essential for testing/debugging, since you don’t have an OLED display.

But for testing your STM32 programming setup (with the Blinky program) I would disconnect the Black Pill from the perfboard.

Once you have passed the «Blinky test», we can proceed to configure the firmware to your hardware setup.


Logged


This is the website that I was working from:
https://www.sgbotic.com/index.php?dispatch=pages.view&page_id=49

Man, what a process downloading and installing the Arduino IDE!
I ended up with V1.8.16. I also downloaded and installed STM32Cube.

I then copied the ‘blink’ code into a new page on the IDE and started the upload process.

I received an error message
Arduino: 1.8.16 (Windows Store 1.8.51.0) (Windows 10), Board: «Generic STM32F4 series, BlackPill F411CE, STM32CubeProgrammer (DFU), Enabled (generic ‘Serial’), CDC (generic ‘Serial’ supersede U(S)ART), Low/Full Speed, Smallest (-Os default), Newlib Nano (default)»

Sketch uses 22128 bytes (4%) of program storage space. Maximum is 524288 bytes.

Global variables use 3624 bytes (2%) of dynamic memory, leaving 127448 bytes for local variables. Maximum is 131072 bytes.

An error occurred while uploading the sketch

STM32_Programmer_CLI.exe not found.

Please install it or add <STM32CubeProgrammer path>bin’ to your PATH environment:

https://www.st.com/en/development-tools/stm32cubeprog.html

Aborting!

This report would have more information with
«Show verbose output during compilation»
option enabled in File -> Preferences.

Could this be due to me changing STM32Cube from the default installation directory?


Logged

an electronics nut from wayback…



Could this be due to me changing STM32Cube from the default installation directory?

I can’t really help you here, because I use Linux and you are using Windows 10. But from the error message, it seems you can solve the problem by uninstalling STM32Cube and reinstalling it in its default installation directory, where the Arduino IDE should be able to find it.

If you need help with this Windows 10 installation, please take a look at the STM32duino forum, there are a number of very competent people there willing to help.

https://www.stm32duino.com/viewforum.php?f=35

« Last Edit: October 14, 2021, 11:46:18 am by AndrewBCN »


Logged



Logged

The following users thanked this post: enut11


Well, some success with Blinky, but I am not sure!

I re-installed the STM32 Cube into its default directory.
I then tried to upload Blinky but got the following error message:
«Error: No debug probe detected»

On re-connecting the STM32 to USB the blue led now blinks slowly.

As I said, I am not sure if it has successfully passed this test!


Logged

an electronics nut from wayback…


Well, some success with Blinky, but I am not sure!

I re-installed the STM32 Cube into its default directory.
I then tried to upload Blinky but got the following error message:
«Error: No debug probe detected»

On re-connecting the STM32 to USB the blue led now blinks slowly.

As I said, I am not sure if it has successfully passed this test!

It seems «Blinky» has been flashed successfully!  :-+

Now you can try to upload a program to test the serial monitor and then we can move on to testing the GPSDO firmware.

To test the serial monitor, try flashing the Communication-> ASCII table example. Open the serial monitor and you should see the ASCII table being printed out.


Logged


A little more info on the serial monitor test please.

As for the «blinky» test, it is more a fading in-out of the blue LED rather than a flash which makes me think that something is not working?


Logged

an electronics nut from wayback…


basically arduino looking for PATH for bin folder for CubeProg, in overall you can install it in any place   adding path, or create a custom one per session. like:

my working folder:  C:Arduino  ;  inside C:ArduinoarduinoIDE — with IDE and STM: C:ArduinoSTM32CubeProg

i created runard.BAT in :ArduinoarduinoIDE , to launch IDE, with custom PATH variable it looks like, last after ; is what we need :

REM ——
SET PATH=C:Program Files (x86)Common FilesOracleJavajavapath;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:ArduinoSTM32CubeProgbin

arduino.exe
REM ——

for com port, when you STM running, it will be COM port in your system, to know precise  one:

You can press Windows + R keys simultaneously to open Windows Run.
type  compmgmt.msc, and hit Enter to open it.

Device Manager -> Ports (COM @ LPT)  …  List of ports (COM-X ) your device

compilation process in IDE should invoke STM …  like this:
Sketch uses 22156 bytes (8%) of program storage space. Maximum is 262144 bytes.
Global variables use 3624 bytes (5%) of dynamic memory, leaving 61912 bytes for local variables. Maximum is 65536 bytes.
      ——————————————————————-
                       STM32CubeProgrammer v2.6.0       

and so … lot of additional info …. ending:

File download complete
Time elapsed during download operation: 00:00:01.152

RUNNING Program …
  Address:      : 0x8000000
Start operation achieved successfully

« Last Edit: October 14, 2021, 09:06:46 pm by GigaJoe »


Logged


Gigajoe quote
«You can press Windows + R keys simultaneously to open Windows Run.
type  compmgmt.msc, and hit Enter to open it.
«

Yes, I did this after plugging the STM32 into the USB port. It did not show up in Device Manager Ports. Do any of the buttons on the STM32 board have to be pressed?


Logged

an electronics nut from wayback…


Gigajoe quote
«You can press Windows + R keys simultaneously to open Windows Run.
type  compmgmt.msc, and hit Enter to open it.
«

Yes, I did this after plugging the STM32 into the USB port. It did not show up in Device Manager Ports. Do any of the buttons on the STM32 board have to be pressed?

Yes, you have to keep the BOOT button pressed while plugging in the USB C cable to the STM32 board, to enter DFU mode. Check post #78 on page 4 of this thread, I pointed Bob around three months ago to a website that explains the STM32 flashing procedure in detail. Or ask on the STM32duino forum.

« Last Edit: October 14, 2021, 09:40:22 pm by AndrewBCN »


Logged


you need drivers to support com port mode , and  DFU programming mode, drivers installing with  cube prog,  or separately, able to find it in folder …STM32CubeProgDrivers — where CUBE Prog was installed

so when STM plug-in and running it will be COM port, press -0 and reset — DFU mode, if no com port, and DFU — as exclamation mark in devices — drivers not installed (or STM not recognized )

try restart PC if drivers was installed ….

UPD:  just a note ,  if ublox connected to PA9 PA10, as on PDF diagram, it possible that board using the same pins for USB, it depends on model. so STM will not recognized in OS.

« Last Edit: October 14, 2021, 11:29:08 pm by GigaJoe »


Logged

The following users thanked this post: enut11


Gigajoe quote
«You can press Windows + R keys simultaneously to open Windows Run.
type  compmgmt.msc, and hit Enter to open it.
«

Yes, I did this after plugging the STM32 into the USB port. It did not show up in Device Manager Ports. Do any of the buttons on the STM32 board have to be pressed?

Yes, you have to keep the BOOT button pressed while plugging in the USB C cable to the STM32 board, to enter DFU mode. Check post #78 on page 4 of this thread, I pointed Bob around three months ago to a website that explains the STM32 flashing procedure in detail. Or ask on the STM32duino forum.

Thanks for the reminder @AndrewBCN. Looks like I skipped over that when I was scanning the thread to catch up on what I had missed.

I must say that Win10 is very fussy in handling the STM32 via USB, more often than not rejecting and refusing to talk to it.

Anyway, using reply #78, I managed to to get Blinky to work properly this time. I then loaded the ASCII program and got the following response in Monitor:

«ASCII Table ~ Character Map
!, dec: 33, hex: 21, oct: 41, bin: 100001
«, dec: 34, hex: 22, oct: 42, bin: 100010
#, dec: 35, hex: 23, oct: 43, bin: 100011
$, dec: 36, hex: 24, oct: 44, bin: 100100
%, dec: 37, hex: 25, oct: 45, bin: 100101
&, dec: 38, hex: 26, oct: 46, bin: 100110
‘, dec: 39, hex: 27, oct: 47, bin: 100111
(, dec: 40, hex: 28, oct: 50, bin: 101000
), dec: 41, hex: 29, oct: 51, bin: 101001″ plus a lot more…

So that appears to work.

I believe I am now ready to tackle the REAL program to control my GPSDSO.  :)


Logged

an electronics nut from wayback…

The following users thanked this post: AndrewBCN


@AndrewBCN quote:
«PS: I have just noticed that STM32 Core version 2.1 has just been released a few days ago. It is the version I recommend for use with the STM32 GPSDO firmware.
« Last Edit: October 11, 2021, 07:32:22 pm by AndrewBCN »»

The latest Core for my Black Pill F401CC is version 1.9. Is this a problem?
enut11


Logged

an electronics nut from wayback…


@AndrewBCN quote:
«PS: I have just noticed that STM32 Core version 2.1 has just been released a few days ago. It is the version I recommend for use with the STM32 GPSDO firmware.
« Last Edit: October 11, 2021, 07:32:22 pm by AndrewBCN »»

The latest Core for my Black Pill F401CC is version 1.9. Is this a problem?
enut11

Yes. Actually it’s the other way around, the earliest Core for the Black Pill F401CC was version 1.9. Please uninstall version 1.9 (simply delete the whole directory) and then reinstall 2.1 from this link: https://github.com/stm32duino/Arduino_Core_STM32/releases/tag/2.1.0

« Last Edit: October 15, 2021, 11:04:34 am by AndrewBCN »


Logged


Anyway, using reply #78, I managed to to get Blinky to work properly this time. I then loaded the ASCII program and got the following response in Monitor:

«ASCII Table ~ Character Map
!, dec: 33, hex: 21, oct: 41, bin: 100001
«, dec: 34, hex: 22, oct: 42, bin: 100010
#, dec: 35, hex: 23, oct: 43, bin: 100011
$, dec: 36, hex: 24, oct: 44, bin: 100100
%, dec: 37, hex: 25, oct: 45, bin: 100101
&, dec: 38, hex: 26, oct: 46, bin: 100110
‘, dec: 39, hex: 27, oct: 47, bin: 100111
(, dec: 40, hex: 28, oct: 50, bin: 101000
), dec: 41, hex: 29, oct: 51, bin: 101001″ plus a lot more…

So that appears to work.

I believe I am now ready to tackle the REAL program to control my GPSDSO.  :)

Excellent!  :-+ Well done.


Logged


You can press Windows + R keys simultaneously to open Windows Run.
type  compmgmt.msc, and hit Enter to open it.

For directly to the Device Manager:

C:>devmgmt.msc


Logged



Logged


A few months ago I bought a Neo-M8N board and a cheap Bingfu puck antenna. Both together were less than $25 from Amazon (of course I threw in some other random cheap item to get free shipping).

Indoors and 3 meters from any window, the GPS module alone did struggle to connect. But once I hooked up the antenna it was able to connect in a matter of minutes. As far as I can tell from the u-blox software the part is genuine.

https://www.eevblog.com/forum/chat/what-did-you-buy-today-post-your-latest-purchase!/msg3612283

« Last Edit: October 15, 2021, 02:19:43 pm by rdl »


Logged


A few months ago I bought a Neo-M8N board…

Oh, I hadn’t realized that those little guys had a micro USB connector on them too.
I have a NEO-5M (that was discontinued ~2014?) on a fleet surveilance board that I removed from a friend’s 2nd hand van!
I forget where the SMA antenna went to. In any case, with a 1/4 wave antenna it can barely pick up the time sometimes.
So I ordered the NEO-M9N and an active antenna.


Logged


Понравилась статья? Поделить с друзьями:

Читайте также:

  • Error no database selected hibernate
  • Error no connection принтер
  • Error no connection to the database itop
  • Error launching winpty agent
  • Error no configuration file found no default or ui configuration directive found

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии