[SOLVED] JLink Flashing Fails ADUCM320

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

  • [SOLVED] JLink Flashing Fails ADUCM320

    Hi,

    I'm using GDB/GDB Server on OSX. When attempting to flash to an Analog Devices Cortex-M3 the verification step fails. GDB server output and .gdbinit included below.

    Thanks,

    Kenny

    .gdbinit

    Source Code

    1. target remote localhost:2331
    2. monitor reset
    3. monitor sleep 100
    4. monitor flash device ADUCM320
    5. monitor flash download = 1
    6. monitor WorkRAM = 0x20000000-0x2003FFFF
    7. monitor flash CFI = 0x00000000-0x00020000
    8. load


    GDB Server Output

    Source Code

    1. SEGGER J-Link GDB Server V4.84f Command Line Version
    3. JLinkARM.dll V4.84f (DLL compiled May 9 2014 20:17:59)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: yes
    11. Generate logfile: off
    12. Verify download: off
    13. Init regs on start: on
    14. Silent mode: off
    15. Single run mode: off
    16. Target connection timeout: 5 sec.
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: ADUCM320
    23. Target interface: SWD
    24. Target interface speed: 1000kHz
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: J-Link Lite-ADI Rev.1 compiled Jan 7 2013 17:58:04
    30. Hardware: V1.00
    31. S/N: 541000757
    32. OEM: ADI
    33. Checking target voltage...
    34. Target voltage: 3.58 V
    35. Listening on TCP/IP port 2331
    36. Connecting to target...Connected to target
    37. Waiting for GDB connection...Connected to 127.0.0.1
    38. Reading all registers
    39. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    40. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    41. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    42. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    43. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    44. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    45. Target endianess set to "little endian"
    46. Resetting target
    47. Sleep 100ms
    48. Selecting device: ADUCM320
    49. Flash download enabled
    50. Selecting work RAM area (0x20000000-0x2003FFFF)
    51. Selecting CFI flash area (0x00000000-0x00020000)
    52. GDB closed TCP/IP connection
    53. Connected to 127.0.0.1
    54. Reading all registers
    55. Read 1 bytes @ address 0x00000000 (Data = 0xFF)
    56. Target endianess set to "little endian"
    57. Resetting target
    58. Sleep 100ms
    59. Selecting device: ADUCM320
    60. Flash download enabled
    61. Selecting work RAM area (0x20000000-0x2003FFFF)
    62. Selecting CFI flash area (0x00000000-0x00020000)
    63. Downloading 392 bytes @ address 0x00000000
    64. Downloading 1232 bytes @ address 0x00000188
    65. Downloading 8 bytes @ address 0x00000658
    66. Downloading 8 bytes @ address 0x00000660
    67. Downloading 12 bytes @ address 0x00000668
    68. Downloading 4 bytes @ address 0x00000674
    69. Downloading 1076 bytes @ address 0x00000678
    70. Downloading 4 bytes @ address 0x00000AAC
    71. ERROR: Verification failed @ address 0x00000000
    72. Writing register (R8 = 0x00000265)
    73. Reading from address 0x00000000 (Data = 0xFFFFFFFF)
    Display All

  • Hi,

    Thanks for your inquiry.

    I assume that you are trying to program the internal flash of the ADuCM320.
    What I see in your gdbinit:

    monitor WorkRAM = 0x20000000-0x2003FFFF
    monitor flash CFI = 0x00000000-0x00020000


    Any idea what CFI flash is?
    It is a standard that is mainly used for external parallel NOR flash.
    The internal flash of the ADuCM320 has nothing to do with CFI.

    Just remove these two lines from your gdbinit and it has a pretty fair chance to work.
    Selecting the device should already do the job.


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Alex,

    Thanks for the response. Yes. I am aware of CFI. I think during some attempts I was trying even silly things.

    I recently got this working. I think it was a linker configuration issue but I very much appreciate that you took the time to look at this. I'm working on an OSX environment and it has been difficult to know what to trust in such an unproven environment (I've used Windows/Segger/IAR for many years).

    I appreciate that Segger supports OSX and Linux!

    Kenny

  • Hi Kenny,

    Good to hear that it is working after all. :)


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.