[SOLVED] ! ARE J-LINK EDU PROBES FLAWED! Trying to USE the SWO to printf address 0xE0040304 - Verify failed

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

  • [SOLVED] ! ARE J-LINK EDU PROBES FLAWED! Trying to USE the SWO to printf address 0xE0040304 - Verify failed

    Hi guys any help appreciated


    I am following online training and the have suggested using the SWO pin on my nucleo 446RE baord to view the printf data

    rather than use the cheap stlink, i thought I would use my J-link EDU, though starting to wish I had not after all the time wasting with it

    I can't work out why something so simple seems so hard like splitting the atom ?


    so this is the problem



    at the moment I am using NUCLEO 446RE dev board and CUBE IDE (which I hate) prefer embeded studio


    I enable the debug J-link and SWO option


    then when in debug I click the SWV ITM Data Console

    Start the trace and get various errors as in bold below ??

    and thus no printf data

    I have also used the code as per segger website for SWO printf

    but don;t think thats the problem


    I need to be able to start the trace without errors


    Can anyone please help


    Thank You







    SEGGER J-Link GDB Server V6.80b Command Line Version

    JLinkARM.dll V6.80b (DLL compiled Jun 5 2020 17:40:22)

    Command line: -port 2331 -s -device STM32F446RE -endian little -speed 4000 -if swd -swoport 2332 -vd
    -----GDB Server start settings-----
    GDBInit file: none
    GDB Server Listening port: 2331
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: localhost only
    Generate logfile: off
    Verify download: on
    Init regs on start: off
    Silent mode: off
    Single run mode: on
    Target connection timeout: 0 ms
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: STM32F446RE
    Target interface: SWD
    Target interface speed: 4000kHz
    Target endian: little

    Connecting to J-Link...
    J-Link is connected.
    Firmware: J-Link V11 compiled Nov 2 2020 09:15:32
    Hardware: V11.00
    S/N: 261000105
    OEM: SEGGER-EDU
    Feature(s): FlashBP, GDB
    Checking target voltage...
    Target voltage: 3.33 V
    Listening on TCP/IP port 2331
    Connecting to target...
    Connected to target
    Waiting for GDB connection...Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x0800060E (Data = 0x2DE4E7FB)
    Read 2 bytes @ address 0x0800060E (Data = 0xE7FB)
    Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x0800060E (Data = 0x2DE4E7FB)
    Received monitor command: WriteDP 0x2 0xF0
    O.K.
    Received monitor command: ReadAP 0x2
    O.K.:0xE00FF003
    Reading 32 bytes @ address 0xE00FFFD0
    Received monitor command: reset
    Resetting target
    Downloading 452 bytes @ address 0x08000000 - Verified OK
    Downloading 11296 bytes @ address 0x080001C4 - Verified OK
    Downloading 176 bytes @ address 0x08002DE4 - Verified OK
    Downloading 8 bytes @ address 0x08002E94 - Verified OK
    Downloading 4 bytes @ address 0x08002E9C - Verified OK
    Downloading 4 bytes @ address 0x08002EA0 - Verified OK
    Downloading 112 bytes @ address 0x08002EA4 - Verified OK
    Writing register (PC = 0x 8000b78)
    Read 4 bytes @ address 0x08000B78 (Data = 0xD034F8DF)
    Read 2 bytes @ address 0x08000B78 (Data = 0xF8DF)
    Read 2 bytes @ address 0x08000B7A (Data = 0xD034)
    Reading 64 bytes @ address 0x080005C0
    Read 2 bytes @ address 0x08000602 (Data = 0x4803)
    Read 4 bytes @ address 0xE000ED14 (Data = 0x00000200)
    Downloading 4 bytes @ address 0xE000ED14 - Verified OK
    Reading all registers
    Read 4 bytes @ address 0x08000B78 (Data = 0xD034F8DF)
    Read 2 bytes @ address 0x08000B78 (Data = 0xF8DF)
    Read 2 bytes @ address 0x08000B7A (Data = 0xD034)
    Read 4 bytes @ address 0xE000EDFC (Data = 0x01000000)
    Downloading 4 bytes @ address 0xE000EDFC - Verified OK
    Reading all registers
    Read 4 bytes @ address 0x08000B78 (Data = 0xD034F8DF)
    Read 2 bytes @ address 0x08000B78 (Data = 0xF8DF)
    Read 2 bytes @ address 0x08000B7A (Data = 0xD034)
    Read 2 bytes @ address 0x080005E8 (Data = 0xF000)
    Setting breakpoint @ address 0x080005E8, Size = 2, BPHandle = 0x0001
    Setting breakpoint @ address 0x08000602, Size = 2, BPHandle = 0x0002
    Starting target CPU...
    ...Breakpoint reached @ address 0x080005E8
    Reading all registers
    Removing breakpoint @ address 0x080005E8, Size = 2
    Removing breakpoint @ address 0x08000602, Size = 2
    Read 4 bytes @ address 0x080005E8 (Data = 0xFAF0F000)
    Read 4 bytes @ address 0xE0042004 (Data = 0x00000027)
    Read 4 bytes @ address 0xE0001FE0 (Data = 0x00000002)
    Downloading 4 bytes @ address 0xE000EDFC - Verified OK
    Downloading 4 bytes @ address 0xE0042004 - Verified OK
    Downloading 4 bytes @ address 0xE00400F0 - Verified OK
    Downloading 4 bytes @ address 0xE0040010 - Verified OK
    Downloading 4 bytes @ address 0xE0000FB0 - Verify failed
    Downloading 4 bytes @ address 0xE0000E80 - Verified OK
    Downloading 4 bytes @ address 0xE0000E40 - Verified OK
    Downloading 4 bytes @ address 0xE0000E00 - Verified OK
    Downloading 4 bytes @ address 0xE0001020 - Verified OK
    Downloading 4 bytes @ address 0xE0001030 - Verified OK
    Downloading 4 bytes @ address 0xE0001040 - Verified OK
    Downloading 4 bytes @ address 0xE0001050 - Verified OK
    Downloading 4 bytes @ address 0xE0001000 - Verify failed
    Downloading 4 bytes @ address 0xE0040304 - Verify failed

    The post was edited 2 times, last by johnnysh ().

  • Starting to think these J-Link EDU are problematic, there is NO reason for these errors below ??

    So I am guess my probe is floored or broken, this is now getting very frustrating, can see me going back to an ST link and getting back to a probe that works

    I'm only trying to do some studying, and the most simple of tasks and the J-link fails ??


    Why is this Segger EDU


    Kicking Errors ???

    Is it flawed is it broken ??/

    Downloading 4 bytes @ address 0xE0001000 - Verify failed
    Downloading 4 bytes @ address 0xE0040304 - Verify failed

    what is going on ??


    any help please

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

  • For anyone interested, after much time wasting

    I have managed to get the SWO / printf working in CUBE IDE using a nucleo ST32F446RE dev board and J-Link EDU


    THERE ARE STILL ERRORS GENERATED FROM THE J-LINK... NOT SURE WHY ???
    buy these were a red herein and do not stop SWO from working






    OK so the problem, is not Probe Related, it is ST CUBE MX Settings for the system debug and SWO.

    The problem was the way ST CUBE MX had configured the System Debug

    It was originally set to single wire, which looked ok

    but the correct setting is TRACE ASYNCHRONOUS Sw (AS in image 2)

    and then you need save these settings

    and finally configure your IDE for SWO and configure the Correct Core Freq (as in image 3) though my clock is setup at 180mhz


    Spent ages trying all sorts, hope my time wasted helps others with the same problems



    when no one else seems to help,,,,
    Sometimes the only way to sort problem is by yourself!!!

    Regards

















    The post was edited 2 times, last by johnnysh ().

  • Hello,

    Thank you for your inquiry and sharing of your findings.
    Good to hear that you are up and running again.

    Generally there are no known issues with J-Link and SWO and as you found out yourself the issue was IDE/Cube MX related.

    Please note that this is a community forum, not a support forum, so there is no guarantee that you will get assistance from a SEGGER employee. If you have a J-Link Base or higher that is in valid support period we recommend to use our official support channel as explained in my signature.

    The remaining errors (I assume you mean the verify failed messages) you see are not necessarily errors. This is just an indicator in Cube IDE that a certain SWO related init step could not be verified. This does not mean it did not go through.

    However this log messages do not come from J-Link software but from Cube IDE itself. As the SWO init etc. is also completely issued by the Cube IDE and J-Link is here only executing the requested reads and writes, there is no issue to be found on SEGGER's software or hardware side.

    If you still see issues with Cube IDE or Cube MX, we recommend to contact ST support as non of the reported issues are related to any SEGGER hardware or software.

    If you are looking for an alternative IDE than Cube IDE we recommend to give Embedded Studio a try:
    segger.com/products/development-tools/embedded-studio/

    If you like to keep Cube IDE for code generation but want to try another debugger we recommend the usage of Ozone:
    segger.com/products/development-tools/embedded-studio/

    We will consider this thread as closed now.

    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.