WindML problems...

[Bm34]

Hi All:

I was wondering if anyone knew of any resources on using WindML. I am having
problems with such trivial things as building the examples and integrating
the generic 16 bit driver into a VxWorks image.

If anyone can advise me if this is the correct newsgroup to ask these sorts
of questions or any links to helpful information, tutorials, etc. I would
greatly appreciate it.

Thanks,

Bill

[John]

Hello,

Ask away... we'll see if we can help - there are a number of WindML
users who post to this group. Also, remember to check the archives
(searchable through groups.google.com and other places).

HTH,

John...

"Bm34" <bm34m...@bigfoot.com> wrote in message news:<V8xl7.104843$n75.25...@news4.rdc1.on.home.com>...

[Bm34]

Hi John:

Thank you very much for your prompt reply and suggestions. As you mentioned,
I used google to search for my first problem, which is building WindML
itself with the examples. Sadly, I only found my original post...

Please bear with me as I am a newbie when it comes to both WindML and
VxWorks itself, so these questions may have easy answers. My development
machine is a PC running Windows 2000 Professional with only Tornado 2.0 and
WindML 2.0 (w/ Tornado 2.0.3 patch) installed. At the point I am at now, I
have not created a project I am merely trying to build WindML and the
examples.

Using the WindML Configuration Tool, I have selected the Generic VGA driver,
8-bit colour depth, 320x200 resolution and 60 MHz refresh rate. Under the
miscellaneous tab I selected "Build WindML Examples".

WindML itself appears to build as expected, but I receive the following
error when the examples begin compilation:

...
make.exe *** [ugldemo] Error 0xc0000005

Building is then halted. I cannot seem to find any reference to this error
number so I am not sure what to troubleshoot as far as my configuration
goes.

Any suggestions to resolve this are greatly appreciated. If any additional
information is required please let me know that as well, that is everything
I can think of.

Thanks,

Bill

"John" <john_...@yahoo.com> wrote in message
news:488e459a.01090...@posting.google.com...

[Werner Schiendl]

Hi,

I had the same problem with this build utility.
Build without the examples and the image will be built ok.

To build the examples, like often with WRS tools, it is better to go the
command line way.

Building the examples from the command line is quite well described in the
manuals that come with WindML.
You can go to the '$(WIND_BASE)/target/src/ugl/example' directory and type:

make CPU=<what your CPU type is>

More options are described in the manuals.
Your object files then end up in '$(WIND_BASE)/lib/obj<your CPU
type>gnuApps'

Feel free to ask, if you need more help.
I did not, however, track down why the build failes in the GUI.

hth
Werner

"Bm34" <bm34m...@bigfoot.com> wrote in message

news:rLMl7.111054$n75.26...@news4.rdc1.on.home.com...

[John]

Hello,

Check that you have all the Win2K patches for the IDE installed. I
seem to remember seeing problems with Win2K in the past.

Also, as Bill suggested, let us have more of the build output. I have
never compiled it using the IDE, only the command line and only on
Unix which tends not to exhibit as many of these strange errors...
There doesn't look to be anything odd going on in the Makefile.

To find the demo, go to [install_dir]/target/src/ugl/example/demo
(there are other examples in the 'example' directory too). You should
then be able to build the demo file using the following command:

> make CPU=ARMARCH4 ugldemo.o

Substitute the value of CPU to match your CPU. If you get an error,
execute [install_dir]/host/x86-win32/bin/torVars.bat to set up your
command line environment (you might like to add this to the
autoexec.bat thingy if you end up using the command line a lot).

HTH,

John...

"Bm34" <bm34m...@bigfoot.com> wrote in message news:<rLMl7.111054$n75.26...@news4.rdc1.on.home.com>...

[Bm34]

Fantastic guys, thank you very much for the advice. I also used the
information you have provided to build WindML from the command line.
Building the examples yields a number of .o files in the directory .

I have a general question. I am working with the pentium BSP, which requires
memory to be allocated for a graphics device in the sysPhysMemDesc[] array.
Upon trying to allocate a memory pool the system hangs on booting with no
additional information. The VxWorks image loads over the network fine but
upon the message

<general information for boot settings>

Starting at 0xNNNNNNNN...

No further processing is done and no further information is given.

Any suggestions on what I might be doing wrong? Any additional information
needed? Thanks, you guys have been extremely helpful.