public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Michael Jones <mjones@linear.com>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Kinetis CYG_HAL_STARTUP_VAR conflict
Date: Sat, 01 Dec 2012 21:07:00 -0000	[thread overview]
Message-ID: <88A5F92E-1AE1-4246-B566-3EFE5DEA360B@linear.com> (raw)

BACKGROUND
----------------------

I am having a little bit of trouble trying to get my first hello world app on a K60 Tower Board.

I have RedBoot running from ROM and I can ping the ethernet port, so presumably I will eventually get GDB to talk to it.

I am having trouble building an initial app that uses the ROM monitor. Following the example in the eCos book, I went hunting for CYGSEM_HAL_USE_ROM_MONITOR, enabled it and then set startup to SRAM. This seems the obvious way to run and debug.

PROBLEM
--------------

I am getting a conflict I don't know how to resolve. I have set CYG_HAL_STARTUP_VAR = SRAM. This results in CYG_HAL_STARTUP = SRAM by calculation.

But I get a conflict from CYGSEM_HAL_USE_ROM_MONITOR that wants CYG_HAL_STARTUP == RAM

QUESTIONS
-----------------

1) Can I ignore this conflict and get the monitor and app to work?

2) Is there a better approach?

3) Has anyone succeeded to use RedBoot on the K60 and can you supply an example config project that works that I can look at?

Thanks,

Mike

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2012-12-01 21:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01 21:07 Michael Jones [this message]
2012-12-02  7:13 ` Michael Jones
2012-12-02 10:12 ` Ilija Kocho
2012-12-02 15:44   ` Michael Jones
2012-12-02 16:52     ` Ilija Kocho
2012-12-02 17:53       ` Michael Jones
2012-12-02 19:14         ` Ilija Kocho
2012-12-02 20:58         ` Ilija Kocho
2012-12-03  0:01   ` Michael Jones
2012-12-03 19:13     ` Ilija Kocho
2012-12-04  2:18       ` Michael Jones
2012-12-04  2:31         ` Michael Jones
2012-12-04  5:32       ` Michael Jones
2012-12-04  8:42         ` Ilija Kocho
2012-12-04  8:51           ` 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=88A5F92E-1AE1-4246-B566-3EFE5DEA360B@linear.com \
    --to=mjones@linear.com \
    --cc=ecos-discuss@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).