Posts by SEGGER - Tobias

Hi,

The new beta version of the J-Link software (V4.21g) which
contains the fix is now available for download from our website:

http://www.segger.com/cms/beta-software-version.html

Best regards,
Tobias

Hi,

We have analyzed and fixed the problem.
We will built a new beta version of the J-Link software this week,
in which this problem is solved.

Best regards,
Tobias

Hello,

The latest beta version of the J-Link GDB Server (V4.11n) contains a commandline option "-noreset" to disable
the reset at startup. When starting the GDB Server with this option it should work.

The latest beta version is available for download from our website:
http://www.segger.com/cms/beta-software-version.html

Best regards,
Tobias

Hello M3Guy,

We have analyzed this and we have found 2 problems.

The first one was a problem in the GDB Server which causes the flash download to be skipped.
This will be fixed in a new beta version (V4.11a) of the software which will be available for download later today.

The second one is in the GDB init file. The "monitor reset 0" should be done before the "load" command.
Furthermore you should include "monitor endian little" to set the GDB server to little endian.

Attached is the corrected GDB init file.

Best regards,
Tobias

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

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

Hi Uwe,

Do you have NOR flash on your eval. board ?
J-Flash can only be used to program NOR flash.

Best regards,
Tobias

Hi Luke,

I have tested this with an AT91SAM7S256-EK and I can not see a problem.

Can you please tell me what exact MCU you have on your AT91SAM7S-EK ?
Can you please try to type "rx 0" into the J-Link commander ?

Best regards,
Tobias

Hello,

Which version of the J-Link GDB Server do you use ?

Can you please try to use the latest version of the J-Link GDB Server (V3.80c) ?

You can download the latest version from our website:
http://www.segger.com/download_jlink.html

Best regards,
Tobias

Hi,

Which version of J-Flash do you use ?
Can you please try the latest software version (V3.80b) ?

You can download the latest version from our website:
http://www.segger.com/download_jlink.html

Best regards,
Tobias

Hi Steve,

the license system was not changed between V3.80a and V3.80b.
Maybe you have one J-Link with built-in license and another one without license.
Are you sure that you have used the same J-Link with both versions ?

Best regards,

Tobias

Hello,

We will add JTAGLoad to the J-Link ARM Software package.
The tool will be free of charge.

Best regards,
Tobias

Hello Steve,

J-Flash uses the .ini file to save the global settings and to remember
the last project file used. In the case that you start two instances of
J-Flash via commandline it is possible that both of them try to
write to the .ini file at the same time to save the name of the project
file.

We will improve this behaviour in future releases.

A good workaround for now is, to make a copy of the J-Flash folder and start
the two instances from the different folders. This causes the two
J-Flash to use different .ini files.

Best regards,
Tobias

Hi Ken,

This was a problem in the J-Flash software. We have fixed it in
the current beta version of the J-Link ARM software.

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

We will also built a new release version in which
this problem will be fixed.

Best regards,

Tobias

Hello Kevin,

The problem is that the J-Link DLL shipped with the IAR EWARM version 4.30A
or earlier is over 2 years old. This old DLL does not support J-Links with hardware
revision 6.

You can solve the problem by downloading and installing a new version of the
J-Link ARM Software.

The current J-Link Software is always available for download from our website:
http://www.segger.com/download_jlink.html

Short feedback if this solves the problem would be appreciated.

Best regards,

Tobias

Hello,

We have analyzed and fixed the single step problem.

A new beta version in which this problem is solved is
available for download from our website:

http://www.segger.com/download_jlink_beta.html

Can you please download this version
and confirm that the problem is sovled ?

Regarding the reset problem we will take a look
at it and then we will get back to you.

Best regards and happy holidays,

Tobias

Hi Duane,

I have built a new beta version which includes support
for data watchpoints.

The new version is available on our website:
http://www.segger.com/download_jlink_beta.html

You can set watchpoints using the GDB Insight
or via new remote commands:

BD [R|W] <Addr> [<Data>] [<DataMask>]
BDH [R|W] <Addr> [<Data>] [<DataMask>]
BDB [R|W] <Addr> [<Data>] [<DataMask>]

For a list of available remote commands please type in the GDB console:
monitor help

For more detailed information about a remote command please type:
monitor help <command>

Best regards,
Tobias

Hi Duane,

You are right, the GDB Server should allow to set watchpoints
We will implement this.

Best regards,
Tobias

Hello Duane,

We have built a new beta version of the J-Link GDB Server
which can generate a detailed logfile.

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

Can you please download this version and
send us the GDB logfile ?

To generate a GDB logfile please enable the
"Generate logfile" checkbox in the GDB Server
dialog.

You will find the logfile in the program folder of
the GDB Server. It is named "JLinkGDB.log".

Best regards,
Tobias

Hi Mike,

The MMU can be enabled / disabled by bit 0 of the CP15 control
register (which is addressed with: CRn=1, CRm=0, op1=0, op2=0).

You can use the GDB Server to read out the current value
of the control register and to write back a modified value.

The sequence below shows how to disable and enable
the MMU on an Atmel AT91SAM9260.

We have configured the MMU to map SDRAM @ 0x40000000
which was normally address of the NAND flash. As you can see,
we disable the MMU and we read NAND flash (which was empty).
If we enable the MMU again, we read SDRAM.

(gdb) monitor long 0x40000000
Reading from address 0x40000000 (Data = 0x2204480B)
(gdb) monitor cp15 1 0 0 0
Reading CP15 register (1,0,0,0 = 0x0005507D)
(gdb) monitor cp15 1 0 0 0 = 0x5507c
Writing CP15 register (1,0,0,0 = 0x0005507C)
(gdb) monitor long 0x40000000
Reading from address 0x40000000 (Data = 0xFFFFFFFF)
(gdb) monitor cp15 1 0 0 0 = 0x5507d
Writing CP15 register (1,0,0,0 = 0x0005507D)
(gdb) monitor long 0x40000000
Reading from address 0x40000000 (Data = 0x2204480B)

Does this answer your questions ?

Best regards,
Tobias