This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: AT91EB40 and RedBoot


On Fri, 2002-06-07 at 19:05, Scott Dattalo wrote:
> On 7 Jun 2002, Gary Thomas wrote:
> 
> > On Fri, 2002-06-07 at 18:15, Scott Dattalo wrote:
> > > 
> > > The short question:
> > > 
> > > I can establish a communication link to my Atmel AT91EB40 evaluation board 
> > > with gdb (Insight). However, after I download the redboot_RAM.elf, I'm 
> > > unable to obtain a redboot prompt with minicom. The question is, well, why 
> > > not? Specifically (see below), how does one "interrupt 'Angel' with a 
> > > ^Z" after the RedBoot binary has been downloaded?
> 
> <snip>
> 
> > 
> > You don't run minicom at this point, but rather GDB.  Use the command
> > line form (-nw), not Insight.  Once you start up GDB, you'll be talking
> > (via GDB) to the Angel on the board.  Download the RedBoot image and 
> > start it.  Then simply type ^Z - this will send the GDB session into
> > the background and you can then connect via minicom.  Once you do
> > that, you'll be able to talk to RedBoot via its command line interface.
> 
> Wow, that was a really quick response. Invoking gdb with -nw enabled the 
> ^Z background trick. I should have caught that...
> 
> However, minicom is still unable to establish a serial link with the 
> AT91EB40 serial port. I've invoked minicom with and without -o. I've tried 
> 9600 and 38.4k. The only way I can establish a minicom <-> EB40 link is by 
> setting the Baud to 9600in minicom and resetting the EB40. Minicom will 
> display the start up header (but obviously is unable to sustain the 
> communication).
> 
> Any idea what else may be happening?

Are you sure that you loaded & started RedBoot (using the 'load' and
'continue' commands) before typing ^Z?

If you have started RedBoot, but still can't talk to it, something else
may be wrong.  I'm afraid you may be into "debug this on your own" 
territory.  What I would do is to add some code in 
  .../hal/arm/at91/current/include/hal_platform_setup.h
in the path for RAM startup, put something that tickles the LEDs.  Then
you should be able to see it do something when it starts up, and maybe
carry on from there to get RedBoot running full steam.

Sorry I don't have any "pat" answers.  Good luck.


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]