ek-tm4c1294xl and openocd: memory write failure

Giuseppe Iellamo

Other Parts Discussed in Thread: EK-TM4C123GXL

Hi all,

I'm experimentig with the TIVA connected launchpad using a linux PC and a arm-none-eabi-gcc toolchain.

I'm able to build examples and to program the chip using lm4tools, but if try to use openocd (0.7.0) with the config file

#
# TI Tiva Launchpad ek-tm4c123gxl Evaluation Kits    
#
# http://www.ti.com/tool/ek-tm4c123gxl
#

#
# NOTE: using the bundled ICDI interface is optional!
# This interface is not ftdi based as previous boards were
#
source [find interface/ti-icdi.cfg]

set WORKAREASIZE 0x8000
set CHIPNAME tm4c129ncpdt
source [find target/stellaris_icdi.cfg]

I can connect to the board but when i try to load the code i got a memory write failure

$ arm-none-eabi-gdb hello.axf 
GNU gdb (GNU Tools for ARM Embedded Processors) 7.6.0.20140529-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-linux-gnu --target=arm-none-eabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/giellamo/work/giellamo/TI_stuff/GccMode/examples/boards/ek-tm4c1294xl/hello/gcc/hello.axf...done.
(gdb) target extended-remote :3333
Remote debugging using :3333
0x00000000 in g_pfnVectors ()
(gdb) monitor reset halt
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000560 msp: 0x20000204
(gdb) load
Loading section .text, size 0xff4 lma 0x0
Start address 0x564, load size 4084
Transfer rate: 8 KB/sec, 1361 bytes/write.
(gdb) monitor reset init
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000564 msp: 0x20000204
(gdb) c
Continuing.
Memory write failure!

On OOCD shell

[605] giellamo@dorne: ~/work/giellamo/TI_stuff/openocd/tcl $ sudo openocd --file lm4f.cfg 
Open On-Chip Debugger 0.7.0 (2013-10-22-08:31)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : This adapter doesn't support configurable speed
Info : ICDI Firmware version: 1224
Info : tm4c129ncpdt.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3333
Warn : Unknown did0 class
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000560 msp: 0x20000204
Error: memory write failed: 0x7
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000564 msp: 0x20000204
Error: Memory write failure!

over 9 years ago

0 Petrei over 9 years ago

Guru 26105 points

Hi,

AFAIK the 129 processor/Connected Launchpad was added in version 0.8.0 and the new script for this is as below:

#
# TI Tiva C Series ek-tm4c1294xl Launchpad Evaluation Kit
#
# http://www.ti.com/tool/ek-tm4c1294xl
#

source [find interface/ti-icdi.cfg]

set WORKAREASIZE 0x8000
set CHIPNAME tm4c1294ncpdt

source [find target/tiva_icdi.cfg]

Please note tiva_icdi.cfg instead stellaris_icdi.cfg

Petrei

0 Amit Ashara over 9 years ago in reply to Petrei

TI__Guru**** 244380 points

Hello Petrei

I believe 0.7.0 also did start supporting 129. Not been able to find that thread on OPENOCD forum

Regards

Amit

0 Giuseppe Iellamo over 9 years ago in reply to Petrei

Prodigy 220 points

Hi,

I've downloaded OOCD 0.8.0 but in the boards subdir there is only the

ek-tm4c123gxl.cfg file and not the 129 one and in the target ther is stellaris_icdi.cfg but not tiva...

0 Petrei over 9 years ago in reply to Giuseppe Iellamo

Guru 26105 points

Hi,

Then copy the snipped posted and name the file ek-tm4c129gxl.cfg and place it in boards subdir.

This is what i have and work with - I installed with brew (not on Windows...).

Observation - there could be a mistake in that file, first executable row is [find interface/ti_icdi.cfg] and after the name is repeated otherwise ... i use as shown ....

Petrei

0 Giuseppe Iellamo over 9 years ago in reply to Petrei

Prodigy 220 points

If I copy it will became the same I was using at the beginning and that didn't work...

0 Petrei over 9 years ago in reply to Giuseppe Iellamo

Guru 26105 points

HI,

I am using this: https://launchpad.net/gcc-arm-embedded - the executable is .elf, (not .axf) - that is specifically developed for ARM/Cortex micros.

Petrei

0 Giuseppe Iellamo over 9 years ago in reply to Petrei

Prodigy 220 points

Yes it's exactely the same toolchain I'm using.

By the way also the .axf is an elf file

file gcc/hello.axf

gcc/hello.axf: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, not stripped

0 Petrei over 9 years ago in reply to Giuseppe Iellamo

Guru 26105 points

Hi,

Looking on github - a patch for a bug concerning flash erase for ti-icdi was commited on Feb.25 this year - so if your version is prior this, may give you the error mentioned in first thread. Maybe would be wise to compile from github if you try this on Linux...

Petrei

Arm-based microcontrollers

Arm-based microcontrollers forum

ek-tm4c1294xl and openocd: memory write failure