"download_apps" doesn't actually work

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Hi,

I've found out that "download_apps" actually doesn't download the firmware to the SPI flash on the BCM4343W_AVN platform. Has anyone experienced anything like this?

Here's my OpenOCD output:

Open On-Chip Debugger 0.10.0-dev-00224-g217aaab-dirty (2016-09-08-15:37)

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 <transport>'.

Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

adapter speed: 2000 kHz

adapter_nsrst_delay: 100

none separate

post_init_43909_setup

Info : Unable to match requested speed 2000 kHz, using 1800 kHz

Info : Unable to match requested speed 2000 kHz, using 1800 kHz

Info : clock speed 1800 kHz

Info : STLINK v2 JTAG v27 API v2 SWIM v6 VID 0x0483 PID 0x3748

Info : using stlink api v2

Info : Target voltage: 3.208372

Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints

26820 bytes written at address 0x20000000

downloaded 26820 bytes in 0.301316s (86.923 KiB/s)

entry_address= 536888685

stack_address= 536907212

buffer_size= 16384

pc (/32): 0x2000456D

Total write size is 383156

writing 16384 bytes at 4096

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x81000000 pc: 0x20005fde msp: 0x20008d7c

loadimage address 536870940 foffset 0 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.178440s (89.666 KiB/s)

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x21000000 pc: 0x20006374 msp: 0x20008c34

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x61000000 pc: 0x200052c4 msp: 0x20008c14

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x41000000 pc: 0x20005540 msp: 0x20008c24

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x61000000 pc: 0x20004a68 msp: 0x20008cf4

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x2100dc00 pc: 0x20005244 msp: 0x20008c1c

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x21000000 pc: 0x200063a2 msp: 0x20008c6c

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x61000000 pc: 0x20004dd2 msp: 0x20008d0c

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x21000000 pc: 0x200063d4 msp: 0x20008d74

****************** Result: Verify after write failed

stm32f4x.cpu: target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x41000000 pc: 0x200063b4 msp: 0x20008d74

===== arm v7m registers

(0) r0 (/32): 0x40000800

(1) r1 (/32): 0x20008D78

(2) r2 (/32): 0x40010000

(3) r3 (/32): 0x00000004

(4) r4 (/32): 0x2000000C

(5) r5 (/32): 0x2000000C

(6) r6 (/32): 0x0000100A

(7) r7 (/32): 0x200068C4

(8) r8 (/32): 0x00000000

(9) r9 (/32): 0x0000100A

(10) r10 (/32): 0x00000000

(11) r11 (/32): 0x2000401C

(12) r12 (/32): 0x00000000

(13) sp (/32): 0x20008D74

(14) lr (/32): 0x200059C7

(15) pc (/32): 0x200063B4

(16) xPSR (/32): 0x41000000

(17) msp (/32): 0x20008D74

(18) psp (/32): 0x00000000

(19) primask (/1): 0x00

(20) basepri (/8): 0x00

(21) faultmask (/1): 0x00

(22) control (/2): 0x00

(23) d0 (/64): 0x0000000000000000

(24) d1 (/64): 0x0000000000000000

(25) d2 (/64): 0x0000000000000000

(26) d3 (/64): 0x0000000000000000

(27) d4 (/64): 0x0000000000000000

(28) d5 (/64): 0x0000000000000000

(29) d6 (/64): 0x0000000000000000

(30) d7 (/64): 0x0000000000000000

(31) d8 (/64): 0x0000000000000000

(32) d9 (/64): 0x0000000000000000

(33) d10 (/64): 0x0000000000000000

(34) d11 (/64): 0x0000000000000000

(35) d12 (/64): 0x0000000000000000

(36) d13 (/64): 0x0000000000000000

(37) d14 (/64): 0x0000000000000000

(38) d15 (/64): 0x0000000000000000

(39) fpscr (/32): 0x00000000

===== Cortex-M DWT registers

(40) dwt_ctrl (/32)

(41) dwt_cyccnt (/32)

(42) dwt_0_comp (/32)

(43) dwt_0_mask (/4)

(44) dwt_0_function (/32)

(45) dwt_1_comp (/32)

(46) dwt_1_mask (/4)

(47) dwt_1_function (/32)

(48) dwt_2_comp (/32)

(49) dwt_2_mask (/4)

(50) dwt_2_function (/32)

(51) dwt_3_comp (/32)

(52) dwt_3_mask (/4)

(53) dwt_3_function (/32)

1 Solution
Anonymous
Not applicable

Problem solved: it was a hardware wiring problem (caused by an error in the datasheet). More info here:

http://cloudconnectkits.org/forum/topic/feedback-error-datasheet

View solution in original post

1 Reply
Anonymous
Not applicable

Problem solved: it was a hardware wiring problem (caused by an error in the datasheet). More info here:

http://cloudconnectkits.org/forum/topic/feedback-error-datasheet