BCM943362WCD2 can't support write sflash.bin to external spi flash?

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

cross mob
chch_2120956
Level 3
Level 3
First like received First like given

Dear,

     I want write sflash bin to external flash.(mcu:stm32f103 =>fail;stm32f205 =>ok).

     command:

   make snip.scan-BCM943362WCD2-FreeRTOS-LwIP-SPI   SFLASH=app-download

   message:

Downloading Serial Flash image

Open On-Chip Debugger 0.7.0-dev-00227-g9d47214-dirty (2013-04-16-10:43)

Licensed under GNU GPL v2

For bug reports, read

        http://openocd.sourceforge.net/doc/doxygen/bugs.html

Info : only one transport option; autoselect 'jtag'

trst_and_srst separate srst_nogate trst_push_pull srst_push_pull connect_deasser

t_srst

adapter speed: 1000 kHz

adapter_nsrst_delay: 100

jtag_ntrst_delay: 100

cortex_m3 reset_config vectreset

sflash_write_file

Info : max TCK change to: 30000 kHz

Info : clock speed 1000 kHz

Info : JTAG tap: stm32.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x4)

Warn : JTAG tap: stm32.cpu       UNEXPECTED: 0x4ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x4)

Error: JTAG tap: stm32.cpu  expected 1 of 1: 0x3ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x3)

Info : JTAG tap: stm32.bs tap/device found: 0x790007a3 (mfg: 0x3d1, part: 0x9000

, ver: 0x7)

Warn : JTAG tap: stm32.bs       UNEXPECTED: 0x790007a3 (mfg: 0x3d1, part: 0x9000

, ver: 0x7)

Error: JTAG tap: stm32.bs  expected 1 of 7: 0x06412041 (mfg: 0x020, part: 0x6412

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 2 of 7: 0x06410041 (mfg: 0x020, part: 0x6410

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 3 of 7: 0x16410041 (mfg: 0x020, part: 0x6410

, ver: 0x1)

Error: JTAG tap: stm32.bs  expected 4 of 7: 0x06420041 (mfg: 0x020, part: 0x6420

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 5 of 7: 0x06414041 (mfg: 0x020, part: 0x6414

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 6 of 7: 0x06418041 (mfg: 0x020, part: 0x6418

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 7 of 7: 0x06430041 (mfg: 0x020, part: 0x6430

, ver: 0x0)

Error: Trying to use configured scan chain anyway...

Warn : Bypassing JTAG setup events due to errors

Info : Selecting JTAG transport command set.

Info : AP INIT COMPLETE

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

Info : JTAG tap: stm32.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x4)

Warn : JTAG tap: stm32.cpu       UNEXPECTED: 0x4ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x4)

Error: JTAG tap: stm32.cpu  expected 1 of 1: 0x3ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x3)

Info : JTAG tap: stm32.bs tap/device found: 0x790007a3 (mfg: 0x3d1, part: 0x9000

, ver: 0x7)

Warn : JTAG tap: stm32.bs       UNEXPECTED: 0x790007a3 (mfg: 0x3d1, part: 0x9000

, ver: 0x7)

Error: JTAG tap: stm32.bs  expected 1 of 7: 0x06412041 (mfg: 0x020, part: 0x6412

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 2 of 7: 0x06410041 (mfg: 0x020, part: 0x6410

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 3 of 7: 0x16410041 (mfg: 0x020, part: 0x6410

, ver: 0x1)

Error: JTAG tap: stm32.bs  expected 4 of 7: 0x06420041 (mfg: 0x020, part: 0x6420

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 5 of 7: 0x06414041 (mfg: 0x020, part: 0x6414

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 6 of 7: 0x06418041 (mfg: 0x020, part: 0x6418

, ver: 0x0)

Error: JTAG tap: stm32.bs  expected 7 of 7: 0x06430041 (mfg: 0x020, part: 0x6430

, ver: 0x0)

Error: Trying to use configured scan chain anyway...

Warn : Bypassing JTAG setup events due to errors

Info : Selecting JTAG transport command set.

Info : AP INIT COMPLETE

target state: halted

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

xPSR: 0x01000000 pc: 0x08000400 msp: 0x20002100

50084 bytes written at address 0x20000000

downloaded 50084 bytes in 0.689039s (70.983 KiB/s)

pc (/32): 0x20004225

Erasing Chip

Error: stm32.cpu -- clearing lockup after double fault

target state: halted

target halted due to debug-request, current mode: Handler HardFault

xPSR: 0x00000003 pc: 00000000 msp: 0x2000e7a0

Polling target stm32.cpu failed, GDB will be halted. Polling again in 100ms

Polling target stm32.cpu succeeded again

****************** Result: In Progress

writing 16384 bytes at 0

loadimage address 536870940 foffset 0 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.230014s (69.561 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 16384

loadimage address 536870940 foffset 16384 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.230013s (69.561 KiB/s)

****************** Result: OK

writing 16384 bytes at 32768

loadimage address 536870940 foffset 32768 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 49152

loadimage address 536870940 foffset 49152 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229014s (69.865 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 65536

loadimage address 536870940 foffset 65536 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: OK

writing 16384 bytes at 81920

loadimage address 536870940 foffset 81920 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.230013s (69.561 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 98304

loadimage address 536870940 foffset 98304 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.230013s (69.561 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 114688

loadimage address 536870940 foffset 114688 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.230013s (69.561 KiB/s)

****************** Result: OK

writing 16384 bytes at 131072

loadimage address 536870940 foffset 131072 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 147456

loadimage address 536870940 foffset 147456 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.227013s (70.481 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 163840

loadimage address 536870940 foffset 163840 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: OK

writing 16384 bytes at 180224

loadimage address 536870940 foffset 180224 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.228013s (70.171 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 196608

loadimage address 536870940 foffset 196608 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.230013s (69.561 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 212992

loadimage address 536870940 foffset 212992 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.227013s (70.481 KiB/s)

****************** Result: OK

writing 16384 bytes at 229376

loadimage address 536870940 foffset 229376 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.228013s (70.171 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 245760

loadimage address 536870940 foffset 245760 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: In Progress

writing 16384 bytes at 262144

loadimage address 536870940 foffset 262144 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: OK

writing 16384 bytes at 278528

loadimage address 536870940 foffset 278528 16384

16384 bytes written at address 0x2000001c

downloaded 16384 bytes in 0.229013s (69.865 KiB/s)

****************** Result: In Progress

writing 13108 bytes at 294912

loadimage address 536870940 foffset 294912 13108

13108 bytes written at address 0x2000001c

downloaded 13108 bytes in 0.186010s (68.818 KiB/s)

****************** Result: In Progress

shutdown command invoked


0 Likes
1 Solution

Hi,

I guess you already resolve the issue.

The snip.scan app is loaded to the mail flash of the MCU.

The .../apps/waf/sflash_write app loads all following JTAG data to serial flash.

* SPI Flash Write Application

*

* This application is used by OpenOCD and the WICED build

* system to write to serial flash. The app is loaded into

* MCU RAM directly and once running, interacts with OpenOCD

* to write consecutive chunks of data received via JTAG to

* serial flash.

*

* The linker script places two of the structures

* defined by the app at the beginning of RAM. These structure

* variables contain all the details of the commands

* to be executed and data to be written

Seyhan

View solution in original post

4 Replies
GregG_16
Employee
Employee
50 sign-ins 25 sign-ins 25 comments on KBA

Hello,

This requires you to enable external resources. We will look into this and guide you on how to enable external resources.

0 Likes
GregG_16
Employee
Employee
50 sign-ins 25 sign-ins 25 comments on KBA

Any update?  I sent you a separate note.

0 Likes

Dear Sir,

Store the Wi-Fi firmware in external serial flash by flash programmer tools. the app load wi-fi firmware and work normal.

But it can' t download sflash.bin to external spi flash by make snip.scan-BCM943362WCD2-FreeRTOS-LwIP-SPI SFLASH=app-download.

Did it need external ram ?

Best Regards

Chuang Chen

0 Likes

Hi,

I guess you already resolve the issue.

The snip.scan app is loaded to the mail flash of the MCU.

The .../apps/waf/sflash_write app loads all following JTAG data to serial flash.

* SPI Flash Write Application

*

* This application is used by OpenOCD and the WICED build

* system to write to serial flash. The app is loaded into

* MCU RAM directly and once running, interacts with OpenOCD

* to write consecutive chunks of data received via JTAG to

* serial flash.

*

* The linker script places two of the structures

* defined by the app at the beginning of RAM. These structure

* variables contain all the details of the commands

* to be executed and data to be written

Seyhan