Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Nucleo-F103RB: Board fails to flash #854

Closed
6 tasks done
fadedbee opened this issue Jan 8, 2020 · 5 comments · Fixed by #1113
Closed
6 tasks done

Nucleo-F103RB: Board fails to flash #854

fadedbee opened this issue Jan 8, 2020 · 5 comments · Fixed by #1113
Assignees
@Ant-ON @Nightwalker-87
Labels
bug/fixed bug/regression component/st-util error/flash-loader os/linux programmer/STLINK/V2-1 V2-1 status/resolved target/stm32f1
Milestone
v1.7.0

Comments

@fadedbee
Copy link

fadedbee commented Jan 8, 2020 •
edited by Nightwalker-87
Loading

  • Programmer/board type: e.g Stlink/v2-1-onboard
  • Programmer firmware version: From programmer's (mbed) USB Mass Storage NODE_F103RB/DETAILS.TXT: Version: 0221, Build: Jun 23 2017 17:43:45.
  • Operating system: Linux, Ubuntu 16.04
  • Stlink tools version: 3690de9
  • Stlink commandline tool name: st-util
  • Target chip (and optional board): e.g STM32F103RB (NUCLEO-F103RB)

The flashing of the onboard STM32F103RB fails.

Output:

fadedbee@purple:~/github/stlink$ ./build/Release/src/gdbserver/st-util
st-util 1.5.1-50-g3690de9
2020-01-08T09:35:16 INFO common.c: Loading device parameters....
2020-01-08T09:35:16 INFO common.c: Device connected is: F1 Medium-density device, id 0x20036410
2020-01-08T09:35:16 INFO common.c: SRAM size: 0x5000 bytes (20 KiB), Flash: 0x20000 bytes (128 KiB) in pages of 1024 bytes
2020-01-08T09:35:16 INFO gdb-server.c: Chip ID is 00000410, Core ID is  1ba01477.
2020-01-08T09:35:16 INFO gdb-server.c: Listening at *:4242...
2020-01-08T09:49:00 INFO gdb-server.c: Found 6 hw breakpoint registers
2020-01-08T09:49:00 INFO gdb-server.c: GDB connected.
2020-01-08T09:49:06 INFO common.c: Attempting to write 1024 (0x400) bytes to stm32 address: 134217728 (0x8000000)
Flash page at addr: 0x08000000 erased
2020-01-08T09:49:06 INFO common.c: Finished erasing 1 pages of 1024 (0x400) bytes
2020-01-08T09:49:06 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2020-01-08T09:49:06 INFO flash_loader.c: Successfully loaded flash loader in sram

2020-01-08T09:49:06 INFO common.c: Starting verification of write complete
2020-01-08T09:49:06 INFO common.c: Flash written and verified! jolly good!
2020-01-08T09:49:06 INFO common.c: Attempting to write 1024 (0x400) bytes to stm32 address: 134218752 (0x8000400)
Flash page at addr: 0x08000400 erased
2020-01-08T09:49:06 INFO common.c: Finished erasing 1 pages of 1024 (0x400) bytes
2020-01-08T09:49:06 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2020-01-08T09:49:06 INFO flash_loader.c: Successfully loaded flash loader in sram
2020-01-08T09:49:06 ERROR flash_loader.c: write error, count == 511
2020-01-08T09:49:06 ERROR common.c: stlink_flash_loader_run(0x8000400) failed! == -1
^C

fadedbee@purple:~/vx4000-platform/nucleo-f103rb-blinky$ arm-none-eabi-gdb build/nucleo-f103rb-blinky.elf 
GNU gdb (GNU Tools for Arm Embedded Processors 7-2018-q3-update) 8.1.0.20180315-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-linux-gnu --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/nucleo-f103rb-blinky.elf...done.
(gdb) target extended-remote :4242
Remote debugging using :4242
0x080021d8 in ?? ()
(gdb) load
Loading section .isr_vector, size 0x10c lma 0x8000000
Loading section .text, size 0xe4c lma 0x800010c
Loading section .rodata, size 0x2c lma 0x8000f58
Loading section .init_array, size 0x4 lma 0x8000f84
Loading section .fini_array, size 0x4 lma 0x8000f88
Loading section .data, size 0xc lma 0x8000f8c
Error finishing flash operation
(gdb) quit

Expected/description:

I had expected the flashing to complete successfully.
@fadedbee
Copy link
Author

fadedbee commented Jan 8, 2020

I was able to create an mbed-os-example-blinky project and drop into the nucleo's USB Mass Storage. This then automatically flashed it onto the F103RB.

The blinky is now running, so I don't think that the F103RB is faulty.

@SourceLink
Copy link

I also encountered the same problem, the program uses mdk to compile and download without problems

@Nightwalker-87 Nightwalker-87 added this to the General milestone Feb 19, 2020
@Nightwalker-87 Nightwalker-87 modified the milestones: General, v1.6.1, Feedback required Feb 21, 2020
@Nightwalker-87 Nightwalker-87 self-assigned this Feb 21, 2020
@Nightwalker-87 Nightwalker-87 removed their assignment Mar 21, 2020
@Nightwalker-87 Nightwalker-87 modified the milestones: Feedback required, Device issues Mar 31, 2020
@Nightwalker-87 Nightwalker-87 added programmer/STLINK/V2-1 V2-1 and removed programmer/STLINK/V2 V2 / V2-A / V2-B labels Mar 31, 2020
@Nightwalker-87 Nightwalker-87 changed the title Fails to flash NUCLEO-F103RB. Nucleo-F103RB: Board fails to flash Mar 31, 2020
@Nightwalker-87 Nightwalker-87 modified the milestones: Device issues, ERROR flash_loader.c: write error Apr 6, 2020
@Nightwalker-87 Nightwalker-87 modified the milestones: e) ERROR flash_loader.c: write error, a) Old issues Mar 11, 2021
@Nightwalker-87
Copy link
Member

I have tried to reproduce this issue with under mostly identical circumstances:

  • v1.5.1 / commit: 3690de9
  • Programmer: STLink/V2-clone Firmware V2J37S7
  • Board: STM32F103C8T6

Looking at the output reveals that st-util and gdb appear to deliver the expected output:

$ ./build/Release/src/gdbserver/st-util 
st-util 1.5.1-50-g3690de9
2021-03-12T00:05:13 INFO common.c: Loading device parameters....
2021-03-12T00:05:13 INFO common.c: Device connected is: F1 Medium-density device, id 0x20036410
2021-03-12T00:05:13 INFO common.c: SRAM size: 0x5000 bytes (20 KiB), Flash: 0x10000 bytes (64 KiB) in pages of 1024 bytes
2021-03-12T00:05:13 INFO gdb-server.c: Chip ID is 00000410, Core ID is  2ba01477.
2021-03-12T00:05:13 INFO gdb-server.c: Listening at *:4242...
2021-03-12T00:16:36 INFO gdb-server.c: Found 6 hw breakpoint registers
2021-03-12T00:16:36 INFO gdb-server.c: GDB connected.
2021-03-12T00:16:42 INFO common.c: Attempting to write 1024 (0x400) bytes to stm32 address: 134217728 (0x8000000)
Flash page at addr: 0x08000000 erased
2021-03-12T00:16:42 INFO common.c: Finished erasing 1 pages of 1024 (0x400) bytes
2021-03-12T00:16:42 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2021-03-12T00:16:42 INFO flash_loader.c: Successfully loaded flash loader in sram

2021-03-12T00:16:42 INFO common.c: Starting verification of write complete
2021-03-12T00:16:42 INFO common.c: Flash written and verified! jolly good!
2021-03-12T00:16:42 INFO common.c: Attempting to write 1024 (0x400) bytes to stm32 address: 134218752 (0x8000400)
Flash page at addr: 0x08000400 erased
2021-03-12T00:16:42 INFO common.c: Finished erasing 1 pages of 1024 (0x400) bytes
2021-03-12T00:16:42 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2021-03-12T00:16:42 INFO flash_loader.c: Successfully loaded flash loader in sram

2021-03-12T00:16:42 INFO common.c: Starting verification of write complete
2021-03-12T00:16:42 INFO common.c: Flash written and verified! jolly good!
2021-03-12T00:16:42 INFO common.c: Attempting to write 1024 (0x400) bytes to stm32 address: 134219776 (0x8000800)
Flash page at addr: 0x08000800 erased
2021-03-12T00:16:42 INFO common.c: Finished erasing 1 pages of 1024 (0x400) bytes
2021-03-12T00:16:42 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2021-03-12T00:16:42 INFO flash_loader.c: Successfully loaded flash loader in sram

2021-03-12T00:16:42 INFO common.c: Starting verification of write complete
2021-03-12T00:16:42 INFO common.c: Flash written and verified! jolly good!
2021-03-12T00:16:42 INFO common.c: Attempting to write 1024 (0x400) bytes to stm32 address: 134220800 (0x8000c00)
Flash page at addr: 0x08000c00 erased
2021-03-12T00:16:42 INFO common.c: Finished erasing 1 pages of 1024 (0x400) bytes
2021-03-12T00:16:42 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2021-03-12T00:16:42 INFO flash_loader.c: Successfully loaded flash loader in sram

2021-03-12T00:16:42 INFO common.c: Starting verification of write complete
2021-03-12T00:16:42 INFO common.c: Flash written and verified! jolly good!
2021-03-12T00:17:27 ERROR gdb-server.c: cannot recv: -2
2021-03-12T00:17:27 INFO gdb-server.c: Listening at *:4242...


$ gdb-multiarch /[...]/Blinker.elf 
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /[...]/Blinker.elf...
(No debugging symbols found in /[...]/Blinker.elf)
(gdb) load
You can't do that when your target is `exec'
(gdb) target extended-remote :4242
Remote debugging using :4242
0xfffffffe in ?? ()
(gdb) load
Loading section .isr_vector, size 0x130 lma 0x8000000
Loading section .text, size 0xbac lma 0x8000130
Loading section .rodata, size 0x74 lma 0x8000cdc
Loading section .init_array, size 0x4 lma 0x8000d50
Loading section .fini_array, size 0x4 lma 0x8000d54
Loading section .data, size 0x68 lma 0x8000d58
Start address 0x080002b4, load size 3520
Transfer rate: 16 KB/sec, 586 bytes/write.
(gdb) quit
A debugging session is active.

	Inferior 1 [Remote target] will be killed.

Quit anyway? (y or n) y

@Nightwalker-87 Nightwalker-87 self-assigned this Mar 11, 2021
@Nightwalker-87 Nightwalker-87 modified the milestones: Old issues, v1.6.2 Mar 12, 2021
@Nightwalker-87 Nightwalker-87 modified the milestones: Old issues, v1.6.2 Mar 22, 2021
@Nightwalker-87
Copy link
Member

@Ant-ON What about this one. Do you have an idea?

@Ant-ON
Copy link
Collaborator

Ant-ON commented Mar 25, 2021

@Nightwalker-87 Most likely fixed by #1113

@Nightwalker-87 Nightwalker-87 mentioned this issue Mar 25, 2021
Merged
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Mar 25, 2021
@Nightwalker-87 Nightwalker-87 moved this to Done in Release v1.7.0 Apr 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Ant-ON Ant-ON

@Nightwalker-87 Nightwalker-87

Labels
bug/fixed bug/regression component/st-util error/flash-loader os/linux programmer/STLINK/V2-1 V2-1 status/resolved target/stm32f1
Projects
No open projects
Release v1.7.0
Status: Done
Milestone
v1.7.0
Development

Successfully merging a pull request may close this issue.

Flash loader rework Ant-ON/stlink
4 participants
@Ant-ON @Nightwalker-87 @SourceLink @fadedbee