Search Results

Search results 1-20 of 25.

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

  • Problem solved: There were two Debuggers attached (targetting different devices) and they were (for some reason) swapped ... Regards Marcus

  • Hello all, I am not able to erase the STM32H743 anymore using the Segger J-Trace Pro (SW interface) within Keil MDK v5.25, while the ST-Link V2 works - with otherwise identical configuration. Erasing/flashing the STM32F767 on the same board (only µC exchanged) works fine. The warnings/error are marked in red below. I suspect that the device "STM32H743IIKX" is not sufficiently supported by J-Link V.640 because I received a message box which asked me to select the device (see jpg attached). Any he…

  • Hello Nino, I know, we also have the newer J-Trace PRO which certainly has advantages. Still, the old one was important in my debug configuraiton. It has the following SN/version info: J-Trace CM3 V3.2 14-43 SN 203200722 Kind regards Marcus

  • Unfortunately, the over-voltage was passed via USB hub to my J-Trace. After opening I recognized that a voltage controller (one of them close to the large JTAG connector) was overheated. I would be glad to get the specs/name of the voltage controller(s) in order to be able to repair my valuable device. Thanks a lot, Marcus

  • Hello Nino, I now can confirm that one trace lane (D1) is always low. Layout and wiring seems to be ok, though. Thanks for the hint: the resistances 901 and 902 are not populated. I will check whether there is any error in the GPIO/periphery configuration. One question: I assumed that when I configure 1 bit tracing (only D0) then I should be able to use a much higher core clock than 100 MHz before getting errors like J-Link: LTRACE (Time since start: 30.996 626, Thread=RX Trace packets have been…

  • Hi Nino, now some news: When I configure 1 bit tracing the half-sync detection is ok and things work - depending on the core / trace clock: clock 100 MHz: everything seems fine until this error message turns up: J-Link: LTRACE (Time since start: 30.996 626, Thread=RX Trace packets have been lost and cannot be resent by J-Trace With clock increased to 110 MHz or 120 MHz the error message comes much earlier. With clock even higher, the half-sync is still ok, but Ozone does not/hardly receive trace…

  • Hi Nino, thanks a lot for the explanation and the correction for configuring PG13 as TRACE_D0. In fact, I removed the Zener diodes on my hardware and I also changed the core clock from 216 MHz to 180 MHz and then down to 100 MHz (motivated by this Segger Wiki page wiki.segger.com/Tracing_on_ST_STM32F769) After adjusting GPIO OSPEED EdgeTCLK = 3; EdgeTD = 3; in the trace config JLinkScript, this is the clock that is detected form J-Trace Pro: Trace clock: 90000 kHz Half-sync detection: 0xD1DDD5DD…

  • Hi Nino, ok: I tried another hardware (STM32F411) with standard trace pin mapping (PE2 ... PE6) and - when Ozone is paused - I get Trace clock: 39990 kHz Half-sync detection: 0xFFF7FFF7 (O.K. half-sync pattern detected) Last incorrect half-sync sampled: 0x17C21B42 When Ozone is running Half-sync detection:0xFF17024B (Not O.K. no half-sync pattern detected) On the STM32F767 things still seem to be wrong/unchanged. I configured the non-standard trace pin mapping (see JLinkScript attached) which sh…

  • Hi Nino, I am not sure whether trace is really running in Ozone ... When I click View > Instruction Trace or Code Profile the orange Trace LED is on and the output of the webserver is: Trace clock: 8080 kHz Half-sync detection: 0xE6EEE6EE (Not O.K. no half-sync pattern detected) Last incorrect half-sync sampled: 0xE6EEE6EE The code runs, but, e.g., the run count within the code profile is not updated (see also pasted console output below). I assume, the trace pins may not be correctly configured…

  • Dear Nino, thanks for your rapid reply. I ported your example "ST_STM32F767_8MHz_TraceExample" for Keil µV5.22 which worked fine, Ozone 2.50b is running. I configured the 4-pin tracing within Ozone within Edit > Trace Settings. The Webserver of the J-Trace Pro (192.168.1.103/traceconfig.htm) now says: Trace clock : 8070 kHz Half-sync detection: 0x00000000 (Not O.K. ....) Is this correkt - or should I expect half-sync detection to be != 0? When I now enable "Trace" in Keil Project options > Debug…

  • Hello all, I get the following error (see screenshot attached) when I enable trace (4 pin) in Keil µVision V5.22 with STM32F767 connected. The webserver of the J-Trace Pro shows this: Trace status Trace clock:0 kHz Half-sync detection:0x00000000 (Not O.K. no half-sync pattern detected) Last incorrect half-sync sampled:0x00000000 The trace connector seems to be correct (see 2nd attachment). SYS_TRACECLK = PE2 SYS_TRACED0 = PG13 SYS_TRACED1 = PE4 SYS_TRACED2 = PE5 SYS_TRACED3 = PE6 What did I do w…

  • Hi Johannes, thanks for the hint with the printf output: SEGGER_RTT_WriteString(0, "Hello World!\n"); is working correctly. Then I re-examined my code and found that the initialization block SEGGER_SYSVIEW_Conf(); SEGGER_SYSVIEW_EnableEvents(....) was beyond a break statement - sorry, dumb fault. After correction everything is fine... Thanks again, Marcus

  • Hi, I read through many posts but still I do not get it working. The control block address is 0x200021e8 (retrieved via _SEGGER_RTT in Keil command window). However, I do not receive RTT with SystemView. J-Link commander does not give an output when I type, e.g.: J-Link> exec SetRTTSearchRanges 0x20002000 0x1000 J-Link RTT Client shows: ###RTT Client: Connecting to J-Link RTT Server via localhost:19021 Connected. SEGGER J-Link V6.20d - Real time terminal output J-Trace PRO V1 Cortex-M compiled S…

  • Hi Nino, with Ozone I used the axf file. According to the Ozone setting I used: J-Link Settings: Traget Interface SWD: 5 MHz Trace configuration: - Trace Port - 4 Bit With this, I assume I used ETM. However, SWD sounds like I used SWO ... !? - Marcus

  • Hi Nino, we are using an own very small board with this jtag/etm connector: www2.keil.com/images/default-s…dk5/20pinetm.png?sfvrsn=6 The pin connection on our board should be correct. Today I tried Ozone and was quite impressed. It works nicely with our F767 (same board, only different µC) - and to my surprise, also with the H743. Kind regards Marcus

  • Hi Nino, in the first step I wanted to use SWO, also because I did not want to risk slowing down the execution. Of course, I would also like (and probably have) to use ETM later on. Thanks for the hint at your wiki trace page. Attached please find the screenshot of the trace configuration. Kind regards Marcus forum.segger.com/index.php/Att…33eb66020cc6cd55b1e35abf2

  • Hello all, I get "Trace HW not present" error on STM32H743 using J-Trace Debugger. With ST-Link V2 trace works correctly as expected. Trace with STM32F7 also worked fine for both Segger and ST-Link. Any ideas? - Marcus Keil µVision 5.22 JLink info: ------------ DLL: V6.14b, compiled Mar 9 2017 08:46:04 Firmware: J-Trace Cortex-M Rev.3 compiled Dec 15 2016 14:46:47 Hardware: V3.10 S/N : 203200722 Feature(s) : RDI, FlashBP, FlashDL, JFlash, GDB * JLink Info: Found SWD-DP with ID 0x6BA02477 * JLink…

  • Hi Niklas, the problem is solved. The reason was a bent contact pin within the JTAG/SWD/Trace connector - caused by too often switching cables at the J-Trace. -- Marcus

  • Hello all, the connection was possible a few times, then it got stuck. Keil: Target Options Options > Debug > Settings does not reveal a JTAG device anymore - even though ST-Link V2 does. The same hardware with different µC chip F767 works fine. I pasted the error message below. -- Marcus Popup: No Cortex-M Device found in JTAG chain. ... Load "D:\\Software\\Gamma\\Delta-S\\MDK-ARM\\Gamma-S Configuration\\out.axf" * JLink Info: Device "STM32H743II" selected. Set JLink Project File to "D:\Softwar…

  • Hello all, some time ago I had the same problem with STM32F7 and J_Trace V5.10g. This was solved, see post [SOLVED] "Active read protected STM32 device" message after upgrading J-Trace to V5.10g Now I got the this error again while trying to debug code for the new STM32H743. - Marcus JLink info: ------------ DLL: V6.12f, compiled Jan 13 2017 16:37:50 Firmware: J-Trace Cortex-M Rev.3 compiled Dec 15 2016 14:46:47 Hardware: V3.10 S/N : 203200722