embOSView versus J-link does not work at all

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

  • embOSView versus J-link does not work at all

    Hi,
    I am new user with embOS and embOSView. Now I am trying to use embOSview with J-link to profile application program. However, when I setup software and hardware based on SEGGER document and open embOSView, there is no useful information show up. For instance, OS-VERSION's value is 0.00.


    The setup configuration on my board is as below:

    IAR embedded workbench for ARM: 6.60.1.5104.
    ARM: ARM-Cortex-M4
    embOSView: V3.84


    Debugger J-Link configuration:
    Host communication: USB-Device0
    Target interface: SWD
    JTAG/SWD speed: Fixed-200kHz
    clock setup: CPU clock: 72.0 MHz
    SWO clock: 2000 kHz


    embOSView setup setting:
    Type: J-Link Cortex-M3(Memory access)
    Host interface: USB-Device0
    Target interface: SWD
    speed: 200kHz


    And embOSView log file is as below:
    T274C 000:000 SEGGER J-Link V4.46f Log File (0006ms, 0000ms total)
    T274C 000:000 DLL Compiled: May 10 2012 08:30:05 (0006ms, 0000ms total)
    T274C 000:000 Logging started @ 2014-10-14 16:45 (0006ms, 0000ms total)
    T274C 000:006 JLINK_OpenEx(...)
    Firmware: J-Link V9 compiled May 23 2014 19:21:14
    Hardware: V9.00
    S/N: XXXXXXXXX
    Feature(s): GDB returns O.K. (0139ms, 0006ms total)
    T274C 000:145 JLINK_TIF_Select(JLINKARM_TIF_SWD) returns 0x00 (0000ms, 0145ms total)
    T274C 000:145 JLINK_SetSpeed(200) (0001ms, 0145ms total)
    T274C 000:146 JLINK_ReadMem (0xE000ED08, 0x0004 Bytes, ...) >0x108 TIF>Found SWD-DP with ID 0x2BA01477 >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x33 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x35 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x33 TIF>TPIU fitted. >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF>
    FPUnit: 6 code (BP) slots and 2 literal slots >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF> >0x35 TIF> >0x33 TIF> >0x33 TIF>Found Cortex-M4 r0p1, Little endian. -- CPU is running -- CPU_ReadMem(4 bytes @ 0xE000ED08) -- Data: 00 40 82 00 returns 0x00 (0045ms, 0146ms total)
    T274C 000:192 JLINK_ReadMemU32(0x00824000, 0x0001 Items, ...) -- CPU is running -- CPU_ReadMem(4 bytes @ 0x00824000) -- Data: D8 5E 89 00 returns 0x01 (0003ms, 0191ms total)
    T274C 000:195 JLINK_ReadMem (0x00895ED5, 0x0003 Bytes, ...) -- CPU is running -- CPU_ReadMem(3 bytes @ 0x00895ED5) -- Data: 45 82 00 returns 0x00 (0004ms, 0194ms total)

    Could you give some tips how to debug whether embOSView is working or not? My project has been delayed due to embOSView issues.
    Hope for your response. Thanks very much.