network problem when boot from flash,

when downloading image with KITL from workstation with PB,the network work
well.
when the same image boots up from flash in target board, the network doesnt
work.Why and how to enable NIC when booting from flash?
I havent nic driver and only have ethdbg driver.

thanks!

Yannick
Mon Dec 13 00:39:06 CST 2004

When not using a NIC driver, if you want to be able to access network at
applicative level, you need a KITL connection (i.e connection between PB &
target).

To have it, you need the following
- Enable KITL in the image (image settings)
- Have bootloader transmitting network settings to OAL (this is normally
done when bootloader succesfully initiated connection with PB to perform
download. In your case, you'll probably need to set the settings directly in
code)
- Enable connection waiting from PB (jump to image menu option)


--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADESET
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"visi" <zqvisi@hotmail.com> wrote in message
news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> when downloading image with KITL from workstation with PB,the network work
> well.
> when the same image boots up from flash in target board, the network
doesnt
> work.Why and how to enable NIC when booting from flash?
> I havent nic driver and only have ethdbg driver.
>
> thanks!
>
>

visi
Mon Dec 13 01:28:06 CST 2004

Thank your reply in time!
I see the codes in private directory and find :after OAL initializes network
hardwork, it will try to connect PB in desktop through sending raw
dataframe.
But my image dont want to connet PB when booting from flash ,other than
downloading by PB.
Where do I need to modify ?

thanks again!
"Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in message
news:e9rty5N4EHA.3336@TK2MSFTNGP11.phx.gbl...
> When not using a NIC driver, if you want to be able to access network at
> applicative level, you need a KITL connection (i.e connection between PB &
> target).
>
> To have it, you need the following
> - Enable KITL in the image (image settings)
> - Have bootloader transmitting network settings to OAL (this is normally
> done when bootloader succesfully initiated connection with PB to perform
> download. In your case, you'll probably need to set the settings directly
in
> code)
> - Enable connection waiting from PB (jump to image menu option)
>
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> ADESET
> Windows Embedded Manager
> ychammings AT adeset DOT com>
> http://www.adeset.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
>
> "visi" <zqvisi@hotmail.com> wrote in message
> news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > when downloading image with KITL from workstation with PB,the network
work
> > well.
> > when the same image boots up from flash in target board, the network
> doesnt
> > work.Why and how to enable NIC when booting from flash?
> > I havent nic driver and only have ethdbg driver.
> >
> > thanks!
> >
> >
>
>

Werner
Mon Dec 13 10:11:06 CST 2004

Rebuild your image with KITL disabled in FeatureView | Settings | Build
Options.
Make sure your NIC is NE2000 or Realtek8139 or any other supported card (No
3COM PCI cards!!!, they are not supported for product ethernet although you
can use that card for debugging with KITL). Download or copy this image
NK.bin to your flash. Start image. This time KITL will not "steal" your
network card and you can use it for product ethernet.

You will find more info if you search past messages in this newsgroup.
Good luck
Werner

"visi" wrote:

> when downloading image with KITL from workstation with PB,the network work
> well.
> when the same image boots up from flash in target board, the network doesnt
> work.Why and how to enable NIC when booting from flash?
> I havent nic driver and only have ethdbg driver.
>
> thanks!
>
>
>

Yannick
Tue Dec 14 01:23:27 CST 2004

You should look at eboot code, probably in OEMLaunch function : this is
where bootloader is initializing settings for Kitl connection when ethernet
is available

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADESET
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"visi" <zqvisi@hotmail.com> wrote in message
news:eSjRTUO4EHA.3336@TK2MSFTNGP11.phx.gbl...
> Thank your reply in time!
> I see the codes in private directory and find :after OAL initializes
network
> hardwork, it will try to connect PB in desktop through sending raw
> dataframe.
> But my image dont want to connet PB when booting from flash ,other than
> downloading by PB.
> Where do I need to modify ?
>
> thanks again!
> "Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in
message
> news:e9rty5N4EHA.3336@TK2MSFTNGP11.phx.gbl...
> > When not using a NIC driver, if you want to be able to access network at
> > applicative level, you need a KITL connection (i.e connection between PB
&
> > target).
> >
> > To have it, you need the following
> > - Enable KITL in the image (image settings)
> > - Have bootloader transmitting network settings to OAL (this is normally
> > done when bootloader succesfully initiated connection with PB to perform
> > download. In your case, you'll probably need to set the settings
directly
> in
> > code)
> > - Enable connection waiting from PB (jump to image menu option)
> >
> >
> > --
> > ----------------------------------------------------------------
> > Yannick Chamming's (eMVP)
> > ADESET
> > Windows Embedded Manager
> > ychammings AT adeset DOT com>
> > http://www.adeset.com
> > Tél : +33 (0)4.72.18.57.77
> > Fax : +33 (0)4.72.18.57.78
> > ----------------------------------------------------------------
> >
> > "visi" <zqvisi@hotmail.com> wrote in message
> > news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > > when downloading image with KITL from workstation with PB,the network
> work
> > > well.
> > > when the same image boots up from flash in target board, the network
> > doesnt
> > > work.Why and how to enable NIC when booting from flash?
> > > I havent nic driver and only have ethdbg driver.
> > >
> > > thanks!
> > >
> > >
> >
> >
>
>

Bruce
Tue Dec 14 12:53:02 CST 2004

Trusting you, that the image is the same, then you are saying that Ethernet
KITL is not working when the image is in flash, but works well when you
download it.

So what is different between the two? One obvious difference is that your
loader is initializing the Ethernet controller when you download, but is not
when you run from FLASH.

What you didn't tell us is what you mean by "doesn't work"?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups

"visi" <zqvisi@hotmail.com> wrote in message
news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> when downloading image with KITL from workstation with PB,the network work
> well.
> when the same image boots up from flash in target board, the network
doesnt
> work.Why and how to enable NIC when booting from flash?
> I havent nic driver and only have ethdbg driver.
>
> thanks!
>
>

visi
Wed Dec 15 04:00:18 CST 2004

yes,Mr.Bruce,you are right,and what I mean is just what you say!

how can bootloader initialize Ethernet controller when running image from
FLASH?

thanks again!

"Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote in
message news:ORofk4g4EHA.3644@tk2msftngp13.phx.gbl...
> Trusting you, that the image is the same, then you are saying that
Ethernet
> KITL is not working when the image is in flash, but works well when you
> download it.
>
> So what is different between the two? One obvious difference is that your
> loader is initializing the Ethernet controller when you download, but is
not
> when you run from FLASH.
>
> What you didn't tell us is what you mean by "doesn't work"?
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
> Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> Embedded newsgroups? Let us know!
> https://www.windowsembeddedeval.com/community/newsgroups
>
> "visi" <zqvisi@hotmail.com> wrote in message
> news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > when downloading image with KITL from workstation with PB,the network
work
> > well.
> > when the same image boots up from flash in target board, the network
> doesnt
> > work.Why and how to enable NIC when booting from flash?
> > I havent nic driver and only have ethdbg driver.
> >
> > thanks!
> >
> >
>
>

Bruce
Wed Dec 15 07:32:05 CST 2004

The kernel, your OAL, should initialize it also.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups

"visi" <zqvisi@hotmail.com> wrote in message
news:u7lKnyo4EHA.1392@tk2msftngp13.phx.gbl...
> yes,Mr.Bruce,you are right,and what I mean is just what you say!
>
> how can bootloader initialize Ethernet controller when running image from
> FLASH?
>
> thanks again!
>
> "Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote
in
> message news:ORofk4g4EHA.3644@tk2msftngp13.phx.gbl...
> > Trusting you, that the image is the same, then you are saying that
> Ethernet
> > KITL is not working when the image is in flash, but works well when you
> > download it.
> >
> > So what is different between the two? One obvious difference is that
your
> > loader is initializing the Ethernet controller when you download, but is
> not
> > when you run from FLASH.
> >
> > What you didn't tell us is what you mean by "doesn't work"?
> >
> > --
> > Bruce Eitman (eMVP)
> > Senior Engineer
> > beitman AT applieddata DOT net
> >
> > Applied Data Systems
> > www.applieddata.net
> > An ISO 9001:2000 Registered Company
> > Microsoft WEP Gold-level Member
> >
> > Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> > Embedded newsgroups? Let us know!
> > https://www.windowsembeddedeval.com/community/newsgroups
> >
> > "visi" <zqvisi@hotmail.com> wrote in message
> > news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > > when downloading image with KITL from workstation with PB,the network
> work
> > > well.
> > > when the same image boots up from flash in target board, the network
> > doesnt
> > > work.Why and how to enable NIC when booting from flash?
> > > I havent nic driver and only have ethdbg driver.
> > >
> > > thanks!
> > >
> > >
> >
> >
>
>

Solarflares
Wed Jan 05 04:53:57 CST 2005

Hello,

Could you please send the code snippet of the files - functions if present:
a. EBOOT\eth.c - OEMEthInititalize
b. EBOOT\main.c - OEMPlatformInit, OEMPreDownload, OEMLaunch

I think the main changes are to done is in OEMEthInititalize function:
//--------------------------------------------------------------------------
--
BOOL jumpToImage = FALSE;
....
if (BOOTFROMFLASH == TRUE) {
jumpToImage = TRUE;
}
....
/* Initialize TFTP transport*/
/* Note that first parameter must be pointer to global variable...*/
if (!EbootInitEtherTransport(
&g_edbgAddr, &subnetMask, &jumpToImage, pLeaseTime,
EBOOT_VERSION_MAJOR, EBOOT_VERSION_MINOR, PLATFORM_STRING,
pBootArgs->systemId, EDBG_CPU_R5500, 0
)) {
Log("EbootInitEtherTransport call failed\n");
goto cleanUp;
}
//--------------------------------------------------------------------------
--
Above is the code snippet that we are using.

I assume the code snippet in your OEMPreDownload would be something like
this:
//--------------------------------------------------------------------------
---
/* Image download depend on protocol */
switch (BOOTDEVICE) {
case FLASH:
/* ADD THE FOLLOWING AFTER MODIFYING "eth.c"
OEMEthInititalize(bootargs);
rc = DownloadImageFromFlash();
break;
case ETH:
rc = OEMEthInititalize(bootargs);
break;
}
//--------------------------------------------------------------------------
---

Hope this helps.

- Solarflares

"visi" <zqvisi@hotmail.com> wrote in message
news:u7lKnyo4EHA.1392@tk2msftngp13.phx.gbl...
> yes,Mr.Bruce,you are right,and what I mean is just what you say!
>
> how can bootloader initialize Ethernet controller when running image from
> FLASH?
>
> thanks again!
>
> "Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote
in
> message news:ORofk4g4EHA.3644@tk2msftngp13.phx.gbl...
> > Trusting you, that the image is the same, then you are saying that
> Ethernet
> > KITL is not working when the image is in flash, but works well when you
> > download it.
> >
> > So what is different between the two? One obvious difference is that
your
> > loader is initializing the Ethernet controller when you download, but is
> not
> > when you run from FLASH.
> >
> > What you didn't tell us is what you mean by "doesn't work"?
> >
> > --
> > Bruce Eitman (eMVP)
> > Senior Engineer
> > beitman AT applieddata DOT net
> >
> > Applied Data Systems
> > www.applieddata.net
> > An ISO 9001:2000 Registered Company
> > Microsoft WEP Gold-level Member
> >
> > Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> > Embedded newsgroups? Let us know!
> > https://www.windowsembeddedeval.com/community/newsgroups
> >
> > "visi" <zqvisi@hotmail.com> wrote in message
> > news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > > when downloading image with KITL from workstation with PB,the network
> work
> > > well.
> > > when the same image boots up from flash in target board, the network
> > doesnt
> > > work.Why and how to enable NIC when booting from flash?
> > > I havent nic driver and only have ethdbg driver.
> > >
> > > thanks!
> > >
> > >
> >
> >
>
>

Han
Thu Mar 10 04:21:02 CST 2005

Hello Solarflares,

I have the same problem as visi. If you have email address I can send
email to you since the EBOOT\eth.c - OEMEthInititalize EBOOT\main.c -
OEMPlatformInit, OEMPreDownload, OEMLaunch is too long to be posted here.

Regards,

HAN


"Solarflares" wrote:

> Hello,
>
> Could you please send the code snippet of the files - functions if present:
> a. EBOOT\eth.c - OEMEthInititalize
> b. EBOOT\main.c - OEMPlatformInit, OEMPreDownload, OEMLaunch
>
> I think the main changes are to done is in OEMEthInititalize function:
> //--------------------------------------------------------------------------
> --
> BOOL jumpToImage = FALSE;
> .....
> if (BOOTFROMFLASH == TRUE) {
> jumpToImage = TRUE;
> }
> .....
> /* Initialize TFTP transport*/
> /* Note that first parameter must be pointer to global variable...*/
> if (!EbootInitEtherTransport(
> &g_edbgAddr, &subnetMask, &jumpToImage, pLeaseTime,
> EBOOT_VERSION_MAJOR, EBOOT_VERSION_MINOR, PLATFORM_STRING,
> pBootArgs->systemId, EDBG_CPU_R5500, 0
> )) {
> Log("EbootInitEtherTransport call failed\n");
> goto cleanUp;
> }
> //--------------------------------------------------------------------------
> --
> Above is the code snippet that we are using.
>
> I assume the code snippet in your OEMPreDownload would be something like
> this:
> //--------------------------------------------------------------------------
> ---
> /* Image download depend on protocol */
> switch (BOOTDEVICE) {
> case FLASH:
> /* ADD THE FOLLOWING AFTER MODIFYING "eth.c"
> OEMEthInititalize(bootargs);
> rc = DownloadImageFromFlash();
> break;
> case ETH:
> rc = OEMEthInititalize(bootargs);
> break;
> }
> //--------------------------------------------------------------------------
> ---
>
> Hope this helps.
>
> - Solarflares
>
> "visi" <zqvisi@hotmail.com> wrote in message
> news:u7lKnyo4EHA.1392@tk2msftngp13.phx.gbl...
> > yes,Mr.Bruce,you are right,and what I mean is just what you say!
> >
> > how can bootloader initialize Ethernet controller when running image from
> > FLASH?
> >
> > thanks again!
> >
> > "Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote
> in
> > message news:ORofk4g4EHA.3644@tk2msftngp13.phx.gbl...
> > > Trusting you, that the image is the same, then you are saying that
> > Ethernet
> > > KITL is not working when the image is in flash, but works well when you
> > > download it.
> > >
> > > So what is different between the two? One obvious difference is that
> your
> > > loader is initializing the Ethernet controller when you download, but is
> > not
> > > when you run from FLASH.
> > >
> > > What you didn't tell us is what you mean by "doesn't work"?
> > >
> > > --
> > > Bruce Eitman (eMVP)
> > > Senior Engineer
> > > beitman AT applieddata DOT net
> > >
> > > Applied Data Systems
> > > www.applieddata.net
> > > An ISO 9001:2000 Registered Company
> > > Microsoft WEP Gold-level Member
> > >
> > > Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> > > Embedded newsgroups? Let us know!
> > > https://www.windowsembeddedeval.com/community/newsgroups
> > >
> > > "visi" <zqvisi@hotmail.com> wrote in message
> > > news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > > > when downloading image with KITL from workstation with PB,the network
> > work
> > > > well.
> > > > when the same image boots up from flash in target board, the network
> > > doesnt
> > > > work.Why and how to enable NIC when booting from flash?
> > > > I havent nic driver and only have ethdbg driver.
> > > >
> > > > thanks!
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>

Han
Thu Mar 10 08:17:03 CST 2005

Dear Sir,

I did exactly what you advice.

1. Enabled the kitl.
2. I adjust the network settings.
3. I can use ping ,ftpd etc now.


The problem isthe device needs PB connection. If I do not connect with PB,
the device seems like waiting for PB connection.Is there any solution to this?

Best regards,

HAN

"Yannick Chamming's [eMVP]" wrote:

> When not using a NIC driver, if you want to be able to access network at
> applicative level, you need a KITL connection (i.e connection between PB &
> target).
>
> To have it, you need the following
> - Enable KITL in the image (image settings)
> - Have bootloader transmitting network settings to OAL (this is normally
> done when bootloader succesfully initiated connection with PB to perform
> download. In your case, you'll probably need to set the settings directly in
> code)
> - Enable connection waiting from PB (jump to image menu option)
>
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> ADESET
> Windows Embedded Manager
> ychammings AT adeset DOT com>
> http://www.adeset.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
>
> "visi" <zqvisi@hotmail.com> wrote in message
> news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> > when downloading image with KITL from workstation with PB,the network work
> > well.
> > when the same image boots up from flash in target board, the network
> doesnt
> > work.Why and how to enable NIC when booting from flash?
> > I havent nic driver and only have ethdbg driver.
> >
> > thanks!
> >
> >
>
>
>

Bruce
Thu Mar 10 09:29:14 CST 2005

With KITL enabled, yes you need a connection to PB. The kernel will wait
for that.

You need a NIC driver to do it without KITL. What NIC are you using?

Bruce

"Han" <Han@discussions.microsoft.com> wrote in message
news:6C671561-2217-49E3-A27A-67886115C471@microsoft.com...
> Dear Sir,
>
> I did exactly what you advice.
>
> 1. Enabled the kitl.
> 2. I adjust the network settings.
> 3. I can use ping ,ftpd etc now.
>
>
> The problem isthe device needs PB connection. If I do not connect with PB,
> the device seems like waiting for PB connection.Is there any solution to
> this?
>
> Best regards,
>
> HAN
>
> "Yannick Chamming's [eMVP]" wrote:
>
>> When not using a NIC driver, if you want to be able to access network at
>> applicative level, you need a KITL connection (i.e connection between PB
>> &
>> target).
>>
>> To have it, you need the following
>> - Enable KITL in the image (image settings)
>> - Have bootloader transmitting network settings to OAL (this is normally
>> done when bootloader succesfully initiated connection with PB to perform
>> download. In your case, you'll probably need to set the settings directly
>> in
>> code)
>> - Enable connection waiting from PB (jump to image menu option)
>>
>>
>> --
>> ----------------------------------------------------------------
>> Yannick Chamming's (eMVP)
>> ADESET
>> Windows Embedded Manager
>> ychammings AT adeset DOT com>
>> http://www.adeset.com
>> Tél : +33 (0)4.72.18.57.77
>> Fax : +33 (0)4.72.18.57.78
>> ----------------------------------------------------------------
>>
>> "visi" <zqvisi@hotmail.com> wrote in message
>> news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
>> > when downloading image with KITL from workstation with PB,the network
>> > work
>> > well.
>> > when the same image boots up from flash in target board, the network
>> doesnt
>> > work.Why and how to enable NIC when booting from flash?
>> > I havent nic driver and only have ethdbg driver.
>> >
>> > thanks!
>> >
>> >
>>
>>
>>

Han
Thu Mar 10 09:55:05 CST 2005

Dear Sir,

My application is PXA255 with ASIX 88796 ethernet chip. This chip is NE2000
compatible. I do not have device driver, I could not get it from neither the
board manufacturer nor the chip manufacturer. I tried to use Windows CE
NE2000 compatible device driver but no success. Really do not know where to
start. I try to follow the documentation from the microsoft web site but I
show very slow progress than I expect.

Best regards,

HAN

"Bruce Eitman (eMVP)" wrote:

> With KITL enabled, yes you need a connection to PB. The kernel will wait
> for that.
>
> You need a NIC driver to do it without KITL. What NIC are you using?
>
> Bruce
>
> "Han" <Han@discussions.microsoft.com> wrote in message
> news:6C671561-2217-49E3-A27A-67886115C471@microsoft.com...
> > Dear Sir,
> >
> > I did exactly what you advice.
> >
> > 1. Enabled the kitl.
> > 2. I adjust the network settings.
> > 3. I can use ping ,ftpd etc now.
> >
> >
> > The problem isthe device needs PB connection. If I do not connect with PB,
> > the device seems like waiting for PB connection.Is there any solution to
> > this?
> >
> > Best regards,
> >
> > HAN
> >
> > "Yannick Chamming's [eMVP]" wrote:
> >
> >> When not using a NIC driver, if you want to be able to access network at
> >> applicative level, you need a KITL connection (i.e connection between PB
> >> &
> >> target).
> >>
> >> To have it, you need the following
> >> - Enable KITL in the image (image settings)
> >> - Have bootloader transmitting network settings to OAL (this is normally
> >> done when bootloader succesfully initiated connection with PB to perform
> >> download. In your case, you'll probably need to set the settings directly
> >> in
> >> code)
> >> - Enable connection waiting from PB (jump to image menu option)
> >>
> >>
> >> --
> >> ----------------------------------------------------------------
> >> Yannick Chamming's (eMVP)
> >> ADESET
> >> Windows Embedded Manager
> >> ychammings AT adeset DOT com>
> >> http://www.adeset.com
> >> Tél : +33 (0)4.72.18.57.77
> >> Fax : +33 (0)4.72.18.57.78
> >> ----------------------------------------------------------------
> >>
> >> "visi" <zqvisi@hotmail.com> wrote in message
> >> news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
> >> > when downloading image with KITL from workstation with PB,the network
> >> > work
> >> > well.
> >> > when the same image boots up from flash in target board, the network
> >> doesnt
> >> > work.Why and how to enable NIC when booting from flash?
> >> > I havent nic driver and only have ethdbg driver.
> >> >
> >> > thanks!
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Bruce
Fri Mar 11 07:23:20 CST 2005

I haven't worked with an NE2000 on board chip, but I would think that you
may need to change some registry settings to get it to work. Probably
similar changes to what you did for eboot/KITL. Things like

[HKEY_LOCAL_MACHINE\Comm\NE20001\Parms]
"BusNumber"=dword:0
"BusType"=dword:8
"InterruptNumber"=dword:03
"IoBaseAddress"=dword:0300
"Transceiver"=dword:3
"CardType"=dword:1

Bruce

"Han" <Han@discussions.microsoft.com> wrote in message
news:57939466-7ECB-48BF-8FB4-308206DF5640@microsoft.com...
> Dear Sir,
>
> My application is PXA255 with ASIX 88796 ethernet chip. This chip is
> NE2000
> compatible. I do not have device driver, I could not get it from neither
> the
> board manufacturer nor the chip manufacturer. I tried to use Windows CE
> NE2000 compatible device driver but no success. Really do not know where
> to
> start. I try to follow the documentation from the microsoft web site but I
> show very slow progress than I expect.
>
> Best regards,
>
> HAN
>
> "Bruce Eitman (eMVP)" wrote:
>
>> With KITL enabled, yes you need a connection to PB. The kernel will wait
>> for that.
>>
>> You need a NIC driver to do it without KITL. What NIC are you using?
>>
>> Bruce
>>
>> "Han" <Han@discussions.microsoft.com> wrote in message
>> news:6C671561-2217-49E3-A27A-67886115C471@microsoft.com...
>> > Dear Sir,
>> >
>> > I did exactly what you advice.
>> >
>> > 1. Enabled the kitl.
>> > 2. I adjust the network settings.
>> > 3. I can use ping ,ftpd etc now.
>> >
>> >
>> > The problem isthe device needs PB connection. If I do not connect with
>> > PB,
>> > the device seems like waiting for PB connection.Is there any solution
>> > to
>> > this?
>> >
>> > Best regards,
>> >
>> > HAN
>> >
>> > "Yannick Chamming's [eMVP]" wrote:
>> >
>> >> When not using a NIC driver, if you want to be able to access network
>> >> at
>> >> applicative level, you need a KITL connection (i.e connection between
>> >> PB
>> >> &
>> >> target).
>> >>
>> >> To have it, you need the following
>> >> - Enable KITL in the image (image settings)
>> >> - Have bootloader transmitting network settings to OAL (this is
>> >> normally
>> >> done when bootloader succesfully initiated connection with PB to
>> >> perform
>> >> download. In your case, you'll probably need to set the settings
>> >> directly
>> >> in
>> >> code)
>> >> - Enable connection waiting from PB (jump to image menu option)
>> >>
>> >>
>> >> --
>> >> ----------------------------------------------------------------
>> >> Yannick Chamming's (eMVP)
>> >> ADESET
>> >> Windows Embedded Manager
>> >> ychammings AT adeset DOT com>
>> >> http://www.adeset.com
>> >> Tél : +33 (0)4.72.18.57.77
>> >> Fax : +33 (0)4.72.18.57.78
>> >> ----------------------------------------------------------------
>> >>
>> >> "visi" <zqvisi@hotmail.com> wrote in message
>> >> news:OYmeqhL4EHA.2540@TK2MSFTNGP09.phx.gbl...
>> >> > when downloading image with KITL from workstation with PB,the
>> >> > network
>> >> > work
>> >> > well.
>> >> > when the same image boots up from flash in target board, the network
>> >> doesnt
>> >> > work.Why and how to enable NIC when booting from flash?
>> >> > I havent nic driver and only have ethdbg driver.
>> >> >
>> >> > thanks!
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

Han
Fri Mar 11 16:09:05 CST 2005

Dear Sir,

Thanks for the information. I tried the NE2000 drivers but there are lots of
parameters and I could not find eqivalents for PXA255.

And each try cost me more than 20 minutes. (Compiling platform, download to
the flash etc) Is there faster method to test device drivers?

I also could not find where the ethernet device initialized when using
NE2000 drivers.

I did not develop the eboot, the development kit supplier developed.




Best regards,

HAN


"Bruce Eitman (eMVP)" wrote:

> I haven't worked with an NE2000 on board chip, but I would think that you
> may need to change some registry settings to get it to work. Probably
> similar changes to what you did for eboot/KITL. Things like
>
> [HKEY_LOCAL_MACHINE\Comm\NE20001\Parms]
> "BusNumber"=dword:0
> "BusType"=dword:8
> "InterruptNumber"=dword:03
> "IoBaseAddress"=dword:0300
> "Transceiver"=dword:3
> "CardType"=dword:1
>
> Bruce
>
>