Dear forum
Sometime in the last month or so, uVision has stopped connecting to debug my device.
Before my problems started, my process start debugging in uVision was:
Now I have to run J-Link Flash to manually establish a connection (via J-Link Plus) to my device.
My process to start debugging in uVision is:
It seems that uVision has "forgotten" how to connect to my device, but it can use a connection established by J-Flash.
During my investigations, I have found that the JTAG device chain (see attached screenshots) is populated when when J-Flash has connected, but is empty when J-Flash has not connected.
It is not the adapter*. I tried tried two adapters (J_Link Pro and Flasher) and both adapters exhibit the same problem.
It is not my software project*. I have reverted to my known working code from several months ago(prior to any problems) and problem persists.
It is not my end device*. I have tested against both a CC2538 and a LPC1768 chips. Both devices were known to be working.
I am using the latest hardware, software, and firmware as of yesterday for both uVision and J-Flash. When prompted I updated the firmware for the J-Link Pro and Flasher adapters. My adapter is protected with a J-Link SWD isolator. I am developing on a freshly created windows installation.
My experience with Segger and uVision is limited and I am stuck. I have a workaround but I am crossing my fingers that the J-Flash workaround doesn't stop working.
I contacted Keil s(vision support) who said that the problem was with the Segger supplied debug dlls.
Does anyone have a suggestion of how I proceed?
thanks
Joe
Edit:
* I am 90% sure of these conclusions.
Display All
Sometime in the last month or so, uVision has stopped connecting to debug my device.
Before my problems started, my process start debugging in uVision was:
- edit my code
- compile my code
- Start debugging (Ctrl-F5) which would flash my new binary and stop at main().
Now I have to run J-Link Flash to manually establish a connection (via J-Link Plus) to my device.
My process to start debugging in uVision is:
- edit my code
- compile my code
- start J-Flash; open a flash project; and connect (Target->Connect) to the device
- Start debugging (Ctrl-F5) which would flash my new binary and stop at main().
It seems that uVision has "forgotten" how to connect to my device, but it can use a connection established by J-Flash.
During my investigations, I have found that the JTAG device chain (see attached screenshots) is populated when when J-Flash has connected, but is empty when J-Flash has not connected.
It is not the adapter*. I tried tried two adapters (J_Link Pro and Flasher) and both adapters exhibit the same problem.
It is not my software project*. I have reverted to my known working code from several months ago(prior to any problems) and problem persists.
It is not my end device*. I have tested against both a CC2538 and a LPC1768 chips. Both devices were known to be working.
I am using the latest hardware, software, and firmware as of yesterday for both uVision and J-Flash. When prompted I updated the firmware for the J-Link Pro and Flasher adapters. My adapter is protected with a J-Link SWD isolator. I am developing on a freshly created windows installation.
My experience with Segger and uVision is limited and I am stuck. I have a workaround but I am crossing my fingers that the J-Flash workaround doesn't stop working.
I contacted Keil s(vision support) who said that the problem was with the Segger supplied debug dlls.
Does anyone have a suggestion of how I proceed?
thanks
Joe
Edit:
* I am 90% sure of these conclusions.
Source Code
- IDE-Version: µVision V5.14.0.0
- Copyright (C) 2015 ARM Ltd and ARM Germany GmbH. All rights reserved.
- License Information:
- <snip>
- Tool Version Numbers:
- Toolchain: MDK-ARM Professional Version: 5.14.0.0
- Toolchain Path: C:\Keil_v5\ARM\ARMCC\Bin
- C Compiler: Armcc.exe V5.05 update 1 (build 106)
- Assembler: Armasm.exe V5.05 update 1 (build 106)
- Linker/Locator: ArmLink.exe V5.05 update 1 (build 106)
- Library Manager: ArmAr.exe V5.05 update 1 (build 106)
- Hex Converter: FromElf.exe V5.05 update 1 (build 106)
- CPU DLL: SARMCM3.DLL V5.14.0.0
- Dialog DLL: DCM.DLL V1.13.1.0
- Target DLL: Segger\JL2CM3.dll V2.99.13.0
- Dialog DLL: TCM.DLL V1.14.4.0
Source Code
- J-Link Commander information
- SEGGER J-Link Commander V4.98b ('?' for help)
- Compiled Apr 10 2015 20:16:11
- DLL version V4.98b, compiled Apr 10 2015 20:15:52
- Firmware: J-Link V9 compiled Apr 10 2015 10:51:08
- Hardware: V9.30
- S/N: 609301634
- Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
- VTarget = 0.000V
- J-Link>
Source Code
- SEGGER J-Link Commander V4.98b ('?' for help)
- Compiled Apr 10 2015 20:16:11
- DLL version V4.98b, compiled Apr 10 2015 20:15:52
- Firmware: J-Link ARM / Flasher ARM V4 compiled Mar 31 2015 22:22:18
- Hardware: V4.00
- S/N: 164101831
- Feature(s): JFlash, GDB
- IP-Addr.: 255.255.255.255 (DHCP)
- VTarget = 0.000V
- J-Link>
The post was edited 1 time, last by joedev ().