Error while determining flash info on SAMV71

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

    • Error while determining flash info on SAMV71

      I'm experiencing this on a ATSAMV71Q21B. I've erased the chip completely using different methods and tried the following commands:

      Source Code

      1. h
      2. rx 300
      3. erase

      The last part fails with error -1, failed while determining flash info, claiming it failed to prepare RAMCode.

      Full log:

      Source Code

      1. Target connection not established yet but required for command.
      2. Please specify device / core. <Default>: ATSAMV71Q21
      3. Type '?' for selection dialog
      4. Device>connect
      5. Please specify target interface:
      6. J) JTAG (Default)
      7. S) SWD
      8. F) FINE
      9. I) ICSP
      10. C) C2
      11. T) cJTAG
      12. TIF>s
      13. Specify target interface speed [kHz]. <Default>: 4000 kHz
      14. Speed>auto
      15. Device "ATSAMV71Q21" selected.
      16. Connecting to target via SWD
      17. Found SW-DP with ID 0x0BD11477
      18. DPIDR: 0x0BD11477
      19. Scanning AP map to find all available APs
      20. AP[1]: Stopped AP scan as end of AP map has been reached
      21. AP[0]: AHB-AP (IDR: 0x04770041)
      22. Iterating through AP map to find AHB-AP to use
      23. AP[0]: Core found
      24. AP[0]: AHB-AP ROM base: 0xE00FD000
      25. CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
      26. Found Cortex-M7 r1p1, Little endian.
      27. FPUnit: 8 code (BP) slots and 0 literal slots
      28. CoreSight components:
      29. ROMTbl[0] @ E00FD000
      30. ROMTbl[0][0]: E00FE000, CID: B105100D, PID: 000BB4C8 ROM Table
      31. ROMTbl[1] @ E00FE000
      32. ROMTbl[1][0]: E00FF000, CID: B105100D, PID: 000BB4C7 ROM Table
      33. ROMTbl[2] @ E00FF000
      34. ROMTbl[2][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
      35. ROMTbl[2][1]: E0001000, CID: B105E00D, PID: 000BB002 DWT
      36. ROMTbl[2][2]: E0002000, CID: B105E00D, PID: 000BB00E FPB-M7
      37. ROMTbl[2][3]: E0000000, CID: B105E00D, PID: 000BB001 ITM
      38. ROMTbl[1][1]: E0041000, CID: B105900D, PID: 001BB975 ETM-M7
      39. ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BB9A9 TPIU-M7
      40. Cache: Separate I- and D-cache.
      41. I-Cache L1: 16 KiB, 256 Sets, 32 Bytes/Line, 2-Way
      42. D-Cache L1: 16 KiB, 128 Sets, 32 Bytes/Line, 4-Way
      43. Cortex-M7 identified.
      44. PC = FFFFFFFE, CycleCnt = B5F633CE
      45. R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
      46. R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
      47. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
      48. R12= 00000000
      49. SP(R13)= FFFFFFD8, MSP= FFFFFFD8, PSP= 00000000, R14(LR) = FFFFFFF9
      50. XPSR = 01000003: APSR = nzcvq, EPSR = 01000000, IPSR = 003 (HardFault)
      51. CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00
      52. FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
      53. FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
      54. FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
      55. FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= FFFFFFFF
      56. FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
      57. FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
      58. FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
      59. FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= FFFFFFFF
      60. FPSCR= 00000000
      61. J-Link>rx 300
      62. Reset delay: 300 ms
      63. Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
      64. Reset: Halt core after reset via DEMCR.VC_CORERESET.
      65. Reset: Reset device via AIRCR.SYSRESETREQ.
      66. J-Link>erase
      67. Without any give address range, Erase Chip will be executed
      68. Erasing device...
      69. J-Link: Flash download: Total time needed: 7.744s (Prepare: 0.038s, Compare: 0.000s, Erase: 7.700s, Program: 0.000s, Verify: 0.000s, Restore: 0.005s)
      70. ****** Error: Failed to prepare RAMCode using RAM
      71. Error while determining flash info (Bank @ 0x80000000)
      72. ERROR: Erase returned with error code -1.
      73. J-Link>
      Display All


      I've used 7.00a and 7.22a.


      Source Code

      1. SEGGER J-Link Commander V7.22a (Compiled Jun 9 2021 16:38:16)
      2. DLL version V7.22a, compiled Jun 9 2021 16:38:00
      3. Connecting to J-Link via USB...O.K.
      4. Firmware: J-Trace PRO V1 Cortex-M compiled Feb 2 2021 16:38:18
      5. Hardware version: V1.00
      6. S/N: 751000526
      7. License(s): RDI, FlashBP, FlashDL, JFlash, GDB
      8. IP-Addr: 192.168.0.6
      9. Emulator has RAWTRACE capability
      10. VTref=3.219V
      11. Type "connect" to establish a target connection, '?' for help
      12. J-Link>
      Display All

      The post was edited 1 time, last by emrainey: fixing code/logs ().

    • This morning I tried something different, by using the erase as a range.

      Source Code

      1. J-Link>erase 0x400000 0x600000
      2. Erasing selected range...
      3. J-Link: Flash download: Total time needed: 7.744s (Prepare: 0.081s, Compare: 0.000s, Erase: 7.659s, Program: 0.000s, Verify: 0.000s, Restore: 0.004s)
      4. J-Link: Flash download:
      5. Flash sectors within Range [0x00400000 - 0x00600000] deleted.
      6. Erasing done.
      This seemed to work correctly.

      What is the difference in the SEGGER tools between erase (ERASE chip?) and erase 0x400000 0x600000 ?
    • Since Admins aren't answering these messages, I'll just chime in that that range in the error above is for the QSPI memory, which isn't attached or enabled (AFAIK). Perhaps this RAMCode which is loaded to clear the flash thinks it has to erase a QSPI memory as well? How do we stop it from doing that?
    • Hi,

      this is not a support forum. If you are entitled to support please use our official support channel as explained in my signature.

      Best regards,
      Nino
      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.