Problems initializing network on mcf5235BCC

Joel Sherrill joel.sherrill at oarcorp.com
Mon Jul 2 15:36:47 UTC 2007


Good news!!

I am not comfortable editing the assembly code based on the
description.  Can you either diff the file for the changes or send
me the modified file?

Thanks.

--joel

CWolfe at motioncontrol.org wrote:
> A heads up/update.... 
> Soheilla discovered a flaw in the initialization code in the bsp ....
> the starts.s file needs to enable the second sram port so the fec can access it.....
>
> IAW the RM's chapter/section 6.2 
> to enable the 2nd sram port, include the following in start.s in the bsp folder (recompile of 
> rtems,etc. will be required)
>
>     move.l  #0x20000201, d0 
>     move.l   d0,(0x40000008)      | set up 2nd RAMBAR to make 2nd port avail to FEC   
>    
>
> this allows the fec initialization code to complete. 
> whether or not it is initializing properly is unknown just yet, but i think it's probably a safe bet.
> now I have to get the webserver running, but I don't forsee too many complications there....
>
> This also explains why alan was able to get them working with gdb and why Mike Bertosh 
> never discovered the problem... the initialization code for gdb initializes those sram ports 
> ...........
>
> thanks both for your immeasurable help 
> Regards,
> Christopher Wolfe
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>   




More information about the users mailing list