Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 11:17 01 Aug 2025 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : HELP NEEDED WITH A NEW F4

Author Message
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 986
Posted: 04:10am 21 Feb 2023
Copy link to clipboard 
Print this post

I purchased some STM32F4 black boards and I have found one of the boards will not program via the ST software. I cannot get the unit to register in the cube software like the other units but if I take off the BT0 and BT1 links the screen displays this:




Can anyone offer any ideas?

OA47
 
disco4now

Guru

Joined: 18/12/2014
Location: Australia
Posts: 1003
Posted: 05:26am 21 Feb 2023
Copy link to clipboard 
Print this post

Are you reconnecting the power with BT0 and BT1 strapped, I have found just resetting via the RST key can be a bit hit and miss, but a full power off/on always works.
Regards
Gerry
Latest F4 Latest H7 FotS
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 986
Posted: 05:45am 21 Feb 2023
Copy link to clipboard 
Print this post

  Quote  Are you reconnecting the power with BT0 and BT1 strapped, I have found just resetting via the RST key can be a bit hit and miss, but a full power off/on always works.


Definitely using the usb plug to reset the F4 with BT0 & BT1 Strapped.

OA47
 
disco4now

Guru

Joined: 18/12/2014
Location: Australia
Posts: 1003
Posted: 07:05am 21 Feb 2023
Copy link to clipboard 
Print this post

Only other thing I can think of is checking continuity from the BT0 pin to pin 94 on the actual chip itself. Also BT1 to pin 37 on the actual chip.
Latest F4 Latest H7 FotS
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 986
Posted: 08:15am 21 Feb 2023
Copy link to clipboard 
Print this post

  Quote  Only other thing I can think of is checking continuity from the BT0 pin to pin 94 on the actual chip itself. Also BT1 to pin 37 on the actual chip.


Was thinking of that and I will check it out.

0A47
 
JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 4044
Posted: 08:36am 21 Feb 2023
Copy link to clipboard 
Print this post

Does the chip have the right markings for the CPU it's supposed to be?

John
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6283
Posted: 08:45am 21 Feb 2023
Copy link to clipboard 
Print this post

Somewhere in the dim past I remember some modules needing non-standard settings for BT0 and BT1.
I forget what modules were the ones we were having trouble with but it is worth trying a variety of settings.

Jim
VK7JH
MMedit
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 986
Posted: 09:38pm 21 Feb 2023
Copy link to clipboard 
Print this post

@Disco4now
I have traced the BT0 and BT1 pins back to the chip via R23 and R33 so no luck there.

@JohnS
I can confirm that the chip is the same as the others

@Jim
I grabbed another board of the same build (DevEBox V33) and checked the pin configuration and it is recognized by the Cubeprogrammer.

I did reflow the ARM chip and changed the crystal and battery but still the software will not recognize the board. It is strange that there is life when the screen above shows.

OA47
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6283
Posted: 09:51pm 21 Feb 2023
Copy link to clipboard 
Print this post

It does appear to have a program installed.
If you can't erase it and load your own, perhaps whoever loaded the original program made it write protected in which case I don't know where to go next.

Jim
VK7JH
MMedit
 
JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 4044
Posted: 11:12pm 21 Feb 2023
Copy link to clipboard 
Print this post

I hit something which might be along the same lines and ended up using both Texane stlink & qstlink / qstlink2 (one or other fixed whatever it was).

I think the issue was probably corrupted option byte(s).

John
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 986
Posted: 12:35am 22 Feb 2023
Copy link to clipboard 
Print this post

  Quote  I hit something which might be along the same lines and ended up using both Texane stlink & qstlink / qstlink2 (one or other fixed whatever it was).

I think the issue was probably corrupted option byte(s).


John could you elaborate on the software you used?

OA47
 
OA47

Guru

Joined: 11/04/2012
Location: Australia
Posts: 986
Posted: 02:43am 22 Feb 2023
Copy link to clipboard 
Print this post

  Quote  It does appear to have a program installed.
If you can't erase it and load your own, perhaps whoever loaded the original program made it write protected in which case I don't know where to go next.


Jim, the unit is fresh out of the bag from the supplier. The units that have programmed with MMBasic are still recognised with Cube software.

OA47
 
JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 4044
Posted: 09:09am 22 Feb 2023
Copy link to clipboard 
Print this post

  OA47 said  
  Quote  I hit something which might be along the same lines and ended up using both Texane stlink & qstlink / qstlink2 (one or other fixed whatever it was).

I think the issue was probably corrupted option byte(s).


John could you elaborate on the software you used?

OA47

I think it was before OpenOCD had SWD support, or it just couldn't recover from whatever weirdness had occurred, about 9 years ago. You might well just be able to use oocd now.

Looks like Texane stlink is now https://github.com/stlink-org/stlink

I think the other was https://github.com/fpoussin/QStlink2

John
 
Print this page


To reply to this topic, you need to log in.

The Back Shed's forum code is written, and hosted, in Australia.
© JAQ Software 2025