Re: Debug config eboot.nb0 required for debugging?
- From: John M <kalypso2@xxxxxxxxxxxxxxxxxxx>
- Date: 11 May 2007 01:59:47 -0700
Hi Mike,
You're an absolute champ! Thanks a lot for your informative
replies.
Regards,
John
On May 11, 10:22 am, "Mike E." <m...@xxxxxxxxxxxxx> wrote:
John M <kalyp...@xxxxxxxxxxxxxxxxxxx> wrote innews:1178870145.272642.46230@xxxxxxxxxxxxxxxxxxxxxxxxxxx:
Hi Mike, thanks for your reply. I verified that I only have one eboot
binary; eboot.nb0 which is 256kB in size. So that rules that factor
out.
So I take it that all I need to do to add kernel debugging support to
the release build is to go to Platform=>Settings then Build Options
tab and then select the 'Enable Kernel Debugger' check box?
So how about the eboot binaries from the release and debug
builds....are they interchangeable? For instance, can I use the
eboot.nb0 from the debug RelDir as the bootloader for the NK.bin from
the release RelDir?
I ask this question because one of my colleagues said that she thinks
there is some KITL related stuff in the debug bootloader which the
release bootloader might not have. Though, since my debug bootloader
is hanging I am forced to either fix the hanging problem (which I'm
totally stuck on), or just use the release bootloader.
Regards,
John
On May 10, 5:15 pm, "Mike E." <m...@xxxxxxxxxxxxx> wrote:
John M <kalyp...@xxxxxxxxxxxxxxxxxxx> wrote
innews:1178808438.525360.236560@xxxxxxxxxxxxxxxxxxxxxxxxxxx:
Hi group,
I'm just wondering if the eboot.nb0 built as part of a
debug configuration needs to be used when using a debugging NK.bin?
Or, is it ok to leave the eboot.nb0 already in my target device's
flash, which was built as part of a release configuration?
I ask this question because the debug eboot.nb0 does not seem to
work. EBOOT hangs when trying to initialize the LAN controller,
here are a few lines of the debug msgs up to that point:
"INFO: Look for Tuple Loop!
INFO: Attribute value is 0x0
INFO: Look for Tuple Loop!
INFO: Attribute value is 0x0
ERROR: Failed to detect and initialize Ethernet controller "
My target device is a custom board based on MainstoneII. The LAN
Controller is an SMSC LAN9118.
So, I'm left wondering, what is the difference between a
debug/release eboot.nb0 ?
Regards,
John
Hi John,
No you can always use the release build also for a debug version of
your Windows CE kernel. Are you sure you have only one eboot.nbx
file? It might be your bootloader have been split, because of the
size into two files (eboot.nb0 and eboot.nb1) and that's why it
hangs.
Best regards,
Mike E.
--
Digi International Inc.http://www.digi.com
Hi John,
Yes you only need to add Kernel debugger support and enable KITL. This
is normally done when you select a debug build from the Platform
Builder.
The files eboot.nb0 and nk.bin are interchangeable for use.
The KITL configuration is done in the OAL of the Windows CE kernel. The
eboot normally only downloads teh image and prepares the boot arguments
for the OS to know how to start the kernel. It is not necessary to build
the boot loader as a debug version. We only use teh release version of
eboot for debugging and for downloading the release image.
Best regards,
Mike E.
--
Digi International Inc.http://www.digi.com
.
- References:
- Debug config eboot.nb0 required for debugging?
- From: John M
- Re: Debug config eboot.nb0 required for debugging?
- From: Mike E.
- Re: Debug config eboot.nb0 required for debugging?
- From: John M
- Re: Debug config eboot.nb0 required for debugging?
- From: Mike E.
- Debug config eboot.nb0 required for debugging?
- Prev by Date: Re: RequestPowerNotifications
- Next by Date: Re: How to pass a structture to a driver using Deviceiocontrol
- Previous by thread: Re: Debug config eboot.nb0 required for debugging?
- Next by thread: Debug img hanging
- Index(es):
Relevant Pages
|
