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.

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

iotlab-m3 nodes always fail on flashing #6043

Closed
kYc0o opened this issue Nov 2, 2016 · 9 comments
Closed

iotlab-m3 nodes always fail on flashing #6043

kYc0o opened this issue Nov 2, 2016 · 9 comments
Assignees
Labels
Area: tools Area: Supplementary tools Platform: ARM Platform: This PR/issue effects ARM-based platforms Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@kYc0o
Copy link
Contributor

kYc0o commented Nov 2, 2016

While testing the release specs I found that the iotlab-m3 is flashed correctly, but I always have an error.

Can anyone else confirm this behaviour on 2016.10-RC1?

My config is:

Open On-Chip Debugger 0.9.0-dev-gbdd8312 (2016-01-12-18:06)

And

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.2.1 20151202 (release) [ARM/embedded-5-branch revision 231848]

I'm in a Debian jessie machine this time ;-)

@kYc0o kYc0o added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Platform: ARM Platform: This PR/issue effects ARM-based platforms Area: tools Area: Supplementary tools labels Nov 2, 2016
@kYc0o kYc0o added this to the Release 2016.10 milestone Nov 2, 2016
@thomaseichinger
Copy link
Member

@kYc0o What is the actual error (message)?

@kYc0o
Copy link
Contributor Author

kYc0o commented Nov 2, 2016

Sorry I forgot to put it in the description:

/home/facosta/git/RIOT-OS/RIOT/tests/emb6/../../Makefile.include:329: recipe for target 'flash' failed
make: *** [flash] Error 1

@miri64
Copy link
Member

miri64 commented Nov 3, 2016

That was one of my main issues, when trying to implement a working test framework ;-)

@kYc0o
Copy link
Contributor Author

kYc0o commented Nov 7, 2016

Just tested on OS X with Open On-Chip Debugger 0.10.0-dev-gdfc6658 (2016-02-18-22:16) and it works as expected.

@OlegHahm
Copy link
Member

OlegHahm commented Nov 8, 2016

The reason is probably the old OpenOCD version. See discussion in #2472.

@kYc0o
Copy link
Contributor Author

kYc0o commented Nov 8, 2016

Yes, that's the problem. We can then say somewhere (wiki?) that we recommend OpenOCD 0.10 or higher?

@OlegHahm
Copy link
Member

OlegHahm commented Nov 8, 2016

Actually, I thought we already did this, but I cannot find it. So, 👍 for recommending OpenOCD > 0.9 somewhere.

@kYc0o
Copy link
Contributor Author

kYc0o commented Nov 10, 2016

Done in the wiki.

@kYc0o kYc0o closed this as completed Nov 10, 2016
@Joe-sae
Copy link

Joe-sae commented Aug 3, 2017

I have install RIOT and openocd followed wed size https://github.com/RIOT-OS/RIOT/wiki/OpenOCD and https://github.com/RIOT-OS/RIOT/wiki.
anything is OK.
But it is fail to make flash after I connect ST-LINK with STM32 broad,.
it shows that Error: corrupted fifo read pointer 0xe7fee7fe.
could you give me some help ?


next information is catching in Ubuntu.

$ make flash
Building application "test_stm32" for "nucleo-f103" with MCU "stm32f1".

"make" -C /home/joe/win_share/RIOT-master/boards/nucleo-f103
"make" -C /home/joe/win_share/RIOT-master/core
"make" -C /home/joe/win_share/RIOT-master/cpu/stm32f1
"make" -C /home/joe/win_share/RIOT-master/cpu/cortexm_common
"make" -C /home/joe/win_share/RIOT-master/cpu/cortexm_common/periph
"make" -C /home/joe/win_share/RIOT-master/cpu/stm32_common
"make" -C /home/joe/win_share/RIOT-master/cpu/stm32_common/periph
"make" -C /home/joe/win_share/RIOT-master/cpu/stm32f1/periph
"make" -C /home/joe/win_share/RIOT-master/drivers
"make" -C /home/joe/win_share/RIOT-master/drivers/periph_common
"make" -C /home/joe/win_share/RIOT-master/sys
"make" -C /home/joe/win_share/RIOT-master/sys/auto_init
"make" -C /home/joe/win_share/RIOT-master/sys/isrpipe
"make" -C /home/joe/win_share/RIOT-master/sys/newlib_syscalls_default
"make" -C /home/joe/win_share/RIOT-master/sys/pm_layered
"make" -C /home/joe/win_share/RIOT-master/sys/tsrb
"make" -C /home/joe/win_share/RIOT-master/sys/uart_stdio
text data bss dec hex filename
8492 136 2756 11384 2c78 /home/joe/win_share/RIOT-master/examples/test_stm32/bin/nucleo-f103/test_stm32.elf
/home/joe/win_share/RIOT-master/dist/tools/openocd/openocd.sh flash

Flashing Target

Open On-Chip Debugger 0.10.0+dev-00169-g02bc718 (2017-08-01-13:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v27 API v2 SWIM v6 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.256458
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
TargetName Type Endian TapName State


0* stm32f1x.cpu hla_target little stm32f1x.cpu halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080003f4 msp: 0x20000200
auto erase enabled
Info : device id = 0x10036414
Info : flash size = 512kbytes
Error: corrupted fifo read pointer 0xe7fee7fe
Error: timed out while waiting for target halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x61000003 pc: 0x08001040 msp: 0x20000180
Error: error waiting for target flash write algorithm
Error: error writing to flash at address 0x08000000 at offset 0x00000000

/home/joe/win_share/RIOT-master/examples/test_stm32/../../Makefile.include:370: recipe for target 'flash' failed
make: *** [flash] Error 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: tools Area: Supplementary tools Platform: ARM Platform: This PR/issue effects ARM-based platforms Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

No branches or pull requests

5 participants