[SOLVED] Altera Cyclone V - cannot connect with V6.22g, V6.30 - was working with V6.20i.

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

  • [SOLVED] Altera Cyclone V - cannot connect with V6.22g, V6.30 - was working with V6.20i.

    Hi,

    I used to be able to connect to my Altera Cyclone SBC using the following JLink Commander command using V6.20:
    "C:\Program Files (x86)\SEGGER\JLink\JLink.exe" -device "CYCLONE V" -if JTAG -speed 4000 -AutoConnect 1 -JTAGConf -1,-1

    Command output for 6.20i:

    SEGGER J-Link Commander V6.20i (Compiled Nov 17 2017 17:47:07)
    DLL version V6.20i, compiled Nov 17 2017 17:46:22

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
    Hardware version: V8.00
    S/N: 268000935
    License(s): FlashBP, GDB
    OEM: SEGGER-EDU
    VTref = 3.034V
    Device "CYCLONE V" selected.


    Connecting to target via JTAG
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    CoreSight AP[0]: 0x04770001, AHB-AP
    CoreSight AP[1]: 0x04770002, APB-AP
    Found Cortex-A9 r3p0
    6 code breakpoints, 4 data breakpoints
    Debug architecture ARMv7.0
    Data endian: little
    Main ID register: 0x413FC090
    I-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
    D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
    System control register:
    Instruction endian: little
    Level-1 instruction cache enabled
    Level-1 data cache enabled
    MMU enabled
    Branch prediction enabled
    Cortex-A9 identified.
    J-Link>

    I recently upgraded to 6.22g, and got error messages and a connection failure:

    SEGGER J-Link Commander V6.22g (Compiled Jan 17 2018 16:40:20)
    DLL version V6.22g, compiled Jan 17 2018 16:39:42

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
    Hardware version: V8.00
    S/N: 268000935
    License(s): FlashBP, GDB
    OEM: SEGGER-EDU
    VTref = 3.021V
    Device "CYCLONE V" selected.


    Connecting to target via JTAG
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    AP map detection skipped. Manually configured AP map found.
    AP[0]: AHB-AP (IDR: Not set)
    AP[1]: APB-AP (IDR: Not set)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Skipped. Not an APB-AP
    AP[1]: APB-AP found
    Settings mismatch... core selected: unknown core, core identified: Cortex-A9

    **************************
    WARNING: Identified core does not match configuration. (Found: None, Configured: Cortex-A9)
    **************************


    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

    ****** Error: Cortex-A/R-JTAG (connect): Could not identify core via peripheral ID registers.
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    Cannot connect to target.
    J-Link>


    I am getting the same error with latest 6.30:

    SEGGER J-Link Commander V6.30 (Compiled Jan 30 2018 18:44:50)
    DLL version V6.30, compiled Jan 30 2018 18:44:37

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
    Hardware version: V8.00
    S/N: 268000935
    License(s): FlashBP, GDB
    OEM: SEGGER-EDU
    VTref = 2.976V
    Device "CYCLONE V" selected.


    Connecting to target via JTAG
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    AP map detection skipped. Manually configured AP map found.
    AP[0]: AHB-AP (IDR: Not set)
    AP[1]: APB-AP (IDR: Not set)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Skipped. Not an APB-AP
    AP[1]: APB-AP found
    Settings mismatch... core selected: unknown core, core identified: Cortex-A9

    **************************
    WARNING: Identified core does not match configuration. (Found: None, Configured: Cortex-A9)
    **************************


    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

    ****** Error: Cortex-A/R-JTAG (connect): Could not identify core via peripheral ID registers.
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
    Cannot connect to target.
    J-Link>


    Any clue on why the Altera Cyclone V is not recognized anymore ? Thanks.

    The post was edited 1 time, last by eperie ().

  • Hello,

    Thank you for your inquiry.
    We were able to reproduce the behaviour and fixed the issue. The fix will be part of our next patched release later today.
    In the meantime you can apply the fix quickly yourself.

    Basically the issue boils down for the J-Link not knowing what core type the target is as we had to change some default behaviours when connecting to Cortex-A devices.
    To apply the patch download the attached JLinkScript.
    Then launch it with your connect sequence. How to use a JLinkScript is explained in the J-Link user manual in more detail.

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

    Thank you for your fast answer.

    You fix worked fine.
    One remark though: this was not obvious than to find the exact option in the documentation to use with the Altera_Cyclone_V.JLinkScript file :
    My current understanding is that there are two types of scripts, JLink Commander scripts containing commands JLink commands, to be used with the -CommanderScript option, and DLL configuration scripts to be used with the -JLinlScriptFile option. Since both types of files seems to share the same .jlinkscript extension in your documentation, this was somewhat confusing to me.

    Using, say, the .CommanderScript extension for JLink Commander scripts would help clarifying this point - my two cents.

    For the record, the complete command now working with 6.30 is:

    "D:\Program Files (x86)\SEGGER\JLink\JLink.exe" -if JTAG -device "CYCLONE V" -speed 4000 -JTAGConf -1,-1 -AutoConnect 1 -JLinkScriptFile "D:\Program Files (x86)\SEGGER\JLink\Devices\Altera\CycloneV\Altera_Cyclone_V.JLinkScript"

    (Having the reference to the -JlinkScriptFile option in your answer, or better, the updated command above, would have been even more helpful.)

    Thanks again for the great support.

    Mit freundlichen Grüßen,
    Éric Périé
  • Hi Eric,

    Great to hear that you are up and running again.
    The CommanderScript and JLinkScript are two different things.
    We will see if we can improve documentation in that regard to avoid confusion.

    With the latest J-Link software release V6.30a the JLinkScript is shipped with the package and is loaded automatically if you use one of our tools and connect to a Cyclone V board.
    That way users don't have to link the scripts manually.
    I just offered you the preliminary fix so you can continue working right away without waiting for the release.

    We will consider this case as closed now.

    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.