Re: WinCE boot from RAM with Lauterbach trace32

Hello All

The problem to boot eboot and WinCE6.0 from RAM using Lauterbach Trace32 has
been solved by disabling watchdog timer at primary boot loader (xldr).
The boot ROM of CPU is enabling watchdog timer to perform cpu bootpin scan
and perform the boot operation as per boot pin configuration like boot form
USB,Eth,NAND flash, and SD card. So the disable watchdog will be the first
task need to perform by xldr (primery boot loader) before performing any
other operation.

But as we are loading primary boot loader (xldr) at internal CPU SRAM
thought trace32 we need to manually enable watchdog timer functional and
interface clock to allow access watchdog registers.

Hope this will help in booting eboot and WinCE6.0 from RAM using trace32 or
any other Jtag.

Thanks,
Prabhat Shrivastav



"Prabhat" wrote:

Thanks for your reply.
No my OS resides at 0x80001000 (RAM). Actually my boot sequence is like i
am using CPU rom code which shall be responsible to load xldr(primary boot
loader) to CPU internal sram from NAND and executes. The xldr shall
initialize the peripheral clocks and DDRAM and copy the eboot(secondary
bootloader) to RAM from NAND and executes. And eboot shall be responsible to
load and executs the CE image to RAM from NAND flash. With the above sequence
every thing is working fine without any problem.

But i dont want anything to load from NAND flash or from any non volatile
memory, So using Lauterbach trace32 i have loaded xldr at internal SRAM ,
eboot and WinCE at RAM. as i mention in my previous mail.

Here at eboot the 0x00000000 might be showing since i have removed NAND copy
and other NAND related code from eboot to make it work independent to NAND
flash.
Is we can run WinCE from RAM without eboot or bootloader, if possible please
let me know how to do that.
please suggest.

Thanks,
Prabhat Shrivastav



"Bruce Eitman [eMVP]" wrote:

Is your OS at address 0x00000000? If it is, is it actually set up to be at
that address in config.bib?

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Prabhat" <Prabhat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F7DAAAC6-0EC0-4C43-B3D0-A936FDC3134C@xxxxxxxxxxxxxxxx
Hello All,

I tried to run WinCE OS image from RAM using Lauterbach trace32 with
following steps
1) Initialized the target board RAM using trace32 script
2) Loaded eboot.nbo into RAM (Since CE have eboot which shall load the CE
image from non volatile memory so I have modified the eboot OEM code such
that it
should not try to create partition or tries to copy from non volatile
memory)
and i am successfully able to bring the boot-loader up from RAM.
3) run eboot and got the proper prints on serial console;
print appears at the end of console is "Launch Windows CE image by
jumping
to 0x00000000" .
4) Loaded nk.bin (kitl was disable) and run; but it's stuck and generate
cpu
exception. Not even got any OC debug prints on serial console.

I am unable to find the cause of this. My point here is- i tried to run OS
image without bootloader also, but it was not worked and so tried with
bootloader with the assumption that CE excepting some boot argument at
boot
time.
But as I mention above bootloader code is for Nand flash so i modified the
portion of OEM boot code to not to look for Nand flash for copying OS
image
and creating partition.

Can anyone please suggest or give some direction to solve this problem?
Thanks in advance
Prabhat Shrivastav
India



.

Relevant Pages

  • Re: WinCE boot from RAM with Lauterbach trace32
    ... Reset the CPU and break at 0x0 ... The problem to boot eboot and WinCE6.0 from RAM using Lauterbach Trace32 ...
    (microsoft.public.windowsce.embedded)
  • Re: WinCE boot from RAM with Lauterbach trace32
    ... No my OS resides at 0x80001000 (RAM). ... Actually my boot sequence is like i ... loader) to CPU internal sram from NAND and executes. ... And eboot shall be responsible to ...
    (microsoft.public.windowsce.embedded)
  • Re: Cant run eboot.nb0.
    ... You can write the BMP file into NAND flash after WinCE boots up. ... EBOOT 8c038000 00080000 RAMIMAGE ... RAM 8c026000 00006000 RAM ... 16 MB area used to cache nk.bin while programming boot media. ...
    (microsoft.public.windowsce.platbuilder)
  • Booting eboot and WinCE6.0 from RAM using Lauterbach
    ... I tried to run WinCE OS image from RAM using Lauterbach trace32 with ... Initialized the target board RAM using trace32 script ... bootloader with the assumption that CE excepting some boot argument at boot ...
    (microsoft.public.dotnet.framework)
  • WinCE boot from RAM with Lauterbach trace32
    ... I tried to run WinCE OS image from RAM using Lauterbach trace32 with ... Initialized the target board RAM using trace32 script ... bootloader with the assumption that CE excepting some boot argument at boot ...
    (microsoft.public.windowsce.embedded)
Loading