micro-ROS / micro-ROS/micro_ros_setup

What is the reason for transaction stalled error while running flash_firmware.sh

Open
#798 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
509
Forks
183
Avg merge
22h 26m
Merged PRs (30d)
7

Description

I am getting the following error while running `ros2 run micro_ros_setup flash_firmware.sh`
```
Flashing firmware for zephyr platform olimex-stm32-e407
Bus 003 Device 018: ID 15ba:002a Olimex OpenOCD JTAG ARM-USB-TINY-H
Open On-Chip Debugger 0.11.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select '.
Info : clock speed 2000 kHz
Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x4)
Info : JTAG tap: [stm32f4x.bs](http://stm32f4x.bs/) tap/device found: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Info : stm32f4x.cpu: hardware has 0 breakpoints, 0 watchpoints
Info : starting gdb server for stm32f4x.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : JTAG tap: stm32f4x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x4)
Info : JTAG tap: [stm32f4x.bs](http://stm32f4x.bs/) tap/device found: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)
Error: Could not find MEM-AP to control the core
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Info : DAP transaction stalled (WAIT) - slowing down
Error: Failed to enable the FPB
TARGET: stm32f4x.cpu - Not halted
[ros2run]: Process exited with failure 1
```

I have the STM32-E407 Board and flashing via ARM-USB-TINY-H. At times it works after I press reset for some time. And after sometime if I try to flash again with a new program this happens.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the `ros2 run micro_ros_setup flash_firmware.sh` entry point and inspect how it invokes OpenOCD for the Olimex STM32-E407. Reproduce the intermittent failure with the ARM-USB-TINY-H and compare runs where pressing reset allows flashing. Done means identifying the cause of the stalled transaction and documenting reliable flashing steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
embedded-iot
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.