SEGGER Forum

I do not have any idea which device you have connected, so it is a bit hard to answer ...

Normally this should work. In order to find out what is going on,
it would be good to know what happened:

- Have you been able to connect to the board earlier ?
- If yes, what did you do before the chip "locked up" ?
If may require a special "unlock" or "Connect under Reset" in order to revive it.
If you know what you programmed into it, could you send it to support@segger.com, referring to this post ?

Thanks,
Rolf

I have been able sometimes to get it to work by hot-plugging the JLink at the same time as I click the debug icon in IAR EWARM. It must be some pin-strapping configuration on the JTAG port?

Has anyone found the source of the problem here? I am having this issue as well: same basic equipment. I am perfectly happy to modify the circuits on the eval board if that is necessary.

Thanks.

What happens when you press RESET, then (keeping your finger on the RESET button)
start the J-Link commander ?

You should see output similar to the following:

SEGGER J-Link Commander V3.86 ('?' for help)
Compiled Jun 27 2008 19:42:43
DLL version V3.86, compiled Jun 27 2008 19:42:28
Firmware: J-Link ARM V6 compiled Jun 27 2008 18:35:51
Hardware: V6.00
S/N : 1
VTarget = 3.267V
JTAG speed: 5 kHz
Info: TotalIRLen = 9, IRPrint = 0x0011
Info: Found Cortex-M3, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
Found 2 JTAG devices, Total IRLen = 9:
Id of device #0: 0x3BA00477
Id of device #1: 0x16410041
Cortex-M3 identified.
J-Link>

Based on the outcome, we'll find a solution for the problem.
We have to assume that you put a program in the device which puts
it into sleep or power down mode right after RESET.
Normally, a connect under Reset should work and allow reprogramming the device.
So if you provide the output of JLink.exe while RESET is pressed and let us knwo which board you have and
what is printed on the chip, we'll go from there.

Could you please try out the latest software version of J-Link (V3.86)?
It should solve the problem.

Best regards,

Alex

Same problem here, and I am using the latest 3.86c J-link software. This is with IAR 5.11 on Cortex-M3, specifically the Luminary LM3S617 on a Luminary stepper-RDK. I reported this problem to Luminary tech support and they experienced the same thing when trying it with a Beta verion of IAR 5.20, but said that it worked with the 5.11 release. 5.11 ships with 3.78b
I should also add that JLInk commander connects fine - no problem at all. The problem for me only starts when I try to connect through the IAR 5.11 debugger
GP

We would like to investigate this, but we can not reproduce a problem.
Everything that we have been doing works fine.

In general, if J-Link.exe can "talk" to the chip, it should be be possible to do the same thing from
within the IAR workbench.

So if anybody has a procedure that allows us to reprodce a problem, we're happy to investigate it.

Rolf

Not exactly a procedure, but here is everything else that I know on the subject.
I started by installing Embedded Workbench for ARM, version 5.11 and all seven or eight patches.
Then I installed JLink 3.86c. It found my installation of EWB4 and EWB5. I let it update both of them.
I ran JLink commander and it updated the firmware of my JLink KS ( hardware v5.2 ) I used this combination to successfully do development on a different project using an ARM9.
When I started to try development with the Luminary Cortex-M3, the debugger would not start and produced this log:

Mon Jul 07 20:44:41 2008: Loaded macro file: C:\Program Files\IAR Systems\Embedded Workbench 5.0\ARM\config\flashloader\Luminary\FlashLM3Sxxx8k.mac

Mon Jul 07 20:44:43 2008: DLL version: V3.86c, compiled Jul 1 2008 19:54:28
Mon Jul 07 20:44:43 2008: Firmware: J-Link compiled Mar 3 2008 19:52:16 ARM Rev.5
Mon Jul 07 20:44:43 2008: JTAG speed is initially set to: 32 kHz
Mon Jul 07 20:44:43 2008: TotalIRLen = 4, IRPrint = 0x01
Mon Jul 07 20:44:43 2008: Found Cortex-M3, Little endian.
Mon Jul 07 20:44:43 2008: TPIU fitted.
Mon Jul 07 20:44:43 2008: FPUnit: 6 code (BP) slots and 2 literal slots
Mon Jul 07 20:59:25 2008: Fatal error: Bad JTAG communication: Write to IR: Expected 0x1, got 0xf (TAP Command : 11) @ Off 0xA.
Wrong AHB ID (15:3). Expected 0x04770001 (Mask 0x0FFFFF0F), Found 0x00000000
When a support person at Luminary tried it (running an earlier version of JLink ) they got this log:


Wed Jul 09 16:52:12 2008: Loaded macro file: C:\Program Files\IAR Systems\Embedded Workbench 5.0\ARM\config\flashloader\Luminary\FlashLM3Sxxx8k.mac
Wed Jul 09 16:52:12 2008: Logging to file: C:\Program Files\IAR Systems\Embedded Workbench 5.0\ARM\cspycomm.log
Wed Jul 09 16:52:12 2008: DLL version: V3.78b, compiled Dec 10 2007 17:56:48
Wed Jul 09 16:52:12 2008: Firmware: J-Link ARM V6 compiled Jun 27 2008 18:35:51
Wed Jul 09 16:52:12 2008: JTAG speed is initially set to: 32 kHz
Wed Jul 09 16:52:12 2008: TotalIRLen = 4, IRPrint = 0x01
Wed Jul 09 16:52:12 2008: TotalIRLen = 4, IRPrint = 0x01
Wed Jul 09 16:52:12 2008: Found Cortex-M3, Little endian.
Wed Jul 09 16:52:12 2008: TPIU fitted.
Wed Jul 09 16:52:12 2008: FPUnit: 6 code (BP) slots and 2 literal slots
Wed Jul 09 16:52:12 2008: Software reset was performed
Wed Jul 09 16:52:12 2008: Initial reset was performed
Wed Jul 09 16:52:12 2008: J-Link found 1 JTAG device. ARM core Id: 2BA00477
Wed Jul 09 16:52:12 2008: Device at TAP0 selected
Wed Jul 09 16:52:12 2008: Turning off watchdog
Wed Jul 09 16:52:12 2008: Time limited license: 64 days left
Wed Jul 09 16:52:13 2008: 3820 bytes downloaded and verified (3.98 Kbytes/sec)
Wed Jul 09 16:52:13 2008: Loaded debugee: C:\Program Files\IAR Systems\Embedded Workbench 5.0\ARM\config\flashloader\Luminary\FlashLM3Sxxx8k.out
Wed Jul 09 16:52:13 2008: TotalIRLen = 4, IRPrint = 0x01
Wed Jul 09 16:52:13 2008: Found Cortex-M3, Little endian.
Wed Jul 09 16:52:13 2008: TPIU fitted.
Wed Jul 09 16:52:13 2008: FPUnit: 6 code (BP) slots and 2 literal slots
Wed Jul 09 16:52:13 2008: Software reset was performed
Wed Jul 09 16:52:13 2008: Target reset
Wed Jul 09 16:52:18 2008: Program exit reached.
Wed Jul 09 16:52:18 2008: TotalIRLen = 4, IRPrint = 0x01
Wed Jul 09 16:52:18 2008: Found Cortex-M3, Little endian.
Wed Jul 09 16:52:18 2008: TPIU fitted.
Wed Jul 09 16:52:18 2008: FPUnit: 6 code (BP) slots and 2 literal slots
Wed Jul 09 16:52:18 2008: Software reset was performed
Wed Jul 09 16:52:18 2008: Time limited license: 64 days left
Wed Jul 09 16:52:19 2008: 13223 bytes downloaded into FLASH and verified (2.15 Kbytes/sec)
Wed Jul 09 16:52:19 2008: Loaded debugee: C:\RDK-Stepper\stepper\ewarm\Exe\stepper.out
Wed Jul 09 16:52:19 2008: TotalIRLen = 4, IRPrint = 0x01
Wed Jul 09 16:52:19 2008: Found Cortex-M3, Little endian.
Wed Jul 09 16:52:19 2008: TPIU fitted.
Wed Jul 09 16:52:19 2008: FPUnit: 6 code (BP) slots and 2 literal slots
Wed Jul 09 16:52:19 2008: Software reset was performed
Wed Jul 09 16:52:19 2008: Target reset

The two diverge when the EWB issues a software reset. Luminary reported that the EWB did not work , and they got the same error message, if they set EWB for anything other than "Software Reset". I was already configure for Software Reset so I had nothing to change.
George

Hello,

We have tried to reproduce this with different boards but we can not see a problem
with them. Unfortunately we do not have the Luminary LM3S617 Stepper-RDK.

We will try to get one board from Luminary so we can test on this board.

Best regards,
Tobias

That is very helpful, thanks for posting. How did you end up waking the CPU ?

Hello,

We analyzed and fixed this problem in the latest beta version of the J-Link software (V3.89d).

The beta version is available for download from our website:
http://www.segger.com/download_jlink_beta.html

Best regards,
Tobias

I downloaded and installed this version to IAR 5.11. It does get past the original problem and is able to better communicate with the target. I believe that it gets as far as downloading an image to the target, then it hangs. The problem may be in the application, I can't really tell. I am working with a Luminary BLDC RDK and will report my experience to them.

Can you check what happens if you uncheck "run to main" ?
You should see the startup code and should be able to step thru.