Who can talk me how to set OampL138 jump adrress in windows ce 6,0??

Zhenhui,

Could you tell us a little more about what you intend to do and why did you made the changes?  All we can tell is you made some changes of the above files.  Without knowing why you made the (potentially incomplete) changes , it's difficult to guess.  

As a preliminary spot check, you made changes in image_cfg.h that has comment:

#define IMAGE_WINCE_DATA_SIZE 0x0193F800 // Match 'RAM' in config.bib

But your config.bib shows 

RAM 82000000 0173F800 RAM

You also need to be careful about other addresses which come after the one you change or the size of the corresponding block you modified.

Regards

WM

hello wm!

   But , this configs are from Ti OamlpL138 Evm borad!

   As you advices!  I change 0173F800 to 0193F800 in config.bib, however it  don't work!

The config.bib follow as these;

MEMORY
    NK                      80000000    02000000    RAMIMAGE
    RAM                     82000000    0193F800    RAM
;    TEST                    8393F000    00000800    RAM
    DISPLAY                 8393F800    00600000    RESERVED
    EMACBUF                 83F3F800    000C0000    RESERVED
    ARGS                    83FFF800    00000800    RESERVED

Regards

Zhenhui Luo

Hi Zhenhui Luo,

As WM memntioned, you have changed several parameters. Where ever parameter you have changed you have to change that parameter in all the configuration files.

For example you have changed IMAGE_SHARE_ARGS_PA address, but you haven't changed that in the ebootnandflash.bib. Similarly you have changed EMACBUF address, but that you haven't changed in the EBOOTNANDFLASH.bib

My suggestion why can't you use the default values first. Then you can change one after the other.

Thank You & Regards,

GSR

Hello GSR!

      Now, I reset its configs to the default configs of evm board bsp. Build and download it eboot.nb0 and nk.bin to my board, Unlucky the wince core don' run successfully! 

      But I notice that It can jum into oal layer  and print 'ADE' by debug serial until 'bl  KernelStart' asm sentence.

Are you meet this issue??  help me!!

Thanks you & Regarts,

ZhenHui Luo

ZhenHui,

In the Catalog for your OSDesign, make sure the SOC Type selected matches your EVM.  Also un-select UART0, UART1 and UART2 if any of them is selected.  Every time after you modify the Catalog, do a clean build: PB > Build > CleanSolution; then PB > Build > RebuildSolution.  See if this helps.

Can you post the bootup log?  This might help others to help you better.

Regards,

WM

Hello VM!

The bootup logs as these;

Completed file(s):
-------------------------------------------------------------------------------
+OEMIsFlashAddr(0x80000000)
-OEMIsFlashAddr(rc = 0)
[0]: Address=0x80000000  Length=0x19FF544  Name="" Target=RAM
+OEMMapMemAddr(0x80000000, 0x80000040)
-OEMMapMemAddr(pAddress = 0xc0000040)
+OEMMapMemAddr(0x80000000, 0x80000044)
-OEMMapMemAddr(pAddress = 0xc0000044)
+OEMMapMemAddr(0x80000000, 0x819fd5bc)
-OEMMapMemAddr(pAddress = 0xc19fd5bc)
ROMHDR at Address 80000044h
+OEMLaunch)
Image Start .......: 0x80000000
Image Size ........: 0x019ff544
Image Launch Addr .: 0x80001000
Image ROMHDR ......: 0xc19fd5bc
Boot Device/Type ..: 2 / 1
OEMLaunch(g_bValidBspArgs)
+OEMMapMemAddr(0x80000000, 0x80001000)
-OEMMapMemAddr(pAddress = 0xc0001000)
INFO: Launch Windows Embedded CE by jumping to 0xc0001000...
Input look addr : 0x0
Input lanuch addr : 0xc0001000
INFO: Launch Windows Embedded CE by jumping to 0xc0001000...ABC

The oal print out 'ABC',but can't jump to kernelstart funtion.

Thanks you & Regards!

ZhenHui Luo

 Hi ZhenHui Luo,

What is the size of SDRAM that are you using on your target board?

If you are using 64MB then make sure you set BSP_64MB_DDR value to 1.

Looks the control is given to the Kernel, But it's not returning to OEMInit....I never debugged at that level...If I find any solutions I will post it here

Thank You & Regards,

GSR

Hi GSR,

The SDRAM size of my board is 128MB, I don't set BSP_64MB_DDR value to 1.

Now I don't know which step the kernel is running. OEMInit ??  But there are not output information printed by debug serial!

Thanks you & Regards,

ZhenHui Luo

Hi ZhenHui Luo,

INFO: Launch Windows Embedded CE by jumping to 0xc0001000...ABC

In one of the replies you are printing ABC string after dots. Where you have enabled this code?

Have you added code to print that string in the following source file c:\WINCE600\PLATFORM\OMAPL138_AM18X\SRC\OAL\OALLIB\oalstartup.s?

If so, I guess it would go to KernelStart api, the source code for this function is at the following path C:\WINCE600\private\winceos\COREOS\nk\kernel\arm\mdarm.c

what am I saying is kernelstart might be called but, it never returns to OEMInit function.

Note: Do not modify any code in private folder or public folder.

Also make sure that you are using the default settings. Have you changed addrtab_cfg.inc?

Additionally please read the following article on WinCE http://blogs.msdn.com/b/ce_base/archive/2007/11/26/how-does-windows-embedded-ce-6.0-start_3f00_.aspx

Thank You & Regards,

GSR

Hi GSR!,

Yes, I changed these code , Frmerly it print ADE string.

INFO: Launch Windows Embedded CE by jumping to 0xc0001000 , This string print from OEMLaunch.

Now,Actually I find that it don't run into OEMInit , Because these are not information printed by debug serial from OEMInit.

Thanks you & Regards ,

ZhenHui Luo

ZhenHui,

As GSR also suggested the kernel might try to start but somehow there is something wrong with the kernel.  

From the bootup log, the start addresses etc. seem to be the same as those in the release.  It might worth a try to download the pre-built kernel from the release and see if it shows anything.  I am not sure how different is your EVM from the LogicPD EVM though.  

In addition to the article that GSR suggests, you can also take a look of this msdn article "Nk.exe Boot Process"

Regards,

WM