Segger Base J-Link Emulator not working AM335x EVM

olegT · Jun 26th 2014, 2:09am

Hello,

I cannot get JTAG to connect reliably on the AM335x EVM (TMDXEVM3358)

) am using Ubuntu 12.04 LTS 32-bit VM image on 64-bit Windows 7 machine

I have

CCS version 5.5.00077

I have installed a Linux JLink driver as specified here
processors.wiki.ti.com/index.php/J-Link_Emulator_Support

I have updated a JLink driver from SEGGER site
sudo dpkg -i "jlink_4.86.1_i386.deb"
[sudo] password for user:
(Reading database ... 153788 files and directories currently installed.)
Preparing to replace jlink 4.85.4 (using jlink_4.86.1_i386.deb) ...
Unpacking replacement jlink ...
Setting up jlink (4.86.1) ...

I am using a Segger Base JLink Emulator.

I have created and launched Target Configuration that uses Segger emulator and AM3358 target.

I have removed the SD-card so that there is not u-boot image of any kind and reset the evm board and launched the Target Configuration.

If I try to connect to the board, I get :
"

Error connecting to the target:

ERROR in JLINKARM_Open"

However, If I run Segger's JLink Command utility before starting code composer: "

sudo JLinkExe -device AM3358 -if JTAG -speed
4000"

which then outputs:

SEGGER J-Link Commander V4.86a ('?' for help)
Compiled Jun 11 2014 17:45:10
Info: Device "AM3358" selected (0 KB flash, 0 KB RAM).
DLL version V4.86a, compiled Jun 11 2014 17:45:07
Firmware: J-Link ARM V8 compiled Nov 25 2013 19:20:08
Hardware: V8.00
S/N: <Serial number>
VTarget = 3.306V
Info: TotalIRLen = 6, IRPrint = 0x01
Info: TotalIRLen = 10, IRPrint = 0x0011
Info: CoreSight AP[0]: 0x04770001, AHB-AP
Info: CoreSight AP[1]: 0x04770002, APB-AP
Info: CoreSight AP[2]: 0x04760000, JTAG-AP
Info: Found Cortex-A8 r3p2
Info: 6 code breakpoints, 2 data breakpoints
Info: Debug architecture ARMv7.0
Info: Data endian: little
Info: Main ID register: 0x413FC082
Info: L1 (I-cache): 32 KB, 128 sets, LineSize 64 bytes, 4-way
Info: L1 (D-cache): 32 KB, 128 sets, LineSize 64 bytes, 4-way
Info: L2 (unified cache): 256 KB, 512 sets, LineSize 64 bytes, 8-way
Info: System control register:
Info: Instruction endian: little
Info: Level-1 instruction cache disabled
Info: Level-1 data cache disabled
Info: MMU disabled
Info: Branch prediction enabled
Found 2 JTAG devices, Total IRLen = 10:
#0 Id: 0x3BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#1 Id: 0x0B94402F, IRLen: 06, IRPrint: 0x1, TI ICEPick
Cortex-A8 identified.
Target interface speed: 4000 kHz

and then quit JLink Command Utility, start code composer studio and launch Target Configurationquite often I can connect to the board

Also if the board is reset I need to at least relaunch the target configuration in CCS. (Disconnecting, resetting the board and then connecting does not work).

SEGGER - Alex · Jul 2nd 2014, 10:03am

Hi,

First of all: It would be nice if you could assign a matching name to this thread... It is actually TI CCS + J-Link + AM3358 which makes problems.
J-Link and AM3358 in general work fine, according to the J-Link Commander output you sent.

Anyhow:
Is J-Link Commander reliably connecting to the AM3358 device?
Meaning that you only see the problems from inside CCS?

Firmware: J-Link ARM V8 compiled Nov 25 2013 19:20:08
Hardware: V8.00
S/N: <Serial number>
VTarget = 3.306V

Any particular reason to remove the serial number of your J-Link here?

Right now, it sounds a bit like a question for the TI CCS guys, since it seems to be a problem caused by the way CCS uses J-Link.
If J-Link Commander works, but CCS not, it is probably more a CCS specific/related problem than a J-Link one.

- Alex

Share