[SOLVED] GDB server problem with vybrid controler

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

  • [SOLVED] GDB server problem with vybrid controler

    Hello! I've got a problem with connection gdb server v6.00e to vybrid controller (VF6xx_A5_ParallelMode). Here is my log:
    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. : VF6XX_A5
    Type '?' for selection dialog
    Device>VF6XX_A5
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    TIF>J
    Device position in JTAG chain (IRPre,DRPre) : -1,-1 => Auto-detect
    JTAGConf>-1,-1
    Specify target interface speed [kHz]. : 4000 kHz
    Speed>100
    Device "VF6XX_A5" selected.


    TotalIRLen = 14, IRPrint = 0x0555
    TotalIRLen = 14, IRPrint = 0x0555
    TotalIRLen = 14, IRPrint = 0x0555
    TotalIRLen = 14, IRPrint = 0x0555

    ****** Error: CPU-TAP not found in JTAG chain

    TotalIRLen = 14, IRPrint = 0x0555
    TotalIRLen = 14, IRPrint = 0x0555
    TotalIRLen = 14, IRPrint = 0x0555
    TotalIRLen = 14, IRPrint = 0x0555

    ****** Error: CPU-TAP not found in JTAG chain

    Cannot connect to target.
    J-Link>


    But with old version v5.00i there is no problems:
    SEGGER J-Link Commander V5.00l ('?' for help)
    Compiled Aug 7 2015 15:53:19
    DLL version V5.00l, compiled Aug 7 2015 15:52:45
    Firmware: J-Link V10 compiled Aug 3 2016 18:49:54
    Hardware: V10.10
    S/N: xxxxxxxx
    Feature(s): GDB
    Emulator has Trace capability
    VTarget = 3.270V
    Info: TotalIRLen = 14, IRPrint = 0x0555
    Info: ARM AP[0]: 0x44770001, AHB-AP
    Info: ARM AP[1]: 0x24770002, APB-AP
    Info: ROMTbl 0 [0]: 0000A003, CID: B105900D, PID:04-003BB907 ETB
    Info: ROMTbl 0 [2]: 0000D003, CID: B105900D, PID:04-004BB912 TPIU
    Info: ROMTbl 0 [3]: 0000E003, CID: B105900D, PID:04-001BB908 CSTF
    Info: ROMTbl 0 [4]: 00009003, CID: B105900D, PID:04-002BB913 ITM
    Info: ROMTbl 0 [5]: 0000F003, CID: B105900D, PID:04-002BB914 SWO
    Info: ROMTbl 0 [6]: 0000B003, CID: B105900D, PID:04-001BB908 CSTF
    Info: ROMTbl 0 [7]: 00005003, CID: B105100D, PID:04-000BB4A5 ROM Table
    Info: ROMTbl 1 [0]: FFFFC003, CID: B105900D, PID:04-001BBC05 Cortex-A5
    Info: Found Cortex-A5 r0p1
    Info: 3 code breakpoints, 2 data breakpoints
    Info: Debug architecture ARMv7.0
    Info: Data endian: little
    Info: Main ID register: 0x410FC051
    Info: I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
    Info: D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
    Info: System control register:
    Info: Instruction endian: little
    Info: Level-1 instruction cache disabled
    Info: Level-1 data cache disabled
    Info: MMU disabled
    Info: Branch prediction enabled
    Found 2 JTAG devices, Total IRLen = 14:
    #0 Id: 0x0318A0DD, IRLen: 10, Unknown device
    #1 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
    Cortex-A5 identified.
    Target interface speed: 100 kHz
    J-Link>


    I am using J-Link V10 now. Can you help me, please?

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

  • Hi,

    We are not aware of any issues with the NXP (Freescale) Vybrid and J-Link in the latest
    version but we will check if we can reproduce this here and get back to you with the results.

    In the meantime, do you use an evaluation board? If yes, which one?


    Best regards
    Erik
    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,

    Sorry for the delay in response.
    I just gave it a try and connecting to a VF6XX_A5 device (in our case, a PVF61GS151CMK50) works fine. (See screenshot below)


    You probably need to specify IRPre, DRPre when asked for
    Device position in JTAG chain (IRPre,DRPre) : -1,-1 => Auto-detect

    , since your JTAG chain (as you mentioned) is different from the eval board:
    Evalboard:
    Found 1 JTAG device, Total IRLen = 4:
    #0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)

    Your custom hardware:
    Found 2 JTAG devices, Total IRLen = 14:
    #0 Id: 0x0318A0DD, IRLen: 10, Unknown device
    #1 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)



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

  • "Specify IRPre, DRPre" is not working unforunately. What is the reason can it be else? I've tried to read devices Id in jtag chain. I get the following: j-link commander can't read MAX10 Altera, returns 0, Vybrid Id is right.
    Images

    • Безымянный.jpg

      52.85 kB, 499×335, viewed 596 times

    The post was edited 5 times, last by artemdmitriev ().

  • We've checked different versions of J-Link Software. On versions older than 5.10g all work fine, but since 5.10g J-Link can't connect to Vybrid controller (see attachments). Moreover, version 5.10f can connect to the Vybrid controller only if I manually specify IRPre = 10 and DRPre = 1, auto mode doesn't work.
    Images

    • 510f.png

      56.93 kB, 921×1,009, viewed 643 times

    • 510g.png

      32.92 kB, 936×765, viewed 569 times

  • Hi,

    thanks for this information.
    I will take a look at the difference between 5.10f and 5.10g.

    Best regards,
    Niklas

    EDIT: Fixed typ0.
    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,

    please find attached a J-Link script file. Could you please give it a try?

    You can start J-Link commander using: "JLink.exe -JLinkScriptFile Freescale_Vybrid_AccessA5.JLinkScript.txt"

    There is no need to configure the device position, everything is set up in the script file.

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

  • Hi,

    did you change your hardware setup?

    Your last screenshot showed TotalIRLen = 14, while the current one shows TotalIRLen = 24.
    You can change the values for JTAG_IRPre and JTAG_DRPre in the script file according to your hardware setup.

    Best regards,

    Arne
    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.

  • Yes, I used a little different hardware on the last screenshot. I've tried to run script with v6.00f version, with the other hardware (same as before),it works. But how to use gdb server now?
    Images

    • scr.png

      83.14 kB, 1,028×988, viewed 649 times

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

  • Hi,

    the GDB server supports J-Link scriptfiles, too.

    "JLinkGDBServer.exe -device VF6xx_A5 -scriptfile Freescale_Vybrid_AccessA5.JLinkScript.txt"

    Best regards,
    Arne
    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,

    do you need it to be fixed in the DLL?

    Best regards,
    Arne
    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,

    we have decided not to change the DLL in this context.
    We will expand the usage of scriptfiles for devices requiring special handling, so JTAG configuration has to be done by editing these files.

    Best regards,
    Arne
    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 all,

    Quick follow up:
    The current implementation works for 99% of our customers and only a very minor group of customers is effected by this (non-standard setup). For those customers, a special configuration (e.g. as part of an script file) is required as auto-detection / the default configuration does not work out-of-the-box. Yes, we could implement that the auto-detection works for some of the devices which require a special connect (at least for your setup) but even after that, for some devices / setups a custom script file would still be required / needs to be adapted depending on the setup. We are already in progress of changing the current implementation to move the device specific connects from the J-Link DLL to J-Link script files to allow customers to modify the specific connects if they have a non-standard setups. Respecting the facts above (a very minor group is effected / in future this can easily changed by customers / currently it can be already work-arounded by using a J-Link script file), from our point of view, it is not reasonable to put efforts / resources in lifting limitations from the old concept.

    We hope you understand our point of view.

    Would you like to be added to the J-Link software update notification list, so you get informed automatically about the availability of new versions?
    Subscribe: segger.com/notification/subscribe.php?prodid=7,94


    Best regards
    Erik
    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.