From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: wwarren@emacinc.com
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel
Date: Sat, 06 Oct 2012 11:46:04 +0200 [thread overview]
Message-ID: <506FFDDC.60104@xenomai.org> (raw)
In-Reply-To: <5afa3b9a7c7daf116f8284b4f255227e.squirrel@mail.emacinc.com>
On 10/06/2012 06:29 AM, Wayne Warren wrote:
> Gilles,
>
> I should have mentioned this earlier... I did as you mentioned in one of
> your previous e-mails and added DEBUG_LL_OMAP3(3, am3517evm) after finding
> that this string corresponds to the processor id passed to the linux
> kernel from u-boot (unless I am misunderstanding how that works). This
> applies to all the kernels I built and tested as described in my previous
> two e-mails.
>
> Thanks for your patience, and sorry for the confusion!
Ok, but for some reason, that is probably what is not working. Are you
sure that:
- the am3517 uart has the same address and registers as an omap3 uart?
- that the serial console is on UART3 ?
- the uart registers range is mapped where the code in debug-macro.S
expects it?
I never had to debug this, but if I had to, I would try to find what are
the values used by the decompressor for the uart physical and virutal
addresses and check whether the virtual adress is really mapped.
If your kernel does not start with CONFIG_IPIPE, earlyprintk does not
work, and you do not have a JTAG probe, you can try toggling some GPIOs
to light some LEDS.
--
Gilles.
next prev parent reply other threads:[~2012-10-06 9:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 21:08 [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel Wayne Warren
2012-10-02 21:32 ` Gilles Chanteperdrix
2012-10-02 21:35 ` Gilles Chanteperdrix
2012-10-04 16:57 ` Wayne Warren
2012-10-04 17:09 ` Gilles Chanteperdrix
2012-10-04 18:02 ` Gilles Chanteperdrix
2012-10-05 8:06 ` Gilles Chanteperdrix
2012-10-05 18:47 ` Wayne Warren
2012-10-05 20:16 ` Gilles Chanteperdrix
2012-10-05 21:47 ` Wayne Warren
2012-10-05 22:43 ` Gilles Chanteperdrix
2012-10-06 4:29 ` Wayne Warren
2012-10-06 9:46 ` Gilles Chanteperdrix [this message]
2012-10-09 20:55 ` Wayne Warren
2012-10-09 21:12 ` Gilles Chanteperdrix
2012-10-19 21:22 ` Wayne Warren
2012-10-20 1:33 ` Gilles Chanteperdrix
2012-10-22 19:22 ` Wayne Warren
2012-10-22 19:25 ` Gilles Chanteperdrix
2012-10-22 19:34 ` Wayne Warren
2012-10-22 21:12 ` Gilles Chanteperdrix
2012-10-23 15:32 ` Wayne Warren
2012-10-23 20:12 ` Gilles Chanteperdrix
2012-10-24 17:32 ` Wayne Warren
2012-10-24 17:38 ` Gilles Chanteperdrix
2012-10-24 17:55 ` Wayne Warren
2012-10-24 18:05 ` Gilles Chanteperdrix
2012-10-24 18:26 ` Wayne Warren
2012-10-24 18:36 ` Gilles Chanteperdrix
2012-10-24 17:36 ` Wayne Warren
2012-10-24 17:57 ` Gilles Chanteperdrix
2012-10-20 8:24 ` Gilles Chanteperdrix
2012-10-19 21:32 ` Wayne Warren
2012-10-20 1:36 ` Gilles Chanteperdrix
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=506FFDDC.60104@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=wwarren@emacinc.com \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.