Opened on 09/21/17 at 06:23:31
Last modified on 09/21/17 at 23:32:50
#3147 assigned defect
DEBUGGER01 Test failure on Beaglebone Black
Reported by: | Chris Johns | Owned by: | Chris Johns |
---|---|---|---|
Priority: | normal | Milestone: | Indefinite |
Component: | score | Version: | 5 |
Severity: | normal | Keywords: | Beaglebone libdebugger |
Cc: | Blocked By: | ||
Blocking: |
Description
Running rtems-test
with a recent u-boot and a current master this failure is reported:
] RTEMS Beagleboard: am335x-based ] ] ] *** BEGIN OF TEST DEBUGGER01 *** ] error: rtems-db: remote not found: test ] [CPU:0] error: rtems-db: test remote: begin ] [CPU:0] rtems-db: remote-debug is on ] [CPU:0] rtems-db: remote running ] [CPU:0] rtems-db: test remote: isconnected: not-connected ] [CPU:0] error: rtems-db: test remote: connect ] [CPU:0] rtems-db: remote running ] [CPU:0] rtems-db: arm debug: (v4.2) ARMv7 [v7, baseline CP14 registers] breakpoints:5 watchpoints:1 ] ] R0 = 0x0000005C R8 = 0x00000000 ] R1 = 0x00000000 R9 = 0x00000000 ] R2 = 0x00000003 R10 = 0x00000000 ] R3 = 0x03078002 R11 = 0x80103778 ] R4 = 0x801029A8 R12 = 0x801029AC ] R5 = 0x00000002 SP = 0x8010CC90 ] R6 = 0x80114950 LR = 0x80015388 ] R7 = 0x00000000 PC = 0x800153CC ] CPSR = 0x20000113 VEC = 0x00000001
Change History (2)
comment:1 follow-up: 2 Changed on 09/21/17 at 15:38:13 by Joel Sherrill
comment:2 Changed on 09/21/17 at 23:32:50 by Chris Johns
Replying to Joel Sherrill:
This is not reported as a failure on erc32, jmr3904, psim, and xilinx_zynq_a9_qemu.
I suspect it is specific to the ARM on the BBB. I will take care of this one.
Note: See
TracTickets for help on using
tickets.
This is not reported as a failure on erc32, jmr3904, psim, and xilinx_zynq_a9_qemu.