Hello,
I have added the script to the target and it is working !!!
Download is working and debugging is working also.
Thanks for your help & have a nice week
Schöne grüße aus Deutschland
PS: please could you add that script in the K60-target standard script (or docu
) . I think I will not be the only user having that problem.
( it is a little confusing because the Kinetis is stopped before starting gdb;
on the other hand - having a first look at - it is running more stable than
j-link and OSBDM )
I will do excessive tests with openocd + Kinetis next week.... perhaps it was
not the only problem :-)I
Hello,
try this in your target configuration:
$_TARGETNAME configure -event gdb-attach {
echo "Halting target"
halt
}
If gdb connect the target is halted.
Regards,
Mathias
On 20.01.2012 11:20, thomas haas wrote:
>
> Hello,
> thanks for that very quick reply!
>
> I use hardware similar to amontec jtagkey. I use zylin plugin with the script
> "zylingdb.txt" (see
> attached; just reset core and load elf-file/symbols)
>
> 1) start openocd with towerK60-skript and start gdb via Eclipse : see try1.txt
> do the same but use -d 3 option (hard stuff for a beginner ...) : see
>try1_d=3.txt
>
> 2) add "gdb_memory_map disable" to towerK60 script; start openocd with
> towerK60-skript and start
> gdb via Eclipse : see try2.txt
> do the same but use -d 3 option (hard stuff for a beginner ...) : see
>try2_d=3.txt
>
> kind regards & thanks for your help
>
> ( I am aware of speed problems; so speed is 500 what should be ok with very
> short cables and low
> impedance)
>
> Hello,
>
> i use the kinetis kwikstick tcl/board/kwikstik.cfg and this device works. I
> have never used it with
> gdb. Can you start openocd with the -d parameter and check what happens?
>
>
> Regards,
>
> Mathias
>
> On 20.01.2012 09:07, thomas haas wrote:
>>
>> Hello OpenOcd-Team,
>> first of all thanks for that great tool that is working perfectly with
>> Stellaris Ti. I am using
>> latest source from git. The built is done for windows with original latest
>> ftdi-driver. I am using a
>> amontec-jtagkey kompatibel hardware, and ICDI from TI also. The toolchain is
>> Eclipse CDT with
>> yagarto toolchain (4.6.x).
>> I have a kinetis K60 tower also. I have connected the tower with the jtagkey
>> compatible hardware and
>> started the debugger with the tower-board-configuration. The debugger is
>> starting correctly (ID is
>> recognized , watchpoints and breakpoints are correct). But when I try to
>> start debugging the system
>> fails.
>> A script with flashing the elf-file only is working, but starting gdb the
>> openocd fails. I added
>> the "gdb_memory_map disable". I that case the openocd did work, but (of
>> cause) the gdb "load"
>> commando did not work.
>> Are there any experience with K60 -tower from Kinetis ? I am also using the
>> j-Trace from Segger in
>> parallel (with the segger gdb-server). Segger also seems to have problems
>> with the K60 (the gdb
>> shows re-starts), but with newer versions it is working. I would be happy to
>> get some helpful hints.
>> Thanks------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
