[ABANDONED] In Segger SystemView 3.12(or 3.10), ERROR: Could not find SystemView Buffer.

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

  • [ABANDONED] In Segger SystemView 3.12(or 3.10), ERROR: Could not find SystemView Buffer.

    Hi, Sir./Madam. :

    Same to this issue : Click Link

    I meet the same issue in v3.12 and v3.10, too, please help me

    ---------------------------------------------------------
    My Env :
    > Core : Cortex-M4
    > Embedded OS : FreeRTOS-v10
    > Desk System : Win10
    > Segger SystemView : v3.12 & v3.10

    ---------------------------------------------------------
    What I do:

    1. merge the SystemView Code to my project,
    2. call SEGGER_SYSVIEW_Conf() & SEGGER_SYSVIEW_Start() at startup.
    3. and compile the project , open the .map file, find the Address of var _SEGGER_RTT, use this as RTT Control Block Address.

    Source Code

    1. _SEGGER_RTT 0x00810ce0 Data 120 segger_rtt_1.o(SYSTEMRTT_RAM)





    (In my Config ： Up channel 0 - RTT Trace ; Up Channel 1: SystemView Data)

    4. Start The Segger SystemView and click Start Record, config the Address, it gives error msg:

    Shell-Script

    1. 17:13:38 - JLink: Found Cortex-M4 r0p1, Little endian.
    2. 17:13:39 - JLink: FPUnit: 6 code (BP) slots and 2 literal slots
    3. 17:13:39 - JLink: CoreSight components:
    4. 17:13:39 - JLink: ROMTbl[0] @ E00FF000
    5. 17:13:39 - JLink: ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
    6. 17:13:39 - JLink: ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    7. 17:13:39 - JLink: ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    8. 17:13:39 - JLink: ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    9. 17:13:39 - JLink: ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
    10. 17:13:39 - ERROR: Could not find SystemView Buffer.

    And I use RTT Viewer tool to receive RTT Data from UP-Channel 0, it's successful.

    5. But if i Access the SystemView Channel-1 by J-Link - Web control panel through web : localhost:19081/rtt.htm - > RTT Module


    It Gets the SystemView Channel's Data correctly.

    > SystemView UpChannel data from "J-Link - Web control panel [RTT]"

    Source Code

    1. 02 0F 9D F1 03 03 E3 02 02 0F 9D F1 03 03 E3 02 02 0F 9D F1 03 03 E3 02
    2. 02 0F 9D F1 03 03 E3 02 02 0F 9D F1 03 03 E3 02 02 0F 9D F1 03 03 E3 02
    3. 02 0F 9D F1 03 03 E3 02 02 0F 9D F1 03 03 E3 02 02 0F 9D F1 03 03 E3 02
    5. 。。。。。。。。。。。

    6. or I start the RTT Logger Tool to capture the SystemView Channel DATA and save to *.SVDat, Then open this with SystemView Tool, it's also OK.


    Brainfuck Source Code

    1. ------------------------------------------------------------
    3. Device name. Default: CORTEX-M4 >
    4. Target interface. > SWD
    5. Interface speed [kHz]. Default: 4000 kHz >
    6. RTT Control Block address. Default: auto-detection > 0x00810ce0
    7. RTT Channel name or index. Default: channel 1 > 1
    8. Output file. Default: RTT_<ChannelName>_<Time>.log > 1234567.SVDat
    10. -----------------------------------------------------------
    12. Searching for RTT Control Block...OK. 2 up-channels found.
    13. RTT Channel description:
    14. Index: 1
    15. Name: SysView
    16. Size: 4096 bytes.
    18. Output file: 1234567.SVDat
    20. Getting RTT data from target. Press any key to quit.
    21. ------------------------------------------------------------
    23. Transfer rate: 9 KByte/s Bytes written: 69 KByte
    Display All

    7. I review the User Guide Of Segger SystemView again and again. but cannot solve this issue.

    =====================

    So Why cannot Record the data by SystemView Tool directly ? what reasons may cause the error : Could not find SystemView Buffer ?

    please help, thx so much

    The post was edited 4 times, last by nixlong ().

  • Hello,

    Thank you for your inquiry.
    Did you follow the suggestions in the thread you have linked? That should already provide you with all needed information to solve this issue.
    Why are you setting Cortex-M4 as the target device?
    Is your target device not supported by J-Link? If it is we recommend to select the exact target device name. This will in most cases be sufficient for the RTT buffer to be found.

    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.