RE: [ECOS] Help on reboot porting to EPXA1 board(Altera ExcaliburARM). Thanks

["Qiang Huang" <jameshq at liverpool dot ac dot uk>]

Thanks Gary.

But how can I connect it to GDB, the redboot I built how can I sure it can
work with GDB? Shouldn't the redboot output some message when it start up?
(Can't I see it via the HyperTerminal?)

BTW there is something strange when I download the redboot into flash:

[SOPC Builder]$ exc_flash_programmer -v -p -e 0 redboot.hex

Altera Excalibur Flash Programmer
Version 2.1 Build 189 09/05/2002 Service Pack 1 SJ Full Version
Copyright (C) 1991-2002 Altera Corporation

Using JTAG cable "ByteBlasterMV [LPT1]"
Using Excalibur EPXA1 (device 1 of 2)
Detected input clock reference at 25.009492MHz
Using 4MByte device (Bottom Boot, Intel compatible) attached to EBI0

Programming (with verify) offsets 00000000h to 00018c8bh
from file: redboot.hex

Percent Complete:  0__________25__________50__________75__________100

............................................................................
.......................................................

Warning: The hex file has specified an non-zero execution start address
of c1800040h, which is beyond the maximum offset of 00018c8bh

Flash programmed and verified successfully


Anything suspicious here?

Thanks a lot.

-----Original Message-----
From: Gary D. Thomas [mailto:gary.thomas@mind.be]
Sent: 07 February 2003 16:30
To: Qiang Huang
Cc: eCos Discussion
Subject: Re: [ECOS] Help on reboot porting to EPXA1 board(Altera
ExcaliburARM). Thanks


On Fri, 2003-02-07 at 09:21, Qiang Huang wrote:
> Hi all:
>    I tried to develop a port for EPXA1 board(similar to Altera Excalibur
> (EPXA10) board). I used the code as the base and made the changes. when I
> download the redboot to the platform, (with the debug enable) I can see
> "ABCDEFGHIJ" (these outputs are from the PLATFORM_SETUP1 macro) , "gedcba"
> (these are the output from LED in vector.S)
>

This looks like an endian problem.

> I also checked that the console is mangled to comm_channel[0] while debug
is
> on the comm_channel[1].  The output from the debug channel is ok but when
I
> call diag_printf("Hello!");
> there is nothing.  putDebugChar (int c) is working properly. and when the
> reboot started it keeps sending out s series of strange strings as:
> $T0a0f:ec9c8001;0d:24bd8101;#1c    and whenever I typed the keyboard it
> reproduced this message again.  I have been playing with this problem for
> days and almost out of idea now, so could anyone give me a hand on this
> Thank you very much.

These aren't "strange" at all!  They come from GDB (many, many
messages in the archives about this!)

Try connecting to your board with GDB and it will tell you
what's up (hint: there was some sort of error, probably accessing
illegal memory or some such.  Get GDB to tell you the PC and then
poke around a bit to see why it happened and where)

--
.--------------------------------------------------------.
|       Mind: Embedded Linux and eCos Development        |
|--------------------------------------------------------|
| Gary Thomas              email:  gary.thomas@mind.be   |
| Mind ( http://mind.be )  tel:    +1 (970) 229-1963     |
| gpg: http://www.chez-thomas.org/gary/gpg_key.asc       |
'--------------------------------------------------------'


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