Re: Connecting Vortex86 - 6072

(I'm assuming you are using CE6.0. Let me know if that's not the case).

While there are a lot of advantages to using Ethernet over serial, you
shouldn't be *required* to do it to get a KITL connection working. You can
pass the /c:0 flag to loadcepc to turn off serial debug output. This flag
should be propagated to both the bootloader and the OS unless the BSP has
modified the default behavior.

--
thobrla@xxxxxxxxxxxxxxxxxxxx (remove "online" from reply-to address)
This posting is provided "AS IS" with no warranties, and confers no rights.
<batvanio@xxxxxxxxx> wrote in message
news:e41a9891-cb7a-47de-a238-413ad59f6809@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Paul,
I guess I will have to setup an Ethernet connection to the board...

Ivan

On Jan 16, 2:20 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Yes, generally one serial port will be reserved for kernel debugging or at
least debug messages, even if kernel debugging is not turned on. Kernel
debugger has to be enabled in the settings in order to have PB connect to
the device for that. Alternatively, you might use KITL only to do your
downloads, but, based on this message, "Override Serial Driver: No COM
port
selected for serial KITL transport, no override necessary", your BSP is
not
configured to do that, hence, no download of OS image or anything else.

No, you don't need two serial ports, one for download of images and one
for
debugging. Turning on KITL and setting the port to the same port as where
the debug messages are currently coming out will do it. However, it's
important to realize that, even at pretty darn fast baud rates, it's takes
a
buttload of time to download nk.bin to the device. It's fine for kernel
debugging only, with no download, but, if you want to download images, you
should get Ethernet KITL working (again, settings for the BSP). That's
actually usable for OS image download, although it still can take a long
time at 10BaseT speeds (minutes).

Paul T.

<batva...@xxxxxxxxx> wrote in message

news:6f442d8b-44c7-4329-aaa9-e71e14e07ccb@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Paul,

Yes, the device has a hard disk and that is what I ultimately did for
loading the image. However, I am still trying to connect to the device
for registry editing etc... So here is what happens: when I try to
boot from floppy use the loadcepc, it comes with the messages "failing
to receive header signature", "sending boot request", "waiting for
boot ack"... If i just start win CE and try to connect, it sends
through the COM port all kind of debug information, which makes me
think that this port is reserved for debugging. This is kind of what
it looks like:

" Debug Serial Initt SysInit GDTBase = 810d2000 IDTBase = 8112a3a0
KData = 810d9800
Windows CE Kernel for i486 Buit on Aug. 27 2007 at 10:41:02
INFO:OALLogSetZone...... InitKitlNIC: Searching for PCI Ethernet NIC
(dwIrq = ...)
RTC - Status Reg B...
X86 Init Done, OEM Address Table = .....
Override Serial Driver: serial dirve debug output selected on COM port
1, disabling serial driver for this port.
Override Serial Driver: No COM port selected for serial KITL
transport, no override necessary
VBridge:: VB_INITIALIZED returns [0]... VMInitLL VBridge is not
initialized! Bail out....
HAMOUSE... etc... "

I guess I need to find a way to use the second serial port on this
device?

Ivan

On Jan 16, 12:08 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:



What goes wrong when you use LOADCEPC? Does the device have a hard disk?
You can use LOADCEPC to load the nk.bin from there...

Paul T.

<batva...@xxxxxxxxx> wrote in message

news:4dfafd39-0ce2-40ee-8c21-6d34eebcc3d8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi

I am trying to connect an Vortex86-6072 - an embedded PC104 device
running Windows CE 6.0.
I have successfully built an image with WIndows Embedded 6.0, but I
have lots of problems downloading the image to the device.
The device has no Ethernet capability - only serial and host USB. I am
booting the device from a floppy and I try to use LOADCEPC.EXE TO load
the image or connect to the device using serial connection (using
sboot.bin) but without any success.
I am using different baud rates and monitoring what is coming through
the serial port. Sometimes device would respond with "failing to
receive header signature", "sending boot request", "waiting for boot
ack" . Using some other baud rates returns nothing.
Also, I noticed that loadcepc.exe reports "unknown or old version of
sboot.bin" even though I built it when I built the nk.bin.

My question is can I use serial connection to connect to 6072 at all?
The only other option that loadcepc gives me is eboot (using ethernet)
but 6072 has no ethernet connectivity. Is there any other way? I also
need to connect to the device in order to be able to do remote things
- registry etc.

Do I need an additional equipment to connect using Ethernet?

Thanks

Ivan- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -


.

Quantcast