From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001426] HAL for Kinetis Kwikstik
Date: Thu, 15 Mar 2012 12:55:00 -0000 [thread overview]
Message-ID: <20120315125444.0288A2F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001426-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001426
--- Comment #11 from Ilija Kocho <ilijak@siva.com.mk> 2012-03-15 12:54:40 GMT ---
(In reply to comment #10)
> Tomas, have you been using ROM startup with KwikStik mainly? Or RAM startup
> with stubs? Or RAM startup without stubs? Have you been using the J-Link GDB
> server? Just interested in what might be a good (well tested) place to start
> experimenting.
Hi John
FYI PEEDI has JTAG/SWD support for Kinetis including flashing. (you mentioned
in some conversation so I assume you might have one).
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-03-15 12:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 10:59 [Bug 1001426] New: " bugzilla-daemon
2011-12-21 17:56 ` [Bug 1001426] " bugzilla-daemon
2011-12-21 18:40 ` bugzilla-daemon
2012-01-09 20:25 ` bugzilla-daemon
2012-01-11 11:33 ` bugzilla-daemon
2012-01-11 11:56 ` bugzilla-daemon
2012-02-23 16:06 ` bugzilla-daemon
2012-02-23 16:09 ` bugzilla-daemon
2012-03-11 14:36 ` bugzilla-daemon
2012-03-12 8:13 ` bugzilla-daemon
2012-03-15 12:22 ` bugzilla-daemon
2012-03-15 12:55 ` bugzilla-daemon [this message]
2012-03-18 21:08 ` bugzilla-daemon
2012-03-26 16:05 ` bugzilla-daemon
2012-03-30 14:58 ` bugzilla-daemon
2012-03-30 15:02 ` bugzilla-daemon
2012-05-04 18:32 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120315125444.0288A2F78001@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).