Forum > Embedded - ARM

Is this STM32 bricked ???

<< < (2/2)

petex:
ok panic over !!

I normally leave the boot0 jumper in the operational position and gdb server just works. I put the jumper to program mode, reset and then started openocd and there were no errors. I then replaced the usb loader with Blinky, went back to operational mode and everything is ok.

When the USB loader program was loaded and running, it was not possible to halt it and I got a load of errors.....

--- Quote ---Info : stm32f103c8t6.cpu: external reset detected
Polling target stm32f103c8t6.cpu failed, trying to reexamine
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Could not find MEM-AP to control the core
Examination failed, GDB will be halted. Polling again in 100ms
Error: Error connecting DP: cannot read IDR
Polling target stm32f103c8t6.cpu failed, trying to reexamine
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Could not find MEM-AP to control the core
Examination failed, GDB will be halted. Polling again in 300ms
Error: Error connecting DP: cannot read IDR
Polling target stm32f103c8t6.cpu failed, trying to reexamine
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Could not find MEM-AP to control the core
Examination failed, GDB will be halted. Polling again in 700ms
Error: Error connecting DP: cannot read IDR
Polling target stm32f103c8t6.cpu failed, trying to reexamine
Error: Error connecting DP: cannot read IDR

--- End quote ---

The upshot of all of this is I am not sure how to get this particular USB bootloader to work. It is recognised by my PC (win 10) and establishes a virtual com port which spews out messages every so often but nothing else shows up.



--- Quote ---
Why do you give a Linux-based example sith sudo and then start talking about a virtual com port?

--- End quote ---

I have a Raspberry pi running OpenOcd server connected to the STM32 and the PC (win)connects to the Pi.

petex:
I have abandoned Roger's USB bootloader (sorry Roger) and have tried this one:-

https://github.com/mmoskal/uf2-stm32f103/releases/tag/v2.0.1

This runs nicely and I get a new mass storage device added to my computer as drive E: .

A question here, the FPC compiler outputs ,bin, ,hex and ,elf. Is it able to output .uf2 format or do i need a converter ?

MiR:
In Trunk and my Binary Pack this fpc parameter works:

      -Xu        Generate executable in UF2 format  (embedded targets only)

You need to make sure that you set the correct offset for the start of the binary.

See this example in MBF:

SamplesBoardSpecific/Blinky-Bluepill

there I have provided properly preconfigured lpi files.

When using Pico you have to use my binary compiler pack, the latest fixes for pico are not yet in trunk of fpc, I will first have to figure out how to best do interrupts in pico before I ask Florian & Friends to include the fixes as a patch.

petex:
compiler option -Xu does not work with latest compiler package.


--- Quote ---Error: Illegal parameter: -Xu

--- End quote ---

I see you have a blinky uf2 project with a .uf2 file. But if i delete it and re-compile, no .uf2 is built.
I couldn't find any extra params in the project options for this.

MiR:
Maybe the fpc you are using is 'outdated' (which could mean two weeks old or so....), please replace it with this version built today:

http://temp.michael-ring.org/fpc-arm-embedded-3.3.1-win64-20210207.zip

It also brings back the compatibility with older units, use

-WpSTM32F103X8

instead of -Wpbluepill

You will not be able to use MBF with  -WpSTM32F103X8 as the units are not compatible (as you already found out)
 

Navigation

[0] Message Index

[*] Previous page

Go to full version