VxSim error when downloading module.

gada...@gmail.com

unread,

Feb 26, 2008, 7:43:48 PM2/26/08

to

Hello All,
I am having problems downloading a VxWorks module (.out file) to the
VxSim simulator (SIMNT) provided by WindRiver Workbench 2.4. Whenever
I attempt to download it, I get an error on my shell that looks like:

Exception !
Vector 13 : Access Violation
Program Counter: 0x100bfc3c
Access Address (write): 0x54e71f04
Status Register: 0x00010216
Task: 0x1516dce8 "tWdbTask"
0x1516dce8 (tWdbTask): WDB exception. restarting agent in 10
seconds...
Exception !
Vector 13 : Access Violation
Program Counter: 0x100bfc3c
Access Address (write): 0x54e71f04
Status Register: 0x00010216
Task: 0x1516dce8 "tWdbTask"

Has anyone seen this kind of error before? I have tried increasing the
stack sizes of the twdbtask, tshell and any spawned tasks but this is
to no avail. I also increased the memory size of the simulator. The
size of the .out file is about 320 kbytes.

I appreciate your help.

Thanks

papi

unread,

Feb 27, 2008, 1:29:28 AM2/27/08

to

Hi,
I had com across this type of error..This error may come due to
logical errors in programs. (lik wrong assignments)
so verify u'r program ....

Regards,
papi

Ignacio G.T.

unread,

Feb 27, 2008, 10:20:24 AM2/27/08

to

gada...@gmail.com escribió:

> Hello All,
> I am having problems downloading a VxWorks module (.out file) to the
> VxSim simulator (SIMNT) provided by WindRiver Workbench 2.4. Whenever
> I attempt to download it, I get an error on my shell that looks like:
>
> Exception !
> Vector 13 : Access Violation
> Program Counter: 0x100bfc3c
> Access Address (write): 0x54e71f04
> Status Register: 0x00010216
> Task: 0x1516dce8 "tWdbTask"
> 0x1516dce8 (tWdbTask): WDB exception. restarting agent in 10
> seconds...

It seems as if you have symbols (code or data) in your .out file with
addresses that overlap memory already used by VxWorks in the simulator.
Check the symbols in the .out file. I do that with nmsimpc or
objdumpsimpc (for instance, objdumpsimpc --section-headers file.out),
but I use Tornado 2.0.2 / VxWorks 5.4.2.

gada...@gmail.com

unread,

Feb 27, 2008, 1:23:48 PM2/27/08

to

On Feb 27, 7:20 am, "Ignacio G.T." <igtorque.rem...@evomer.yahoo.es>
wrote:
> gadal...@gmail.com escribió:

Thanks for all your responses so far. One note I wanted to make is
that this same .out file works perfectly well when placed in an actual
hardware target.
Does that make any difference? If I find my symbols to overlap the
simulator memory, what can I do to fix it?

FYI, I use VxWorks 6.2
Thanks

AliF

unread,

Mar 15, 2016, 6:06:18 PM3/15/16

to

Hi
i have a same problem, in real hardware my code has no error, but simulation take this error(Exception!
Vector 13 : Access Violation) from my code. do you find any solution for that?!!

AliF
--

caina...@gmail.com

unread,

Feb 24, 2020, 12:55:40 PM2/24/20

to

Make sure your simulator is based upon your image project and not the default 'sample' image project.

Gouri Sharma

unread,

Mar 31, 2022, 12:54:02 AM3/31/22

to

Hi

I am facing this issue and i don't know what is next step and i am alos not aware about this error.
can anyone please help me ?

Checking License...OK
Virtual Base Address: 0x10000000
Virtual Top Address: 0x50000000 Virtual Size: 0x40000000 (1024Mb)
Physical Base Address: 0x10000000
Physical Top Address: 0x1bb00000 Physical Size: 0x0bb00000 (187Mb)
Loading...
0x1e5f90 + 0x10ad0 + 0x27210
Loading serial/commSio.dll ... done

Exception !
Vector 13 : Access Violation

Program Counter: 0x101914dc
Access Address (read): 0x00000014
Status Register: 0x00010206
Task: 0x10e5ed40 "ipcom_initd"
0x10e5ed40 (ipcom_initd): task 0x10e5ed40 has had a failure and has been stopped.
0x10e5ed40 (ipcom_initd): The task been terminated because it triggered an exception that raised the signal 11.