j-link am35xx script

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

  • j-link am35xx script

    Hi,

    Section 9.16.2 of UM08001 says that there's a script for the am35xx in the scripts directory. I can not find anything that looks like likely in the 4.80 release. Where can I find this file?

    Thanks!

  • Hi,

    You do not need the script anymore (so this is why it is not shipped anymore).
    We will update the manual regarding this.
    All you need to do is telling the J-Link software what device you are connecting to (e.g. the AM335x family cannot be auto-detected).

    For debuggers like Keil MDK, IAR EWARM, ...: You only need to select the correct device in the debugger. This information is passed automatically to the J-Link software.
    For GDBServer:
    Start it as follows: JLinkGDBServer -device AM3359 -if JTAG -speed 4000

    For J-Link Commander:
    Start it as follows: JLink.exe -device AM3359 -if JTAG -speed 4000

    Then you should be fine.


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

  • Thanks. I tried jlink.exe and there were some problems. I'm trying t connect to a beablebone black, by the way.

    Here's what I'm doing:

    D:\Program Files (x86)\SEGGER\JLinkARM_V480h>jlink -device AM3359 -if JTAG -speed 1000
    SEGGER J-Link Commander V4.80h ('?' for help)
    Compiled Feb 28 2014 21:45:38
    Info: Device "AM3359" selected (0 KB flash, 0 KB RAM).
    DLL version V4.80h, compiled Feb 28 2014 21:45:30
    Firmware: J-Link ARM V8 compiled Nov 25 2013 19:20:08
    Hardware: V8.00
    S/N:
    OEM:
    Feature(s): FlashBP, GDB
    VTarget = 3.338V
    Info: TotalIRLen = 6, IRPrint = 0x01
    Info: TotalIRLen = 10, IRPrint = 0x0011
    Info: ARM AP[0]: 0x04770001, AHB-AP
    Info: ARM AP[1]: 0x04770002, APB-AP
    Info: ARM AP[2]: 0x04760000, JTAG-AP

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

    ****** Error: Could not power up debug port: Control/Status register reads 10000F03

  • Hi,

    Looks like you have an application running on the target which has powered down the debug logic of the core and the power up request made by J-Link is rejected by the device.
    There is not much J-Link can do here if the power-up request (to be able to access the debug logic of the core again) is rejected by the device.

    We do not see this behavior on the AM3359 devices we have here.


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