Eboot stalls in OEMInitDebugSerial

Hi,

This is going back a bit but, i am trying to get a DBPXA255 Lubbock board
running with Win CE.net 4.1 with
Lubbock BSP. I have created an OS image and flashed eboot.nb0 from release
directory to
flash at address 0 with jflashmm tool.
When i boot i get the following on Hyperterminal :

*******Beginning System Initialization******* SDCLK[1] = MemClk/2
MemClk = 99.53 MHz
Run Mode = MemClk
Turbo Mode = 2 * Run Mode
Mode: RUN


Beginning SDRAM Scrub...
SDRAM Scrub Complete

Here it stalls, going into source code i can see its stalling in the
function OEMInitDebugSerial (called from main.c in Eboot src)
It is stalling in this function after it has called OEMInitDebugSerialKernel
(ie setup the FFUART) and just before
calling to OEMWriteDebugString (*****) so the banner full of ***********
doesn't come up. I've checked it stalls
here by inserting code to write to LEDS on the board. So probably UART
initialisation failed although i know hardware
is ok because i get the hyperterminal output above. Has anyone seen this
before. In my build options
i have Enable Img for Flash and Enable ship build checked.

Regards
ms

ms
Thu Mar 31 09:29:37 CST 2005

I rebuilt with PDA configuration rather than Internet Applicance and i
managed to get past
the stall below. I thought any required features just to get the bootloader
going would be all
in the BSP but it appears catalog features affect the build. Anyway now to
migrating the BSP
to WinCE 5.0!
"ms" <ms@discussions.microsoft.com> wrote in message
news:%23EdWmqcNFHA.1300@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> This is going back a bit but, i am trying to get a DBPXA255 Lubbock
board
> running with Win CE.net 4.1 with
> Lubbock BSP. I have created an OS image and flashed eboot.nb0 from
release
> directory to
> flash at address 0 with jflashmm tool.
> When i boot i get the following on Hyperterminal :
>
> *******Beginning System Initialization******* SDCLK[1] =
MemClk/2
> MemClk = 99.53 MHz
> Run Mode = MemClk
> Turbo Mode = 2 * Run Mode
> Mode: RUN
>
>
> Beginning SDRAM Scrub...
> SDRAM Scrub Complete
>
> Here it stalls, going into source code i can see its stalling in the
> function OEMInitDebugSerial (called from main.c in Eboot src)
> It is stalling in this function after it has called
OEMInitDebugSerialKernel
> (ie setup the FFUART) and just before
> calling to OEMWriteDebugString (*****) so the banner full of ***********
> doesn't come up. I've checked it stalls
> here by inserting code to write to LEDS on the board. So probably UART
> initialisation failed although i know hardware
> is ok because i get the hyperterminal output above. Has anyone seen this
> before. In my build options
> i have Enable Img for Flash and Enable ship build checked.
>
> Regards
> ms
>
>

Dean
Fri Apr 01 16:38:30 CST 2005

You were right the first time - OS configuration has absolutely nothing to
do with the bootloader. You must have done something else in the process
that solved the problem.

--
Dean Ramsier - eMVP
Vibren Technologies
http://www.vibren.com/Products/schema_bsp.htm


"ms" <ms@discussions.microsoft.com> wrote in message
news:e3bT2ZgNFHA.688@TK2MSFTNGP10.phx.gbl...
> I rebuilt with PDA configuration rather than Internet Applicance and i
> managed to get past
> the stall below. I thought any required features just to get the
bootloader
> going would be all
> in the BSP but it appears catalog features affect the build. Anyway now to
> migrating the BSP
> to WinCE 5.0!
> "ms" <ms@discussions.microsoft.com> wrote in message
> news:%23EdWmqcNFHA.1300@TK2MSFTNGP14.phx.gbl...
> > Hi,
> >
> > This is going back a bit but, i am trying to get a DBPXA255 Lubbock
> board
> > running with Win CE.net 4.1 with
> > Lubbock BSP. I have created an OS image and flashed eboot.nb0 from
> release
> > directory to
> > flash at address 0 with jflashmm tool.
> > When i boot i get the following on Hyperterminal :
> >
> > *******Beginning System Initialization******* SDCLK[1] =
> MemClk/2
> > MemClk = 99.53 MHz
> > Run Mode = MemClk
> > Turbo Mode = 2 * Run Mode
> > Mode: RUN
> >
> >
> > Beginning SDRAM Scrub...
> > SDRAM Scrub Complete
> >
> > Here it stalls, going into source code i can see its stalling in the
> > function OEMInitDebugSerial (called from main.c in Eboot src)
> > It is stalling in this function after it has called
> OEMInitDebugSerialKernel
> > (ie setup the FFUART) and just before
> > calling to OEMWriteDebugString (*****) so the banner full of ***********
> > doesn't come up. I've checked it stalls
> > here by inserting code to write to LEDS on the board. So probably UART
> > initialisation failed although i know hardware
> > is ok because i get the hyperterminal output above. Has anyone seen
this
> > before. In my build options
> > i have Enable Img for Flash and Enable ship build checked.
> >
> > Regards
> > ms
> >
> >
>
>