public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: prathika <prathika@deeopl.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UART2 Console in u-boot
Date: Sat, 25 Apr 2009 12:01:05 +0530	[thread overview]
Message-ID: <49F2AE29.20203@deeopl.com> (raw)
In-Reply-To: <49F28D35.7060003@deeopl.com>

hi,
I got things working on UART2 as console....but i still have issues in 
relocating..
its problem in my hardware...so things are going on well...
thank u Mr.Stefan for the help extended........

Thanks & Regards,
Prathika R


prathika wrote:
> hi,
>
> i did add the UART2 in the serial multi infrastructure at the end of 
> my serial.c.
> i have also configured GPIO registers for enabling UART2 Tx and Rx lines.
> As I understand, these lines are also multiplexed with the boot strap 
> lines of the PowerPC 440EP. Will this create any issue in the 
> performance?
> As I already mentioned I have enabled #define CONFIG_UART2_CONSOLE and
>
> #define UART2_BASE    CFG_PERIPHERAL_BASE + 0x500
>
> You have mentioned to enable the UART2 as default stdin and 
> stdout...where do I enable that??
>
> Thanks & Regards,
> Prathika R
>
>
> Stefan Roese wrote:
>> On Friday 17 April 2009, prathika wrote:
>>  
>>> i have ported u-boot this way to my board with few changes in the 
>>> u-boot
>>> source code and the board is up and i have tested stand alone
>>> application execution also.
>>>     
>>
>> So you did a "real" board port to your custom board? Or did you 
>> "just" change the yosemite files?
>>
>>  
>>> Now as my requirement is that my console should be on UART2 as my UART0
>>> and UART1 are coming out as RS 422 lines and only UART2 is RS232. I did
>>> some patch up work on UART0 lines and tested my u-boot porting.
>>>     
>>
>> Ah, I though you wanted the console on UART1. Ok, then my solution 
>> does not work for you.
>>
>>  
>>> I added a line
>>>
>>> #define UART2_BASE    CFG_PERIPHERAL_BASE + 0x500
>>>
>>> I have now changed as below and I commented checking for #define
>>> UART0_CONSOLE and #define UART1_CONSOLE:
>>>
>>> #define UARTBASE    UART2_BASE
>>>
>>> Is this OK??
>>>     
>>
>> Best would be to add the 3rd UART (UART2) to the SERIAL_MULTI 
>> infrastructure (see end of serial.c) and use this device as 
>> "stdin/stdout/.." in your default environment.
>>
>> Best regards,
>> Stefan
>>
>> =====================================================================
>> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
>> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
>> =====================================================================
>>   
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>   

      reply	other threads:[~2009-04-25  6:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  8:28 [U-Boot] UART2 Console in u-boot prathika
2009-04-17  9:07 ` Stefan Roese
2009-04-17  9:27   ` prathika
2009-04-17  9:37     ` Stefan Roese
2009-04-20  3:50       ` prathika
2009-04-25  4:10       ` prathika
2009-04-25  6:31         ` prathika [this message]

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=49F2AE29.20203@deeopl.com \
    --to=prathika@deeopl.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