[ABANDONED] Downloading Verify failed on J-Link GDB Server as u-boot was loaded to customed board based on Atmel SAMA5D2 Xplained Ultra.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [ABANDONED] Downloading Verify failed on J-Link GDB Server as u-boot was loaded to customed board based on Atmel SAMA5D2 Xplained Ultra.

    Hi,

    Would you give me some advice for this? Thanks a lot!

    Downloading Verify failed on J-Link GDB Server as u-boot was loaded to customed board based on Atmel SAMA5D2 Xplained Ultra.
    but in the same develop environment, the same u-boot file can be loaded successfully to Atmel SAMA5D2 Xplained Ultra,
    and work/at91bootstrap-3.8.7/binaries/sama5d2_xplained-dataflashboot-uboot-3.8.7.elf can be loaded and run successfully to customed board and Atmel SAMA5D2 Xplained Ultra.

    The DDR size of customed board is 256M Byte, one piece of DDR. and the DDR size of Atmel SAMA5D2 Xplained Ultra is 512MByte, two pieces of DDR.
    Beneath is the files of u-boot I have changed.

    board/atmel/sama5d2_xplained/sama5d2_xplained.c
    static void ddrc_conf(struct atmel_mpddrc_config *ddrc)
    {
    /*ddrc->md = (ATMEL_MPDDRC_MD_DBW_32_BITS | ATMEL_MPDDRC_MD_DDR3_SDRAM);*/
    ddrc->md = (ATMEL_MPDDRC_MD_DBW_16_BITS | ATMEL_MPDDRC_MD_DDR3_SDRAM);
    }
    include/configs/at91-sama5_common.h
    /* #define CONFIG_SYS_SDRAM_SIZE 0x20000000 */
    #define CONFIG_SYS_SDRAM_SIZE 0x10000000

    the attachments are log files of JLinkGDBServer.
    gdbserver-customboard-1.txt and gdbserver-customboard-2.txt are logs for customer board we developed.
    gdbserver-customboard-1.txt
    gdbserver-customboard-2.txt

    gdbserver-AtmelSAMA5D2Xplain.txt is log for Atmel SAMA5D2 Xplained Ultra board.
    gdbserver-AtmelSAMA5D2Xplain.txt

    The post was edited 2 times, last by GANG ().

  • Hi,


    one first sight, I could not spot a single error in the log files.
    Am I missing sth.?


    Best regards,
    Niklas
    Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
    Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
    Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
    Notification for Embedded Studio: Link
  • I'm sorry for post too much message.

    I loaded u-boot file into customed board twice. I power off and on the same customed board again each times.
    all long stream is verify failed. but short stream loaded at the same address in the same customed board is sometimes verify ok, sometimes failed--CPU_ReadMem(128 bytes @ 0x26F49BA8) .
    but all long and short stream can be loaded successfully on Atmel SAMA5D2 Explained Ultra.


    gdbserver-customboard-1.txt

    03-00000000-00-00084246-0010: - Verify failed
    03-00000000-00-00084246-002B: Downloading 2176 bytes @ address 0x26F4929C
    02-00000000-00-00084289-00CB: T53FFF700 084:246 JLINK_WriteMem(0x26F4929C, 0x0880 Bytes, ...) - Data: 08 19 F4 26 17 00 00 00 10 19 F4 26 17 00 00 00 ... -- CPU_WriteMem(2176 bytes @ 0x26F4929C) returns 0x880 (0043ms, 16741ms total)
    02-00000000-00-00084332-00C9: T53FFF700 084:300 JLINK_ReadMem (0x26F4929C, 0x0880 Bytes, ...) -- CPU_ReadMem(2176 bytes @ 0x26F4929C) - Data: 08 19 F4 26 17 00 00 00 10 19 F4 26 17 00 00 00 ... returns 0x00 (0032ms, 16773ms total)
    03-00000000-00-00084332-0010: - Verify failed
    03-00000000-00-00084333-0029: Downloading 96 bytes @ address 0x26F49B1C
    02-00000000-00-00084345-00C8: T53FFF700 084:333 JLINK_WriteMem(0x26F49B1C, 0x0060 Bytes, ...) - Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... -- CPU_WriteMem(96 bytes @ 0x26F49B1C) returns 0x60 (0012ms, 16785ms total)
    02-00000000-00-00084351-00C7: T53FFF700 084:345 JLINK_ReadMem (0x26F49B1C, 0x0060 Bytes, ...) -- CPU_ReadMem(96 bytes @ 0x26F49B1C) - Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... returns 0x00 (0006ms, 16791ms total)
    03-00000000-00-00084351-0010: - Verify failed
    03-00000000-00-00084351-0029: Downloading 42 bytes @ address 0x26F49B7C
    02-00000000-00-00084357-00C8: T53FFF700 084:351 JLINK_WriteMem(0x26F49B7C, 0x002A Bytes, ...) - Data: 00 5F 69 6D 61 67 65 5F 62 69 6E 61 72 79 5F 65 ... -- CPU_WriteMem(42 bytes @ 0x26F49B7C) returns 0x2A (0006ms, 16797ms total)
    02-00000000-00-00084367-00C7: T53FFF700 084:357 JLINK_ReadMem (0x26F49B7C, 0x002A Bytes, ...) -- CPU_ReadMem(42 bytes @ 0x26F49B7C) - Data: 00 5F 69 6D 61 67 65 5F 62 69 6E 61 72 79 5F 65 ... returns 0x00 (0010ms, 16807ms total)
    03-00000000-00-00084367-000E: - Verified OK
    03-00000000-00-00084367-002A: Downloading 128 bytes @ address 0x26F49BA8
    02-00000000-00-00084374-00C9: T53FFF700 084:367 JLINK_WriteMem(0x26F49BA8, 0x0080 Bytes, ...) - Data: 04 00 00 00 A8 F1 F3 26 05 00 00 00 7C 9B F4 26 ... -- CPU_WriteMem(128 bytes @ 0x26F49BA8) returns 0x80 (0007ms, 16814ms total)
    02-00000000-00-00084381-00C8: T53FFF700 084:374 JLINK_ReadMem (0x26F49BA8, 0x0080 Bytes, ...) -- CPU_ReadMem(128 bytes @ 0x26F49BA8) - Data: 04 00 00 00 A8 F1 F3 26 FF FF FF FF 7C 9B F4 26 ... returns 0x00 (0007ms, 16821ms total)
    03-00000000-00-00084381-0010: - Verify failed
    03-00000000-00-00084381-0029: Downloading 17 bytes @ address 0x26F49C28
    02-00000000-00-00084386-00C8: T53FFF700 084:381 JLINK_WriteMem(0x26F49C28, 0x0011 Bytes, ...) - Data: 2F 75 73 72 2F 6C 69 62 2F 6C 64 2E 73 6F 2E 31 ... -- CPU_WriteMem(17 bytes @ 0x26F49C28) returns 0x11 (0005ms, 16826ms total)
    02-00000000-00-00084394-00C7: T53FFF700 084:386 JLINK_ReadMem (0x26F49C28, 0x0011 Bytes, ...) -- CPU_ReadMem(17 bytes @ 0x26F49C28) - Data: 2F 75 73 72 2F 6C 69 62 2F 6C 64 2E 73 6F 2E 31 ... returns 0x00 (0008ms, 16834ms total)
    03-00000000-00-00084394-000E: - Verified OK


    gdbserver-customboard-2.txt

    02-00000000-00-00054472-00C9: TE5BFA700 054:402 JLINK_ReadMem (0x26F4829C, 0x1000 Bytes, ...) -- CPU_ReadMem(4096 bytes @ 0x26F4829C) - Data: 6C 0A F4 26 17 00 00 00 78 0A F4 26 17 00 00 00 ... returns 0x00 (0071ms, 16586ms total)
    03-00000000-00-00054472-0010: - Verify failed
    03-00000000-00-00054472-002B: Downloading 2176 bytes @ address 0x26F4929C
    02-00000000-00-00054512-00CB: TE5BFA700 054:474 JLINK_WriteMem(0x26F4929C, 0x0880 Bytes, ...) - Data: 08 19 F4 26 17 00 00 00 10 19 F4 26 17 00 00 00 ... -- CPU_WriteMem(2176 bytes @ 0x26F4929C) returns 0x880 (0039ms, 16625ms total)
    02-00000000-00-00054553-00C9: TE5BFA700 054:513 JLINK_ReadMem (0x26F4929C, 0x0880 Bytes, ...) -- CPU_ReadMem(2176 bytes @ 0x26F4929C) - Data: 08 19 F4 26 17 00 00 00 10 19 F4 26 17 00 00 00 ... returns 0x00 (0041ms, 16666ms total)
    03-00000000-00-00054553-0010: - Verify failed
    03-00000000-00-00054553-0029: Downloading 96 bytes @ address 0x26F49B1C
    02-00000000-00-00054564-00C8: TE5BFA700 054:554 JLINK_WriteMem(0x26F49B1C, 0x0060 Bytes, ...) - Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... -- CPU_WriteMem(96 bytes @ 0x26F49B1C) returns 0x60 (0011ms, 16677ms total)
    02-00000000-00-00054570-00C7: TE5BFA700 054:565 JLINK_ReadMem (0x26F49B1C, 0x0060 Bytes, ...) -- CPU_ReadMem(96 bytes @ 0x26F49B1C) - Data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... returns 0x00 (0006ms, 16683ms total)
    03-00000000-00-00054570-000E: - Verified OK
    03-00000000-00-00054570-0029: Downloading 42 bytes @ address 0x26F49B7C
    02-00000000-00-00054576-00C8: TE5BFA700 054:571 JLINK_WriteMem(0x26F49B7C, 0x002A Bytes, ...) - Data: 00 5F 69 6D 61 67 65 5F 62 69 6E 61 72 79 5F 65 ... -- CPU_WriteMem(42 bytes @ 0x26F49B7C) returns 0x2A (0006ms, 16689ms total)
    02-00000000-00-00054583-00C7: TE5BFA700 054:577 JLINK_ReadMem (0x26F49B7C, 0x002A Bytes, ...) -- CPU_ReadMem(42 bytes @ 0x26F49B7C) - Data: 00 5F 69 6D 00 00 00 00 62 69 6E 61 72 79 5F 65 ... returns 0x00 (0007ms, 16696ms total)
    03-00000000-00-00054583-0010: - Verify failed
    03-00000000-00-00054583-002A: Downloading 128 bytes @ address 0x26F49BA8
    02-00000000-00-00054593-00C9: TE5BFA700 054:585 JLINK_WriteMem(0x26F49BA8, 0x0080 Bytes, ...) - Data: 04 00 00 00 A8 F1 F3 26 05 00 00 00 7C 9B F4 26 ... -- CPU_WriteMem(128 bytes @ 0x26F49BA8) returns 0x80 (0009ms, 16705ms total)
    02-00000000-00-00054599-00C8: TE5BFA700 054:594 JLINK_ReadMem (0x26F49BA8, 0x0080 Bytes, ...) -- CPU_ReadMem(128 bytes @ 0x26F49BA8) - Data: 04 00 00 00 A8 F1 F3 26 05 00 00 00 7C 9B F4 26 ... returns 0x00 (0006ms, 16711ms total)
    03-00000000-00-00054600-000E: - Verified OK
    03-00000000-00-00054600-0029: Downloading 17 bytes @ address 0x26F49C28
    02-00000000-00-00054604-00C8: TE5BFA700 054:601 JLINK_WriteMem(0x26F49C28, 0x0011 Bytes, ...) - Data: 2F 75 73 72 2F 6C 69 62 2F 6C 64 2E 73 6F 2E 31 ... -- CPU_WriteMem(17 bytes @ 0x26F49C28) returns 0x11 (0004ms, 16715ms total)
    02-00000000-00-00054609-00C7: TE5BFA700 054:605 JLINK_ReadMem (0x26F49C28, 0x0011 Bytes, ...) -- CPU_ReadMem(17 bytes @ 0x26F49C28) - Data: 2F 75 73 72 2F 6C 69 62 2F 6C 64 2E 73 6F 2E 31 ... returns 0x00 (0005ms, 16720ms total)
    03-00000000-00-00054609-000E: - Verified OK
    02-00000000-00-00054609-005C: TE5BFA700 054:610 JLINK_WriteReg(R15 (PC), 0x26F00000) returns 0x00 (0000ms, 16720ms total)

    The post was edited 2 times, last by GANG ().

  • I load u-boot file via gdb

    (gdb) load /work/u-boot-at91-u-boot-2016.03-at91/u-boot
    Loading section .text, size 0x32a1c lma 0x26f00000
    Loading section .rodata, size 0xc78a lma 0x26f32a1c
    Loading section .hash, size 0x2c lma 0x26f3f1a8
    Loading section .dtb.init.rodata, size 0x410 lma 0x26f3f1e0
    Loading section .data, size 0x21e0 lma 0x26f3f5f0
    Loading section .got.plt, size 0xc lma 0x26f417d0
    Loading section .u_boot_list, size 0xac0 lma 0x26f417dc
    Loading section .rel.dyn, size 0x7880 lma 0x26f4229c
    Loading section .dynsym, size 0x60 lma 0x26f49b1c
    Loading section .dynstr, size 0x2a lma 0x26f49b7c
    Loading section .dynamic, size 0x80 lma 0x26f49ba8
    Loading section .interp, size 0x11 lma 0x26f49c28
    Start address 0x26f00000, load size 302121
    Transfer rate: 34 KB/sec, 3640 bytes/write.