From: Ilija Kocho <ilijak@siva.com.mk>
To: Ken Yee <kenkyee@excite.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Date: Fri, 05 Oct 2012 18:57:00 -0000 [thread overview]
Message-ID: <506F2D7F.5080102@siva.com.mk> (raw)
In-Reply-To: <20121005141943.18945@web007.roc2.bluetie.com>
On 05.10.2012 20:19, Ken Yee wrote:
>> It's true for break points. The target code being in Flash, rather than
>> RAM, needs hardware break points that are not supported by RedBoor/eCos
>> GDB stubs at present.
> I'm actually using a Segger JLink for debugging...not using Redboot's gdb support.
> That's why I'm puzzled...I should be able to look at the code behind that macro or single step through the assembly code but I can't do anything w/ that IF_PUTC function.
Then I'm afraid I can't help you much. I would check whether the GDB
server is set for hardware break points.
>
>> Try the real (instead of diagnostic) serial driver.
> Is there a way to get "diag_printf" to use the real serial driver? Interesting that you hit the same issue...I always thought the diag_driver just used the same serial port but with interrupts disabled.
Yes, enable the respective tty<n> driver and set it as a console
(default is ttydiag).
But, actually you may have hardware problem (does it print barebone?).
If you power Kwikstik from it's own USB connector there is a voltage
drop on serial diode (I don't recal whether it was D6 or D7) that
hinders RS232.
Ilija
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2012-10-05 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 18:19 Ken Yee
2012-10-05 18:57 ` Ilija Kocho [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-08 22:40 Ken Yee
2012-10-05 1:43 Ken Yee
2012-10-05 10:21 ` Ilija Kocho
2012-09-26 20:39 Ken Yee
2012-09-26 20:49 ` Ilija Kocho
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=506F2D7F.5080102@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=kenkyee@excite.com \
/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).