This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

STM32F10x J-Link Failure

I've problems to program STM32 controllers with the J-Link debugger. I'm using the RealView Toolchain V4.11. When I try to download a file to the controller, the programming dialog fails with the following message:

* JLink Info: Found SWD-DP with ID 0x1BA01477
* JLink Info: TPIU fitted.
* JLink Info: FPUnit: 6 code (BP) slots and 2 literal slots
* JLink Info: Found SWD-DP with ID 0x1BA01477
* JLink Info: TPIU fitted.
* JLink Info: FPUnit: 6 code (BP) slots and 2 literal slots

Target info:
------------
Device: STM32F100C4
VTarget = 3.313V
State of Pins:
TCK: 0, TDI: 1, TDO: 1, TMS: 0, TRES: 1, TRST: 1
Hardware-Breakpoints: 6
Software-Breakpoints: 2048
Watchpoints: 4
JTAG speed: 2000 kHz
---
* JLink Info: Found SWD-DP with ID 0x1BA01477
* JLink Info: TPIU fitted.
* JLink Info: FPUnit: 6 code (BP) slots and 2 literal slots
Full Chip Erase Done.
No Algorithm found for: 00000000H - 00001FC3H
Programming skipped!

The Flash Download Programming is set to the appropriate device (STM32F100C4 or STM32F103VB).

In another project with a EnergyMicro EFM32G890 I've got no problems downloading the firmware to the controller. To me this seems to be a firmware issue of the flash downloader.

Parents
  • Hi,

    I think I got a similar problem to yours with the same messages.
    However, I think I have located the problem source.
    After I checked my HW, I discovered that there is a mistake in the MCU library that I used to design the PCB.
    I'm using STM32F103RB chip where pin 55 is JTDO and pin 56 is JNTRST, but they are switched in the library that I used, so the debugger will always get constant signal on JTDO because it is connected to the reset pin in this case.

    Don't know if this will be helpful in your case.

    Regards,
    Alaa

Reply
  • Hi,

    I think I got a similar problem to yours with the same messages.
    However, I think I have located the problem source.
    After I checked my HW, I discovered that there is a mistake in the MCU library that I used to design the PCB.
    I'm using STM32F103RB chip where pin 55 is JTDO and pin 56 is JNTRST, but they are switched in the library that I used, so the debugger will always get constant signal on JTDO because it is connected to the reset pin in this case.

    Don't know if this will be helpful in your case.

    Regards,
    Alaa

Children
No data