public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Ali Sina <replay688@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Porting eCos / Redboot / Memory map modifications / E7T
Date: Sun, 16 Oct 2005 21:21:00 -0000	[thread overview]
Message-ID: <20051016211751.GA7087@lunn.ch> (raw)
In-Reply-To: <BAY108-F2123D809E64E07DD706CC5EA7F0@phx.gbl>

On Sun, Oct 16, 2005 at 08:46:53PM +0000, Ali Sina wrote:
> Thanks Andrew,
> we finally got the memory recognized by properly modifying the 3 files.
> Indeed, modification of hal_platform_setup.h was necessary.
> 
> Now the next two questions arise:
> 
> 1. I would like to make Redboot the only bootloader on the system and get 
> rid of the ARM BSL. Can this be done reasonably easy on the E7T?
> I understand that Redboot needs to be told to start at 0x01800000 instead 
> of 0x01820000. I have proceeded along the instructions provided here-> 
> http://www.kozio.com/technology/tech_briefs/ChangingRedBootsStartingAddress/
> and put the RB binary in the flash via Wiggler, but the image will not 
> boot. Am I missing something?

The code for the eCos E7T in the repository has RedBoot as the only
boot loader. So you might want to compare your code with the E7T code
and see what is different....

 
> 2. It seems that upon start Redboot is doing _something_ on UART0 of the 
> E7T platform - which is the user UART, while UART1 is used for console 
> communication /debug. This is a problem because the application assumes 
> external equipment to be attached to UART0 and whatever is send out of 
> UART0 by Redboot causes the external equipment (which we cannot change or 
> control) to crash.
> Also, UART1 is assumed to be used for communication purposes, and the roles 
> cannot be switched because of the way our hardware is built.
> After some investigation I concluded that this _something_ might be Redboot 
> trying to find a channel to use for console communication. Looking briefly 
> at the RB source I did not see anything right away. Any ideas of how to fix 
> this?

If you look in packages/hal/arm/e7t/current/src/hal_diag.c you will
see it defines two e7t_ser_channels. One is for UART0 and the other is
for UART1. Try disabling UART0. 

        Andrew

-- 
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:[~2005-10-16 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 10:52 Ali Sina
2005-09-28 11:17 ` Andrew Lunn
2005-10-16 20:46   ` Ali Sina
2005-10-16 21:21     ` Andrew Lunn [this message]
2005-10-23 10:10       ` Ali Sina
2005-10-23 11:10         ` Andrew Lunn
2005-10-24  7:49           ` Andrew Lunn

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=20051016211751.GA7087@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=replay688@hotmail.com \
    /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).