Home/Support/Support Forum/How to migrate Segger "JLINK" for ESP1.4.1/NET+OS7.4.2/NS9210
New and improved user forum site going live on 12/6 (All users will need to reset their password when the new forum is active)
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

How to migrate Segger "JLINK" for ESP1.4.1/NET+OS7.4.2/NS9210

0 votes
I am using NET+OS7.4 succeedingly for support of the old product which carries NS9210.
Since "Digi JTAG LINK" was damaged, I requested the purchase of that from the local agency. :blue:
Their reply was time-for-delivery one month.
It is over the time for delivery of imposing-on us repair work. :?
Then, we purchased "SEGGER JLINK" of the manufacturer of this debugger.
When it was connected to PC, it succeeded in "JLINK" being recognized by Windows-XP (Pro:32Bit) and starting "GDB SERVER V3.88" from "ESP".
However, it will become an error if it is actually going to start debugging. :blue:
In this case, is there any necessity of upgrading GDB Server?
Furthermore, do I have the necessity of changing some setup of ESP?
The following is a log of "GDB Servar".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEGGER J-Link GDB Server V3.88

JLinkARM.dll V3.88 (DLL compiled Jul 25 2008 15:05:59)

Listening on TCP/IP port 2331

J-Link connected
Firmware: J-Link V9 compiled Oct 18 2012 19:49:50
Hardware: V9.00
S/N: 59104542
Feature(s): GDB

J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x27926031 (ARM9)

Connected to 127.0.0.1
Reading all registers
JTAG speed set to 1000 kHz
Target endianess set to "big endian"
Resetting target (halt with breakpoint @ address 0)
Writing 0x00000001 @ address 0xA0700000
Writing 0x00000006 @ address 0xA0700024
Writing 0x00000001 @ address 0xA0700028
Writing 0x00000001 @ address 0xA0700030
Writing 0x00000003 @ address 0xA0700034
Writing 0x00000005 @ address 0xA0700038
Writing 0x00000000 @ address 0xA070003C
Writing 0x00000004 @ address 0xA0700040
Writing 0x00000001 @ address 0xA0700044
Writing 0x00000005 @ address 0xA0700048
Writing 0x00000005 @ address 0xA070004C
Writing 0x00000001 @ address 0xA0700054
Writing 0x00000001 @ address 0xA0700058
Writing 0x00000680 @ address 0xA0700100
Writing 0x00000680 @ address 0xA0700120
Writing 0x00000680 @ address 0xA0700140
Writing 0x00000680 @ address 0xA0700160
Writing 0x00000202 @ address 0xA0700104
Writing 0x00000202 @ address 0xA0700124
Writing 0x00000202 @ address 0xA0700144
Writing 0x00000202 @ address 0xA0700164
Writing 0x00000103 @ address 0xA0700020
Writing 0x00000001 @ address 0xA0700024
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Writing 0x00000049 @ address 0xA0700024
Writing 0x00000083 @ address 0xA0700020
Reading from address 0x00023000 (Data = 0x00000000)
Writing 0x00000003 @ address 0xA0700020
Writing 0x00080680 @ address 0xA0700100
Writing 0x00080680 @ address 0xA0700120
Writing 0x00080680 @ address 0xA0700140
Writing 0x00080680 @ address 0xA0700160
Read 4 bytes @ address 0x00000000 (Data = 0x00000001)
Downloading 4 bytes @ address 0x00000000
Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
Downloading 4 bytes @ address 0x01000000
Read 4 bytes @ address 0x00000000 (Data = 0x00000001)
Read 4 bytes @ address 0x01000000 (Data = 0x00000001)
Resetting target (halt with breakpoint @ address 0)
Writing 0x00000001 @ address 0xA0700000
Writing 0x00000006 @ address 0xA0700024
Writing 0x00000001 @ address 0xA0700028
Writing 0x00000001 @ address 0xA0700030
Writing 0x00000003 @ address 0xA0700034
Writing 0x00000005 @ address 0xA0700038
Writing 0x00000000 @ address 0xA070003C
Writing 0x00000004 @ address 0xA0700040
Writing 0x00000001 @ address 0xA0700044
Writing 0x00000005 @ address 0xA0700048
Writing 0x00000005 @ address 0xA070004C
Writing 0x00000001 @ address 0xA0700054
Writing 0x00000001 @ address 0xA0700058
Writing 0x00000480 @ address 0xA0700100
Writing 0x00000480 @ address 0xA0700120
Writing 0x00000480 @ address 0xA0700140
Writing 0x00000480 @ address 0xA0700160
Writing 0x00000202 @ address 0xA0700104
Writing 0x00000202 @ address 0xA0700124
Writing 0x00000202 @ address 0xA0700144
Writing 0x00000202 @ address 0xA0700164
Writing 0x00000103 @ address 0xA0700020
Writing 0x00000001 @ address 0xA0700024
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Writing 0x00000049 @ address 0xA0700024
Writing 0x00000083 @ address 0xA0700020
Reading from address 0x00023000 (Data = 0x00000000)
Writing 0x00000003 @ address 0xA0700020
Writing 0x00080480 @ address 0xA0700100
Writing 0x00080480 @ address 0xA0700120
Writing 0x00080480 @ address 0xA0700140
Writing 0x00080480 @ address 0xA0700160
Read 4 bytes @ address 0x00000000 (Data = 0x00000001)
Downloading 4 bytes @ address 0x00000000
Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
Downloading 4 bytes @ address 0x00000200
Read 4 bytes @ address 0x00000000 (Data = 0x00000001)
Read 4 bytes @ address 0x00000200 (Data = 0x00000001)
Resetting target (halt with breakpoint @ address 0)
Writing 0x00000001 @ address 0xA0700000
Writing 0x00000006 @ address 0xA0700024
Writing 0x00000001 @ address 0xA0700028
Writing 0x00000001 @ address 0xA0700030
Writing 0x00000003 @ address 0xA0700034
Writing 0x00000005 @ address 0xA0700038
Writing 0x00000000 @ address 0xA070003C
Writing 0x00000004 @ address 0xA0700040
Writing 0x00000001 @ address 0xA0700044
Writing 0x00000005 @ address 0xA0700048
Writing 0x00000005 @ address 0xA070004C
Writing 0x00000001 @ address 0xA0700054
Writing 0x00000001 @ address 0xA0700058
Writing 0x00000280 @ address 0xA0700100
Writing 0x00000280 @ address 0xA0700120
Writing 0x00000280 @ address 0xA0700140
Writing 0x00000280 @ address 0xA0700160
Writing 0x00000202 @ address 0xA0700104
Writing 0x00000202 @ address 0xA0700124
Writing 0x00000202 @ address 0xA0700144
Writing 0x00000202 @ address 0xA0700164
Writing 0x00000103 @ address 0xA0700020
Writing 0x00000001 @ address 0xA0700024
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Writing 0x00000002 @ address 0xA0900000
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Reading from address 0xA0900000 (Data = 0x00000000)
Writing 0x00000049 @ address 0xA0700024
Writing 0x00000083 @ address 0xA0700020
Reading from address 0x00011800 (Data = 0x00000000)
Writing 0x00000003 @ address 0xA0700020
Writing 0x00080280 @ address 0xA0700100
Writing 0x00080280 @ address 0xA0700120
Writing 0x00080280 @ address 0xA0700140
Writing 0x00080280 @ address 0xA0700160
Writing 0x0201683F @ address 0xA090017C
Writing register (CPSR = 0x000000D3)
Reading register (CPSR = 0x000000D3)
JTAG speed set to 15000 kHz
Downloading 104 bytes @ address 0x00004000
Downloading 512 bytes @ address 0x00004070
ERROR: Write memory error @ address 0x00004000, word access: Core error.
Connection to debugger closed !



J-Link connected
Firmware: J-Link V9 compiled Oct 18 2012 19:49:50
Hardware: V9.00
S/N: 59104542
Feature(s): GDB

J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x27926031 (ARM9)
asked Mar 10, 2014 in NET+OS by K.K New to the Community (2 points)

Please log in or register to answer this question.

1 Answer

0 votes
i never tried to use generic segger debugger, however i hope the debugger scripts in C:\netos75\debugger_files folder will help you
answered Mar 10, 2014 by tuxembb Veteran of the Digi Community (288 points)
I Thank for your cooperation.
In my case, the memory-related error was driven out by editing the following files.

$(NETOS_DIR)/debugger_files/.gdbcc9p9215_a.jlink

    #monitor speed 15000
    monitor speed 8000

However, the following errors are displayed on Console of ESP.  What should I do next?

    No source file named image.elf.
...