[ECOS] [Porting] target seemly hang up on 'hal_mon_init'

[Hu Yajun]

Hi  all,

         I'm trying to make RedBoot running on my target board, which is
based on MPC855T. I used the MBX as my template. In my view, when powering
up, target will go through the following routine:

         __exception_reset -> _start -> hal_hardware_init
->__hal_hardware_init_done->hal_mon_init -> .. -> cyg_start

         I've implemented my 'hal_hardware_init' in the board-initializing
file, 'erxx.S', which is attached for reference. I added some LED_flashing
code in the initializing sequences, which showed that the system couldn't
get through 'hal_mon_init', which is assembly macro defined in
hal/powerpc/mpc8xx/v2_0/include/variant.inc (for my target). I'ved view this
macro definition, it is supposed to copy exception vectors from ROM to RAM,
and initialize VSR and ISR environment, which also would write the RAM. Is
that my RAM couldn't be accessed by now? I've initialized the SDRAM and test
it in my 'hal_hardware_init', it seems okay. 

         Anyone had met such thing b4? Or any comments to solve my problem?
THANKS in advance.

                                                             yjhu


-------------- next part --------------
A non-text attachment was scrubbed...
Name: erxx.S
Type: application/octet-stream
Size: 15833 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20050919/e25f9b65/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vectors.S
Type: application/octet-stream
Size: 35480 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20050919/e25f9b65/attachment-0001.obj>
-------------- next part --------------
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss