From: "Sartakoff A. Wasiliy" <sartakoff@lightcom.ru>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ecos on lpc2378, context switching problem.
Date: Fri, 07 Mar 2008 12:58:00 -0000 [thread overview]
Message-ID: <200803071558.13933.sartakoff@lightcom.ru> (raw)
i think in this must be in discuss mails =)
Hi.
I have some problem with porting ecos on lpc2378.
i have a good worked redboot on lpc2210, and i try start it on new platform.
i changed platform_setup.h pll init, some correct UART and timer, and redboot
started on lpc2378. z-modem works too. but when i use "go 0" or something
else, i havnt context swtiching. good idea for looking on stack, but stack
placed in data segment, and i havnt problem with it. my chip rev. B(Y?), and
i use MAMRC 1, just in case.
can u help me? =)
--
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:[~2008-03-07 12:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200803071558.13933.sartakoff@lightcom.ru \
--to=sartakoff@lightcom.ru \
--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).