Error: Kernel fixup module hd.dll

Hello all,

what does this error mean and what do I have to modify in order to fix it?

Error: Kernel fixup module hd.dll dataptr [8014b000] != m_vreloc [1b0000]

I get this in the makeimg phase and I don't have any clue.

I'm working with PB5.0.

TIA
--
Michael Reim
reim AT helmut-fischer DOT de

Sue
Thu Feb 01 14:23:02 CST 2007

I don't really know what causes this -- I'll try to ask around.

You might be able to get away from it by rebuilding the DLL; try typing
"sysgen hd" in a build window and then run makeimg again.

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________

Michael
Fri Feb 02 01:42:21 CST 2007

Hello Sue,

I tried "sysgen hd", but it doesn't change anything.

What I now found is that I only have this problem if I build the image for
RAM.
If I set IMGFLASH=1 the image is built without any problems.
So maybe I have to look if there is any problem with the address ranges in
config.bib.

Unfortunatly I encountered a second problem now:
PB doesn't get any debug connection to my target after download.
It's been a while since I last used this platform in debug mode, but I never
had a problem with the debug connection.
So I wonder if there is any known issue regarding the QFEs and platform
builder debug connection?
I installed all QFEs including december 2006.

--
Michael Reim
reim AT helmut-fischer DOT de


"Sue Loh [MS]" <sloh@online.microsoft.com> schrieb im Newsbeitrag
news:OqTyE7jRHHA.1212@TK2MSFTNGP03.phx.gbl...
>I don't really know what causes this -- I'll try to ask around.
>
> You might be able to get away from it by rebuilding the DLL; try typing
> "sysgen hd" in a build window and then run makeimg again.
>
> Sue
> sloh@microsoft.com (remove "online" from reply-to address)
> http://blogs.msdn.com/ce_base/
> _____________________________________________________________
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> _____________________________________________________________
>
>

Michael
Fri Feb 02 03:28:49 CST 2007

ok, my first problem is solved.
I had
NK 80065800 00f8a800 RAMIMAGE
in my config.bib.
Setting
NK 80070000 00f80000 RAMIMAGE
solved the problem.

But now I have also the second problem.
PB says: The Kernel Debugger is waiting to connect with target.
It seems that KITL is not getting started at all.


--
Michael Reim
reim AT helmut-fischer DOT de



"Michael Reim" <nospamreim@REMOVENOSPAMANDCAPShelmut-fischer.denospam>
schrieb im Newsbeitrag news:Obf2y2pRHHA.3444@TK2MSFTNGP03.phx.gbl...
> Hello Sue,
>
> I tried "sysgen hd", but it doesn't change anything.
>
> What I now found is that I only have this problem if I build the image for
> RAM.
> If I set IMGFLASH=1 the image is built without any problems.
> So maybe I have to look if there is any problem with the address ranges in
> config.bib.
>
> Unfortunatly I encountered a second problem now:
> PB doesn't get any debug connection to my target after download.
> It's been a while since I last used this platform in debug mode, but I
> never had a problem with the debug connection.
> So I wonder if there is any known issue regarding the QFEs and platform
> builder debug connection?
> I installed all QFEs including december 2006.
>
> --
> Michael Reim
> reim AT helmut-fischer DOT de
>

Remi
Fri Feb 02 04:12:34 CST 2007

Hi,

> PB says: The Kernel Debugger is waiting to connect with target.
> It seems that KITL is not getting started at all.

Do you have some serial debug output available to see what happens on the
target side?

Remi

Michael
Fri Feb 02 08:53:15 CST 2007

The problem is solved.
It was my fault, as usual.

Some time ago I modified config.bib and eboot in order to get more free
memory.
Accidentally I installed an eboot version prior to this modification on the
device.
So the position of bootargs wasn't correct and therefor KITL got never
initialised.
I didn't notice that, because most of the time I'm downloading a release
version into flash.
This standalone version doesn't need the bootargs.

Anyway thank you for help.

--
Michael Reim
reim AT helmut-fischer DOT de


"Remi de Gravelaine" <gravelaine at aton dash sys dot fr> schrieb im
Newsbeitrag news:%23eFlrKrRHHA.388@TK2MSFTNGP04.phx.gbl...
> Hi,
>
>> PB says: The Kernel Debugger is waiting to connect with target.
>> It seems that KITL is not getting started at all.
>
> Do you have some serial debug output available to see what happens on the
> target side?
>
> Remi
>

Remi
Fri Feb 02 09:36:20 CST 2007

BTW, as the KITL TROUBLESHOOTING TIPS topic
(http://blogs.msdn.com/ce_base/archive/2006/10/05/KITL-Troubleshooting-Tips.aspx)
is closed, I would like to add a reason why EBOOT hangs just after having
acknowledged/acquired its IP address and right before sending BOOTME
messages.
I actually spent a few hours on it, on a CEPC whose RTC was not operational,
as this can happen after the battery is changed.
There are several places in EBOOT (and KITL) where system time is read to
implement timeouted loops. If a function like OEMKitlGetSecs does not return
a valid result, the function waiting for the timeout may hang looping
forever.

Hope this will help someone one day.
Remi

Sue
Thu Feb 08 10:18:29 CST 2007

Thanks Remi, I will have Upender add that to the blog post. You can also
reply to the blog using the contact form there if you ever think we should
modify posts where the comments are closed.

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________