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

Can't reset using reset button, and communicate via JTAG after flashing hello-world example #18750

Closed
omicronns opened this issue Oct 15, 2022 · 4 comments · Fixed by #19050
Closed

Can't reset using reset button, and communicate via JTAG after flashing hello-world example #18750

omicronns opened this issue Oct 15, 2022 · 4 comments · Fixed by #19050

Comments

@omicronns
Copy link

omicronns commented Oct 15, 2022 •
edited
Loading

Hi,

I'm playing with RIOT, and I'm experiencing strange behavior after flashing RIOT binary onto LAUNCHXL-CC1352R1.

After flashing hello-world example I can't connect via openocd (JTAG) with the board anymore. I can recover using uniflash tool from TI to erase the flash. Also physical reset button present on the board stops working - board continues to run despite button being pressed.

Is this expected behavior? Does RIOT-OS reconfigure JTAG and reset button in runtime so it is no longer operational?

Reset button behavior is also present for the nRF52840-DK development board.

Flashing the board for the first time:

make BOARD=cc1352-launchpad flash
Building application "hello-world" for "cc1352-launchpad" with MCU "cc26x2_cc13x2".

"make" -C /home/koadas/Documents/work/projects/RIOT/boards/cc1352-launchpad
"make" -C /home/koadas/Documents/work/projects/RIOT/boards/common/init
"make" -C /home/koadas/Documents/work/projects/RIOT/core
"make" -C /home/koadas/Documents/work/projects/RIOT/core/lib
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26x2_cc13x2
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26x2_cc13x2/periph
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26xx_cc13xx
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26xx_cc13xx/periph
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cortexm_common
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cortexm_common/periph
"make" -C /home/koadas/Documents/work/projects/RIOT/drivers
"make" -C /home/koadas/Documents/work/projects/RIOT/drivers/periph_common
"make" -C /home/koadas/Documents/work/projects/RIOT/sys
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/auto_init
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/div
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/libc
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/malloc_thread_safe
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/newlib_syscalls_default
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/stdio_uart
   text    data     bss     dec     hex filename
   8948     112    2288   11348    2c54 /home/koadas/Documents/work/projects/RIOT/examples/hello-world/bin/cc1352-launchpad/hello-world.elf
/home/koadas/Documents/work/projects/RIOT/dist/tools/openocd/openocd.sh flash /home/koadas/Documents/work/projects/RIOT/examples/hello-world/bin/cc1352-launchpad/hello-world.elf
### Flashing Target ###
Open On-Chip Debugger 0.11.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
DEPRECATED! use 'adapter srst pulse_width' not 'adapter_nsrst_assert_width'
DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay'
DEPRECATED! use 'adapter speed' not 'adapter_khz'
adapter speed: 1000 kHz

Info : XDS110: connected
Info : XDS110: vid/pid = 0451/bef3
Info : XDS110: firmware version = 3.0.0.19
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 1000 kHz
Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Info : cc26x2.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for cc26x2.cpu on 0
Info : Listening on port 33997 for gdb connections
    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* cc26x2.cpu         cortex_m   little cc26x2.cpu         halted

Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000fb0 msp: 0x20001080
auto erase enabled
wrote 16384 bytes from file /home/koadas/Documents/work/projects/RIOT/examples/hello-world/bin/cc1352-launchpad/hello-world.elf in 1.457139s (10.980 KiB/s)

verified 9060 bytes in 0.090556s (97.704 KiB/s)

Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
shutdown command invoked
Info : XDS110: disconnected
Done flashing

After first flash:

make BOARD=cc1352-launchpad flash
Building application "hello-world" for "cc1352-launchpad" with MCU "cc26x2_cc13x2".

"make" -C /home/koadas/Documents/work/projects/RIOT/boards/cc1352-launchpad
"make" -C /home/koadas/Documents/work/projects/RIOT/boards/common/init
"make" -C /home/koadas/Documents/work/projects/RIOT/core
"make" -C /home/koadas/Documents/work/projects/RIOT/core/lib
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26x2_cc13x2
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26x2_cc13x2/periph
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26xx_cc13xx
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cc26xx_cc13xx/periph
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cortexm_common
"make" -C /home/koadas/Documents/work/projects/RIOT/cpu/cortexm_common/periph
"make" -C /home/koadas/Documents/work/projects/RIOT/drivers
"make" -C /home/koadas/Documents/work/projects/RIOT/drivers/periph_common
"make" -C /home/koadas/Documents/work/projects/RIOT/sys
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/auto_init
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/div
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/libc
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/malloc_thread_safe
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/newlib_syscalls_default
"make" -C /home/koadas/Documents/work/projects/RIOT/sys/stdio_uart
   text    data     bss     dec     hex filename
   8948     112    2288   11348    2c54 /home/koadas/Documents/work/projects/RIOT/examples/hello-world/bin/cc1352-launchpad/hello-world.elf
/home/koadas/Documents/work/projects/RIOT/dist/tools/openocd/openocd.sh flash /home/koadas/Documents/work/projects/RIOT/examples/hello-world/bin/cc1352-launchpad/hello-world.elf
### Flashing Target ###
Open On-Chip Debugger 0.11.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
DEPRECATED! use 'adapter srst pulse_width' not 'adapter_nsrst_assert_width'
DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay'
DEPRECATED! use 'adapter speed' not 'adapter_khz'
adapter speed: 1000 kHz

Info : XDS110: connected
Info : XDS110: vid/pid = 0451/bef3
Info : XDS110: firmware version = 3.0.0.19
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 1000 kHz
Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Info : cc26x2.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for cc26x2.cpu on 0
Info : Listening on port 37499 for gdb connections
    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* cc26x2.cpu         cortex_m   little cc26x2.cpu         running

Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000930 msp: 0x20000200
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Failed to write memory and, additionally, failed to find out where
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Warn : target was in unknown state when halt was requested
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: failed erasing sectors 0 to 1
auto erase enabled
Info : XDS110: disconnected
make: *** [/home/koadas/Documents/work/projects/RIOT/examples/hello-world/../../Makefile.include:838: flash] Error 1
@omicronns omicronns closed this as not planned Won't fix, can't repro, duplicate, stale Oct 15, 2022
@omicronns omicronns reopened this Oct 15, 2022
@SpooniSpoon
Copy link

Hi,
I have the same issue. Any idee so far to solve the issue?

@SpooniSpoon SpooniSpoon mentioned this issue Oct 17, 2022
Open
@omicronns
Copy link
Author

I'm using gdb load command to flash the board. Using zephyr hello-world binary I can flash the board multiple times, with RIOT I can only do it once, and then I get an error. It seems to be related with binary content somehow.

I'm using same gdb script for both:

target remote localhost:3333
load

And command lines:

openocd -f board/ti_cc13x2_launchpad.cfg

then:

arm-none-eabi-gdb bin/cc1352-launchpad/hello-world.elf -x gdb.script

or

arm-none-eabi-gdb build/zephyr/zephyr.elf -x gdb.script

@omicronns
Copy link
Author

omicronns commented Oct 18, 2022 •
edited
Loading

It looks like running RIOT binary breaks JTAG connection somehow until I erase the flash with uniflash.

I tried to flash now using telnet connection with openocd, which seems more low-level. I can flash RIOT binary multiple times using commands:

reset init
flash write_image erase bin/cc1352-launchpad/hello-world.elf

But after I run the binary with reset run I can't flash the board anymore using previous commands, I'm getting following openocd output now:

Open On-Chip Debugger 0.11.0
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
cortex_m reset_config vectreset

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : XDS110: connected
Info : XDS110: vid/pid = 0451/bef3
Info : XDS110: firmware version = 3.0.0.19
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 5500 kHz
Info : JTAG tap: cc13x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc13x2.cpu enabled
Info : cc13x2.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for cc13x2.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'telnet' connection on tcp/4444
Info : JTAG tap: cc13x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc13x2.cpu enabled
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000930 msp: 0x20000200
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Failed to write memory and, additionally, failed to find out where
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Warn : target was in unknown state when halt was requested
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: failed erasing sectors 0 to 1
auto erase enabled
Error: Invalid ACK (0) in DAP response
Polling target cc13x2.cpu failed, trying to reexamine
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
...

I can flash multiple times running it in between using both telnet and gdb with zephyr image.

@maribu maribu mentioned this issue Jan 4, 2023
Merged
@maribu
Copy link
Member

maribu commented Jan 4, 2023

With #19050 it should already be possible to flash again with OpenOCD (when using the release candidate or a recent build from OpenOCD's master branch) ... most of the time. I hope I can fix the reset halt so that it doesn't bring the JTAG interface in defunct state but works reliable, as just halt may cause issues if the board already installed IRQ handlers that trigger during flashing... But at least for me it worked 100% of the time anyway with the current state, so this may be better than resorting to uniflash.

Regarding the issue with the reset button on the nRF5x: Try flashing the app in dist/tools/nrf52_resetpin_cfg. The reset pin can be disabled in the persistent MCU config (I don't recall the correct name for it - it was called eFuses in AVR terminology). In case of the nRF5x I am 100% certain that this is not an issue with RIOT, but just some board come out of factory with the reset pin not activated. (And also the nRF5x is known to occasionally wipe the persistent config by accident during flashing. This is particularly annoying as it sets the logic level to 1.8 V by default, and only few debuggers have logic level converts included that are needed to restore the config.)

It may be that the CC13xx / CC26xx also have the reset pin configurable similar to the nRF5x. If so, it would be quite feasible to provide a similar tool to restore the reset config - or maybe even just an OpenOCD script.

@bors bors bot closed this as completed in 89ef35f Jan 13, 2023
@maribu maribu mentioned this issue Jan 18, 2023
Merged
bors bot added a commit that referenced this issue Jan 18, 2023
@bors @maribu
Merge #19167
d5a4380 
19167: boards/common/cc26xx cc13xx: clean up and fix flash configs [backport 2023.01] r=kaspar030 a=maribu

# Backport of #19050

### Contribution description

- Add support for XDS110 debugger via `OPENOCD_DEBUG_ADAPTER=xds110`
- Clean up OpenOCD configs in `boards/common/cc26xx_cc13xx`
    - No longer hardcode the debugger to xds110, but use `OPENOCD_DEBUG_ADATER ?= xds110`
    - Add support for cc13x0, cc13x2, cc26x0
- `boards/cc2650*`: drop custom OpenOCD config in favor of shared one
- add variables needed to support flashing with `PROGRAMMER=jlink`
- allow specifying a custom OpenOCD command to bring the device to a halt state, as the default `reset halt` (which causes a second reset) is causing issues with the ICEPick JTAG routers in the CC26xx - CC13xx devices
- Use `halt` instead of `reset halt` for CC26xx / CC13xx boards in OpenOCD to avoid issues in flashing

### Testing procedure

```
make BOARD=cc2650-launchpad -C examples/default flash
```

Should now work. The same should still work for other cc26xx cc13xx boards.

### Issues/PRs references

Partially fixes: #18750

Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

boards/common/cc26xx cc13xx: clean up and fix flash configs maribu/RIOT
3 participants
@maribu @omicronns @SpooniSpoon