This is the mail archive of the ecos-discuss@sourceware.org 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]

Porting problem


Hi,

I've been trying to port redboot on a mips4kc(little endian)
customised board. I copied the hal directory for atlas mips4kc board
and made changes accordingly. I tried following the startup trace:
after going through the reset_vectors and entering _start, it dives
into the hal_cpu_init macro before it supposedly enters the
hal_diag_init() function. On each macro/function we used leds to check
the sequence of calls. However, when we try to place the led code in
the hal_diag_init function, the leds never light up i.e. the execution
path never goes through the function. Consequently, the serial driver
is not activated and we are stuck. One thing we know for sure is that
the hal_diag_init function does compile as putting a syntactically
incorrect string in that dunction generates a compile-time error.
However, the elf file which is created after compilation never shows
the entry of hal_diag_init when I generate a symbol table using 'nm'.
The hal_diag.o.d files is created in the board_build directory.

Q1. What could be the possible problem be?

Q2. I think hal_diag_init initailises the serial driver. What does
hal_if_diag_init do?

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


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