Search Results
Search results 1-18 of 18.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
I added test-points to the custom board we are debugging that crashes the debugger when the motor start command is issued. What I have here are traces of JTDI, SWO, TCK and TMS as the MCU is running in debug mode with the J-LINK EDU JTAG connected. This is before a motor start command is received. The scope probes are 10x mode at 2V/div and the bandwidth is full, which is maybe 500MHz in this case. One capture is 4us/div another is 1us/div and also at 400ns/div. Is the TCK and TMS relationship, …
-
Additional info, I've been using a J-Link EDU for debug. I was told by someone the EDU might have weaker drivers than the J-Link Base, so I tried the Base unit. Now when I start the motor the debugger windows do not crash, they freeze at what they were displaying. If I use the Keil debugger command 'Update windows' it does NOT update the windows. This is still a problem for debugging. This does show though the EDU unit is more susceptible to this problem than the Base unit. I also found four of …
-
Is there a Windows version of GDB? I see MinGW is quite old. If what is needed is a setup with GDB and GDB Server I am prepared to do that I'll just need help pointing in the right direction. I looked at GDB from GNU but if I don't have to generate the whole build environment for GNU I'd prefer the easier path.
-
I'm debugging custom hardware that has a ST32GM431C8 MCU and am connected using a J-Link. My connection to the hardware is the 5-wire JTAG. When running using Keil MDK5 I have a problem in which the Keil debug windows work fine until I execute a specific version of code then the windows get trashed and I cannot debug. I was hoping to try the GDB debugger with J-Link (I'm new to GDB). When I launch either the command line program or the GUI version I get "GDB waiting for connection..." I was hopi…
-
Hi Alex, My MCU is running on a custom board. I could provide project software but it is tied to unique hardware. Also, I am not knowingly using any low power modes. Other notes, I added commands to my uart code so that I can display memory locations. Doing this and using the memory map I can see some variables changing as I expect, but the debugger displays AAAAAAAA as example for almost all watch points and peripheral registers. Also, when the motor is running and I choose ToolBox->Update Wind…
-
I have motor code running on a STM32G431 MCU and am using Keil IDE with J-Link debugger (5-pin jtag). When the motor is stopped I can see timer registers updating and can inspect watch variables. I'm also have a simple uart command interface I use to start/stop the motor and read some variables. When I start the motor the Keil IDE watch window stops updating. I have it set to periodic update under the View menu but nothing updates. I can still communicate over the uart interface but the J-link s…
-
I have motor code running on a STM32G431 MCU and am using Keil IDE with J-Link debugger. When the motor is stopped I can see timer registers updating and can inspect watch variables. I'm also have a simple uart command interface I use to start/stop the motor and read some variables. When I start the motor the Keil IDE watch window stops updating. I have it set to periodic update under the View menu but nothing updates. I can still communicate over the uart interface but the J-link seems locked o…
-
I did get a response from Keil and they said my installation might be corrupted. Based on their suggestion I deleted the existing Keil folder and re-installed a fresh download of Keil in the default folder. c:\Keil_v5. After doing this, and re-installing the license, I tried selecting the J-Link as the debugger in a project. As soon as I hit the 'Settings' button after selecting the J-Link I got the same error, "either JL2CM3.dll or some other dll's were missing". If I inspect the folder c:\Keil…
-
My keil_v5 compiler is not connecting with the J-link / J-trace Cortex debug selection. When I choose SELECT it displays Error!!! Cannot load driver C:\Keil-v5\Arm\Segger\JL2CM3.dll. I do see that driver at that path location. This setup worked at one time, but since then my HDD crashed. I needed to recover everything from my HDD and put on SSD. I have no problems with other Keil projects connecting through a ST-Link debugger to Nucleo boards, so I think the Keil set-up is fine. I can execute J-…
-
I have the J-LINK working for the jtag interface to my STM32G431 project. I am using the 5 pins (SWDIO/TMS, SWCLK/TCK, SWO, JTDI, and JTRST). Is there a way to use this same interface simultaneously with a virtual com port to the MCU? What is the pin connection from these pins to the com port Rx and Tx?. Thanks, Brian
-
Replying to my own question. I believe what is happening is that when the STLINK is held in reset it does not write the port bit to enable the 3.3V switch that supplies Vdd to the G431. I moved the jumper on JP5 to 5V_CHRG and left the reset jumper on JP1. Now the G431 gets it's 3.3V enabled and the hardware is happy. The JTAG chaining is a separate issue to be addressed elsewhere.
-
I've read in some Segger documentation the limit on the number of jtag devices is 8. Is this still the case today (Sept 2020) ? I recently found out the STM32 MCU's I am using have two jtag devices each (ex the STM32G431 and STM32F302). Does this mean if I chain 4 MCU the jtag will see 8 devices? So my limit on chained MCU's is 4? Thanks, Brian
-
Hi All, This is updated 9/17/20 with my latest progress. My interconnection of the two boards was wrong due to a misunderstanding of how TDO is routed on the board. I was able to get the Gerber files and review them so this update includes that information. I interconnected the boards per the new diagram. The connection of the first device TDO to the JTag TDI required removing SB15 and soldering in two wires to go to the appropriate connection. The photo shows the modification to SB15 with wires…
-
Hi, I'm trying to connect to the G431 on a Nucleo G431 board and ST gives two options. Using an external debug tool to program and debug the on-board STM32 There are two basic ways to support an external debug tool: 1. Keep the embedded STLINK-V3E running. Power on the STLINK-V3E at first until the COM LED turns red.Then connect the external debug tool through the CN4 STDC14/MIPI-10 debug connector ug 2. Set the embedded STLINK-V3E in high-impedance state: when jumper JP1 (STLK_RST) is ON, the e…