10 Replies Latest reply on Oct 8, 2020 9:28 AM by DaHa_4740446

    Type1LD Filesystem Download

    DaHa_4740446

      I have been successfully building to the EVK for the Type 1LD. I have all the provided Platform files and configurations. Now when I go to build to a target that is not on the EVK but on a custom board with all the JTAG connections broken out I have issues. At first glance everything looks fine as you can see below.

       

      ********************************************************************************************************************

      Downloading resources filesystem ... build/demo.aws.iot.pub_sub.publisher-MurataType1LD-FreeRTOS-LwIP/filesystem.bin at sector 1  size 105...

      Downloading apps lookup table in wiced_apps.mk ... build/demo.aws.iot.pub_sub.publisher-MurataType1LD-FreeRTOS-LwIP/APPS.bin @ 0x0000 size

      Downloading Application ...

      No changes detected

       

       

      Resetting target

      Target running

      Build complete

      Making .gdbinit

       

       

      17:29:41 Build Finished (took 41s.834ms)

      ********************************************************************************************************************

       

      I know the application is downloaded because I get a console out put on USART6 below:

       

      ********************************************************************************************************************

      Starting WICED Wiced_006.004.000.0061

      Platform MurataType1LD initialised

      Started FreeRTOS v9.0.0

      WICED_core Initialized

      Initialising LwIP v2.0.3

      DHCP CLIENT hostname WICED IP

      ********************************************************************************************************************

       

      At this point the application hangs. After further inspection it is hanging on reading 43438A1.bin. I can only presume it is not actually where it needs to be. I looked at the openocd_log.txt and so there was a Verify after write failed message:

       

      ********************************************************************************************************************

      27156 bytes written at address 0x20000000

      downloaded 27156 bytes in 0.415695s (63.796 KiB/s)

      entry_address= 536888741

      stack_address= 536919956

      buffer_size= 16384

      pc (/32): 0x200045A5

      Total write size is 4096.

      writing 4096 bytes at 0

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

      xPSR: 0x41000000 pc: 0x20005bd0 msp: 0x2000bf34

      loadimage address 536870940 foffset 0 4096

      4096 bytes written at address 0x2000001c

      downloaded 4096 bytes in 0.062890s (63.603 KiB/s)

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

      xPSR: 0x21000000 pc: 0x20005346 msp: 0x2000be3c

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

      xPSR: 0x61000000 pc: 0x20005374 msp: 0x2000be4c

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

      xPSR: 0x41000000 pc: 0x20005baa msp: 0x2000bf34

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

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

      xPSR: 0x61000000 pc: 0x2000629a msp: 0x2000bf34

      ===== arm v7m registers

      (0) r0 (/32): 0x40000800

      (1) r1 (/32): 0x00000000

      (2) r2 (/32): 0x0000AAAA

      (3) r3 (/32): 0x00000005

      (4) r4 (/32): 0x2000000C

      (5) r5 (/32): 0x00001000

      (6) r6 (/32): 0x2000000C

      (7) r7 (/32): 0x00000000

      (8) r8 (/32): 0x00001000

      (9) r9 (/32): 0x20006A14

      (10) r10 (/32): 0x00000000

      (11) r11 (/32): 0x2000101C

      (12) r12 (/32): 0x20006A14

      (13) sp (/32): 0x2000BF34

      (14) lr (/32): 0x20005BBF

      (15) pc (/32): 0x2000629A

      (16) xPSR (/32): 0x61000000

      (17) msp (/32): 0x2000BF34

      (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)

       

      ********************************************************************************************************************

      Does anyone have any idea where I could be going wrong and why the filesystem will not actually download?