public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] problem building redboot - very strange
@ 2001-09-10 11:24 Ravi Kumar B S
  2001-09-10 13:18 ` Jonathan Larmour
  2001-09-16  9:25 ` [ECOS] RedBoot timer Pushparaj
  0 siblings, 2 replies; 5+ messages in thread
From: Ravi Kumar B S @ 2001-09-10 11:24 UTC (permalink / raw)
  To: ecos-discuss

hi,

i am facing a problem in building redboot. the redbot is for ARM evaluator 7t
board and i am working on linux 7.1, kernel 2.4.2, gcc 2.95.2(arm-elf-gcc).
i did following things.

ecosconfig new e7t redboot
ecosconfig add flash
ecosconfig tree
make

i got the following error
arm-elf-gcc -mcpu=arm7tdmi -mno-short-load-words -Wl,--gc-sections
-Wl,-static -g -nostdlib
-L/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib -Ttarget.ld -o
/u/ARM/new-ecos/ecos/packages/redboot-work/install/bin/redboot.elf
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/version.o
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/extras.o: In function
`do_load':
/u/ARM/new-ecos/ecos/packages/redboot/current/src/load.c:337: undefined
reference to `flash_code_overlaps'
/u/ARM/new-ecos/ecos/packages/redboot/current/src/load.c:410: undefined
reference to `flash_code_overlaps'
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/extras.o: In function
`fis_create':
/u/ARM/new-ecos/ecos/packages/redboot/current/src/flash.c:603: undefined
reference to `flash_code_overlaps'
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/libtarget.a(io_flash_f
lash.o): In function `flash_errmsg':
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:417: undefined
reference to `flash_hwr_init'
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:445: undefined
reference to `flash_erase_block'
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:447: undefined
reference to `flash_hwr_map_error'
/u/ARM/new-ecos/ecos/packages/redboot-work/install/lib/libtarget.a(io_flash_f
lash.o): In function `flash_program':
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:274: undefined
reference to `flash_hwr_map_error'
/u/ARM/new-ecos/ecos/packages/io/flash/current/src/flash.c:294: undefined
reference to `flash_program_buf'
collect2: ld returned 1 exit status
make[1]: ***
[/u/ARM/new-ecos/ecos/packages/redboot-work/install/bin/redboot.elf] Error 1
make[1]: Leaving directory
`/u/ARM/new-ecos/ecos/packages/redboot-work/redboot/current'
make: *** [build] Error 2

here are certain interesting results.
1. but if i see load.c file there is no occurence of flash_code_overlaps at
all.
2. i am able to build the redboot image if i dont add flash(i.e without
ecosconfig add flash). in this case the build goes fine.
3. but i am able to build redboot with flash support on a different machine
which is using the same tools.

can some body give some clue to fix this problem

regards,

ravi kumar





^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ECOS] problem building redboot - very strange
  2001-09-10 11:24 [ECOS] problem building redboot - very strange Ravi Kumar B S
@ 2001-09-10 13:18 ` Jonathan Larmour
  2001-09-16  9:25 ` [ECOS] RedBoot timer Pushparaj
  1 sibling, 0 replies; 5+ messages in thread
From: Jonathan Larmour @ 2001-09-10 13:18 UTC (permalink / raw)
  To: Ravi Kumar B S; +Cc: ecos-discuss

Ravi Kumar B S wrote:
> 
> here are certain interesting results.
> 1. but if i see load.c file there is no occurence of flash_code_overlaps at
> all.

It maybe just got a bit confused about the error message.

> 2. i am able to build the redboot image if i dont add flash(i.e without
> ecosconfig add flash). in this case the build goes fine.
> 3. but i am able to build redboot with flash support on a different machine
> which is using the same tools.

For the e7t? That's pretty impressive since the e7t doesn't have a flash
device driver!

The configuration could probably be better: it should refuse to configure
at all rather than get as far as linking.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [ECOS] RedBoot timer
  2001-09-10 11:24 [ECOS] problem building redboot - very strange Ravi Kumar B S
  2001-09-10 13:18 ` Jonathan Larmour
@ 2001-09-16  9:25 ` Pushparaj
  2001-09-16 15:32   ` Gary Thomas
  2001-09-17  2:15   ` Jesper Skov
  1 sibling, 2 replies; 5+ messages in thread
From: Pushparaj @ 2001-09-16  9:25 UTC (permalink / raw)
  To: ecos-discuss

Hi,
I am working on porting of RedBoot on powerpc platform.
Presently I am facing problems with implementing the redboot timer. I cannot
figure out how to implement the function CYGACC_CALL_IF_DELAY_US.  This I guess
is supposed to give a delay for the parameter passed and should not be interrupt
driven and also that it should be some kind of loop.
Could anybody help on this ?


Regards,
Pushparaj

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ECOS] RedBoot timer
  2001-09-16  9:25 ` [ECOS] RedBoot timer Pushparaj
@ 2001-09-16 15:32   ` Gary Thomas
  2001-09-17  2:15   ` Jesper Skov
  1 sibling, 0 replies; 5+ messages in thread
From: Gary Thomas @ 2001-09-16 15:32 UTC (permalink / raw)
  To: pushparaja; +Cc: eCos Discussion

On Mon, 2001-09-17 at 01:27, Pushparaj wrote:
> Hi,
> I am working on porting of RedBoot on powerpc platform.
> Presently I am facing problems with implementing the redboot timer. I cannot
> figure out how to implement the function CYGACC_CALL_IF_DELAY_US.  This I guess
> is supposed to give a delay for the parameter passed and should not be interrupt
> driven and also that it should be some kind of loop.
> Could anybody help on this ?

This is exactly what's required of the function - pause for some number
of microseconds (the parameter), without using interrupts and without
disturbing any system resources (e.g. you can't go about reprogramming
the timer used by eCos heartbeat, etc).

There are many examples of this function in the sources.  In most cases,
the macro yields a call to a HAL supplied routine 'hal_delay_us'.  Just 
have a look at them to see how it's done.

Note: on the PowerPC, you can probably just use one of the solutions 
already in place.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ECOS] RedBoot timer
  2001-09-16  9:25 ` [ECOS] RedBoot timer Pushparaj
  2001-09-16 15:32   ` Gary Thomas
@ 2001-09-17  2:15   ` Jesper Skov
  1 sibling, 0 replies; 5+ messages in thread
From: Jesper Skov @ 2001-09-17  2:15 UTC (permalink / raw)
  To: pushparaja; +Cc: ecos-discuss

>>>>> "Pushparaj" == Pushparaj  <pushparaja@multitech.co.in> writes:

Pushparaj> Hi, I am working on porting of RedBoot on powerpc platform.
Pushparaj> Presently I am facing problems with implementing the
Pushparaj> redboot timer. I cannot figure out how to implement the
Pushparaj> function CYGACC_CALL_IF_DELAY_US.  This I guess is supposed
Pushparaj> to give a delay for the parameter passed and should not be
Pushparaj> interrupt driven and also that it should be some kind of
Pushparaj> loop.  Could anybody help on this ?

Look in the HAL sources for existing implementations.

Jesper

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-09-17  2:15 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-09-10 11:24 [ECOS] problem building redboot - very strange Ravi Kumar B S
2001-09-10 13:18 ` Jonathan Larmour
2001-09-16  9:25 ` [ECOS] RedBoot timer Pushparaj
2001-09-16 15:32   ` Gary Thomas
2001-09-17  2:15   ` Jesper Skov

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).