Launch address of Nk.bin

Hi,

i am trying to jump to the NK.bin downloaded to the ram and i
have assigneed address for the following fn launch(address) with the
physical address of the NK section in the config.bib file.
But while debugging through the JTAG,its jumping but its showing no
instructions in that address.
i really doubt my address is wrong.Pls clarify my doubt,i know
that experts are availble in the group.
i would really appreciate any replies in this regard this i am a
beginner in windows ce.


Following are my queries
1) I really want to have a good insight how the address is fixed
2) what is the functionality of kernelrelocate() (now its commented)
since both my eboot.nb0 and NK.bin is in ram and that i downloaded
through JTAG


Thanking you

Silver
Sun Aug 19 19:40:32 CDT 2007

Look at the output from makeimg to get some information. In this case the
entry point is "Starting ip: 80008000"

That address is virtual, not physical. You need to figure out the physical
address using OALVAtoPA (or some other method that makes sense for your
platform).

The config.bib file uses virtual addresses.

Romimage figures out the entry point and puts it into the length field of
the last record in the bin file.


Geoff
--



RAM AutoSize: RAM Start=80410000 RAM Size=023f7000
Found pTOC at 0000108c
No imports for kitl.dll
No imports for kernel.dll
No imports for coredll.dll
No imports for k.coredll.dll
Processing NK

Writing
D:\WINCE600\OSDesigns\Cray\MassiveCrayComputer\RelDir\Cray_Release\NK.bin
Table of contents 803003c0 000009ac ( 2476)
Writing ROM signature and TOC pointer at 80007040
Profile Header: 8039aeec 00000920 ( 2336)
Kernel data copy section 80014a84 00000040 ( 64)
ROM Header 8030036c 00000054 ( 84)
First DLL Address: 4001c001
Last DLL Address: 401ac049
Physical Start Address: 80007000
Physical End Address: 80404328
Start RAM: 80410000
Start of free RAM: 804c9000
End of RAM: 82807000
Number of Modules: 73
Number of Copy Sections: 4
Copy Section Offset: 80014a84
Kernel Flags: 00000002
FileSys 4K Chunks/Mbyte: 128 <2Mbyte 128 2-4Mbyte 0 4-6Mbyte 0 >6Mbyte
CPU Type: 01c2h
Miscellaneous Flags: 0002h
Extensions Pointer: 80008090
Total ROM size: 003fd328 ( 4182824)
Starting ip: 80008000
<-------------------------- look here
Raw files size: 000418d6
Compressed files size: 000365e1
"Manoj" <mail2me777@gmail.com> wrote in message
news:1187429336.079510.134720@q4g2000prc.googlegroups.com...

Manoj
Tue Aug 21 10:42:35 CDT 2007

On Aug 20, 5:40 am, "Silver" <moc.liamtoh@gnirrevliseht> wrote:
> Look at the output from makeimg to get some information. In this case the
> entry point is "Starting ip: 80008000"
>
> That address is virtual, not physical. You need to figure out the physical
> address using OALVAtoPA (or some other method that makes sense for your
> platform).
>
> The config.bib file uses virtual addresses.
>
> Romimage figures out the entry point and puts it into the length field of
> the last record in the bin file.
>
> Geoff
> --
>
> RAM AutoSize: RAM Start=80410000 RAM Size=023f7000
> Found pTOC at 0000108c
> No imports for kitl.dll
> No imports for kernel.dll
> No imports for coredll.dll
> No imports for k.coredll.dll
> Processing NK
>
> Writing
> D:\WINCE600\OSDesigns\Cray\MassiveCrayComputer\RelDir\Cray_Release\NK.bin
> Table of contents 803003c0 000009ac ( 2476)
> Writing ROM signature and TOC pointer at 80007040
> Profile Header: 8039aeec 00000920 ( 2336)
> Kernel data copy section 80014a84 00000040 ( 64)
> ROM Header 8030036c 00000054 ( 84)
> First DLL Address: 4001c001
> Last DLL Address: 401ac049
> Physical Start Address: 80007000
> Physical End Address: 80404328
> Start RAM: 80410000
> Start of free RAM: 804c9000
> End of RAM: 82807000
> Number of Modules: 73
> Number of Copy Sections: 4
> Copy Section Offset: 80014a84
> Kernel Flags: 00000002
> FileSys 4K Chunks/Mbyte: 128 <2Mbyte 128 2-4Mbyte 0 4-6Mbyte 0 >6Mbyte
> CPU Type: 01c2h
> Miscellaneous Flags: 0002h
> Extensions Pointer: 80008090
> Total ROM size: 003fd328 ( 4182824)
> Starting ip: 80008000
> <-------------------------- look here
> Raw files size: 000418d6
> Compressed files size: 000365e1"Manoj" <mail2me...@gmail.com> wrote in message
>
> news:1187429336.079510.134720@q4g2000prc.googlegroups.com...

First of all,thank you very much for ur response..
Definitely I will try this option...
I heard like from the records of Nk.bin ,the launch address can be
found ,the dwLength field of the last record ..
so we got 0x80001000.. Even this is the same address used in
Mainstone2 BSP.
I think the starting function in the image is OAL_startup in
startup.s ,right..
There we have given one branch intruction to print some charaters to
debug serial port...
Its jumping to the physical address,but the assembly code is not
the one we expected..

what to do ?