JLink under Linux dies with Segmentation fault

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

  • JLink under Linux dies with Segmentation fault

    Hi

    I know that the JLink EDU is not officially supported under Linux. But i bought one because i saw the Linux Beta Software and now unfortunatly it does noth work.

    [a239368:>jlink
    SEGGER J-Link Commander V4.03a ('?' for help)
    Compiled Aug 4 2009 12:13:06
    DLL version V4.03a, compiled Aug 4 2009 12:12:42
    Firmware: J-Link ARM V8 compiled Dec 1 2009 11:42:48
    Hardware: V8.00
    S/N : 268000082
    OEM : SEGGER-EDU
    Feature(s) : FlashBP
    VTarget = 3.267V
    Info: TotalIRLen = 4, IRPrint = 0x01
    Info: Found Cortex-M3 r1p1, Little endian.
    Info: TPIU fitted.
    hInfo: FPUnit: 6 code (BP) slots and 2 literal slots
    Found 1 JTAG device, Total IRLen = 4:
    #0 Id: 0x3BA00477, IRLen: 4, IRPrint: 0x1 Cortex-M3 Core
    Cortex-M3 identified.
    JTAG speed: 5 kHz
    J-Link>h
    R0 = 0000000A, R1 = 00000010, R2 = 00000006, R3 = 20000120
    R4 = 00000001, R5 = 00000000, R6 = 60A78259, R7 = 00000000
    R8 = CF008EEC, R9 = 802642E8, R10= 105014AE, R11= 02420018
    R12= 00000107, R13= 200010E8, MSP= 200010E8, PSP= 2C042240
    R14(LR) = 0000292B, R15(PC) = 000002B0
    XPSR 81000000, APSR 80000000, EPSR 01000000, IPSR 00000000
    CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    J-Link>loadbin ./uart_echo.bin 0x0
    Loading binary file... [./uart_echo.bin]
    /usr/local/bin/jlink: line 8: 3461 Segmentation fault /data/home/a239368/Mikrocontroller/JLINK_EDU/bin/JLinkExe

    Am i doing something wrong ? Or do i just have to wait for a new Software Release ?

    I'am working with Ubuntu 9.10.

    Kind regards,

    Daniel
  • No, and as you see, no answer from Segger ;(

    The Linux Beta Software seems to be only a marketing trick to get more customer.

    You know, that you can work with OpenOCD 0.4.0 with the JLink EDU ? That works ok on Linux, but on Windows it's a nightmare with this paranoid OpenSource Guys and their decision not to allow to distribute a binary version of OpenOCD with the closed-source USB Driver. On Linux it's easy to compile your own version, but on Windows it's not so easy.
    Another bad point in OpenOCD is the fact, that the syntax and configuration options change very heavy from version to version and with each new version you start from scratch.

    My Idea was, to work in both worlds with the same hardware and software and configuration files. Bad Idea....

    Daniel