MUXDEVLOAD FAILURE WHEN BOOTING A PC486 WITH VXWORKS 5.4

[James Pascoe]

Dear All,

I have recently upgraded our Tornado / VxWorks system from 1.0.1 / 5.3.1
to 2.0 / 5.4 in conjunction with a 486 PC target machine.

I have installed the software and have built a new boot disk, but when
VxWorks boots, I get the following error messages towards the end of the
boot cycle:

muxDevLoad failed for device entry 0!
wdbConfig: error Configuring WDB communication interface

then, underneath the normal banner I get:

0x83ee7c (tRootTask): muxLoad failed!

Anybody got any ideas?

Thanks in advance,

James Pascoe

[John Efstathiades]

In article <378071AA...@reading.ac.uk>,

James Pascoe <shu9...@reading.ac.uk> wrote:
> Dear All,
>
> I have recently upgraded our Tornado / VxWorks system from 1.0.1 /
5.3.1
> to 2.0 / 5.4 in conjunction with a 486 PC target machine.
>
> I have installed the software and have built a new boot disk, but when
> VxWorks boots, I get the following error messages towards the end of
the
> boot cycle:
>
> muxDevLoad failed for device entry 0!
> wdbConfig: error Configuring WDB communication interface
>
> then, underneath the normal banner I get:
>
> 0x83ee7c (tRootTask): muxLoad failed!

James,

Ultimately the error is caused by not having the appropriate END in
your VxWorks image. This is because the project builder in Tornado 2
doesn't allow you to explicitly select ENDs. I found two solutions to
this problem:

1. Don't use the project builder to create VxWorks images. Turn on the
Tornado 1.0.1 menu items (Tools->options->projects) and use those
instead (or just use make on the command line).

2. Include the BSD 4.4 driver for your network device using the project
builder. The config.h file in the BSP will then include the END using
the following code:

#ifdef INCLUDE_END
# undef WDB_COMM_TYPE
# define WDB_COMM_TYPE WDB_COMM_END /* END is prefered choice
*/

# ifdef INCLUDE_FEI
# undef INCLUDE_FEI /* don't use BSD driver */
# define INCLUDE_FEI_END /* Use END driver instead */
# endif

[snip]

#endif

HTH,
John.

--
Real Time Products Ltd e-mail: mailto:j...@rtp.co.uk
Chancery House, Tel: +44 (0)121 234 6600
8 Edward Street, Fax: +44 (0)121 234 6611
Birmingham. B1 2RX. England. Web: http://www.rtp.co.uk

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

[tim allen]

>muxDevLoad failed for device entry 0!

Tornado 2 includes and updated (BSD 4.4) network stack, and your network
driver needs upgrading to use it. Your error suggests that you may be using
the older (BSD 4.3) driver, or you have upgraded it incorrectly.

Outline details are given in the Tornado 2 release notes and more detail can
be found in the VxWorks Network 5.4 Programmers Guide.

--------------------
Tim Allen Ltd
Real Time Embedded Software Consultancy

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

[Cameron Fowler]

#define INCLUDE_BSD in your config.h file and remake - this ought to fix
your problem
James Pascoe wrote in message <378071AA...@reading.ac.uk>...

>Dear All,
>
>I have recently upgraded our Tornado / VxWorks system from 1.0.1 / 5.3.1
>to 2.0 / 5.4 in conjunction with a 486 PC target machine.
>
>I have installed the software and have built a new boot disk, but when
>VxWorks boots, I get the following error messages towards the end of the
>boot cycle:
>

>muxDevLoad failed for device entry 0!

>wdbConfig: error Configuring WDB communication interface
>
>then, underneath the normal banner I get:
>
>0x83ee7c (tRootTask): muxLoad failed!
>