From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to enable to print messages on serial port(ttyS0) in u-boot?
Date: Thu, 22 Oct 2009 08:49:13 -0400 [thread overview]
Message-ID: <4AE054C9.2020306@ge.com> (raw)
In-Reply-To: <532dd5840910220518h4df2fe9cy7e66f043a2acd4fc@mail.gmail.com>
Hi Ravi,
Ravi Kumar Kulkarni wrote:
>
> >>Yes, printf(), as you can see by looking at the source. The serial
> port and printf() support is one of the first things that is
> >>configured exactly to help debug via print statements.
> >>If it isn't working on your board, you have more fundamental problems
> (hardware initialization, serial port configuration,
> >>serial port selection, who knows???). Since we don't know anything
> about your board, we cannot help further.
Please use plain text formatting, not HTML. Your quoting will be more
readable and it won't annoy us curmudgeons.
> Hi ! Now im being able to get print on the serial console. My board is
> workin fine . its at91sam9261. the problem is something else. i have
> written a driver spi-new.c for the SPI interface using BUS 1 . now
> though this driver is getting compiled but its not getting executed
> when my board boots up . i have modified the following to u-boot source
> tree.
> 1) changed Makefile in /drivers/spi/ and added a line
> COBJS-$(CONFIG_ATMEL_SPI) +=spi-new.o
> 2) changed config file in /include/configs/at91sam9261ek.h
> added a line
> # CONFIG_ATMEL_SPI 1
I see you actually used "#define"
> though my init function is getting executed in the board file located
> at /board/atmel/at91sam9261ek/at91sam9261ek.c
OK, sounds like you succeeded.
> my driver code is not gettung executed when my board boots up.
> can anyone let me know where else to change to add a new driver in
> u-boot so tat ur board recognizes it.
Since you have succeeded in inserting your new driver in your u-boot
image, it is available. You need to browse the SPI
functionality/framework in u-boot to figure out how to plug your new SPI
driver into the existing code and how to use it.
The statement "my driver code is not gettung[sic] executed when my board
boots up" is too vague for us to address. What do you expect u-boot /
your driver to do when it boots up (that it isn't already doing)?
> warm regards,
> Ravi Kulkarni.
Good luck,
gvb
next prev parent reply other threads:[~2009-10-22 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 5:11 [U-Boot] How to enable to print messages on serial port(ttyS0) in u-boot? sunr2007
2009-10-22 12:04 ` Jerry Van Baren
2009-10-22 12:18 ` Ravi Kumar Kulkarni
2009-10-22 12:34 ` Wolfgang Denk
2009-10-22 12:41 ` Ravi Kumar Kulkarni
2009-10-22 12:49 ` Jerry Van Baren [this message]
2009-10-22 13:01 ` Ravi Kumar Kulkarni
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=4AE054C9.2020306@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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