Hi All,
In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.
Thank
John
not sure what you mean here.
kernel traps are at 0xf2 for all the kernel calls.
0xfb is the monitor code. look at sysdbg.tgz in /usr/free for examples …
this may be what you are looking for.
0xf3 is the reset vector. none others are documented as being available.
but you can use nmi.
i think you may be thinking of the 0xfb … sysdbg.tgz
John Parsons <parsonsj@esi.com> wrote:
Hi All,
In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.Thank
John
–
Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
Randy
Not sure what is going on, but if you take a look at the information given on
the following page (
http://support.qnx.com/support/docs/qnx4/utils/p/proc.html ) you will find
reference to the 0xf5 interrupt vector for the Proc32 command. The following
statement is made just under the first table of options.
" Interrupt vector 0xf5 is always invoked before trying any of these methods.
For custom hardware, you can point
this vector at code to cause the restart. "
So if the above is true, would I still look at the ‘sysdbg.tgz’ file you
suggest. If the above is not true, is there another vector that should be
used or does the Proc32 even do this?
John
Randy Martin wrote:
not sure what you mean here.
kernel traps are at 0xf2 for all the kernel calls.
0xfb is the monitor code. look at sysdbg.tgz in /usr/free for examples …
this may be what you are looking for.0xf3 is the reset vector. none others are documented as being available.
but you can use nmi.i think you may be thinking of the 0xfb … sysdbg.tgz
John Parsons <> parsonsj@esi.com> > wrote:
Hi All,In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.Thank
John–
Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
On 3 May 2001 22:21:06 GMT, Randy Martin <randy@qnx.com> wrote:
Randy look at the online help of Proc32. it does mention
0xf5 has being a vector invoke during the shutdown procedure,
before Proc32 does its thing.
not sure what you mean here.
kernel traps are at 0xf2 for all the kernel calls.
0xfb is the monitor code. look at sysdbg.tgz in /usr/free for examples …
this may be what you are looking for.0xf3 is the reset vector. none others are documented as being available.
but you can use nmi.i think you may be thinking of the 0xfb … sysdbg.tgz
John Parsons <> parsonsj@esi.com> > wrote:
Hi All,In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.Thank
John
\Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
sorry. i’m losing my memory in my old age.
yes, you can take this over. the samples in /usr/free specifically the apm
and the nmi code show how to take over this type of software interrupt.
qnx_hint_attach( 0x200|0xf5, …)
you need Proc32 425
Mario Charest <mcharest@nozinformatic.com> wrote:
On 3 May 2001 22:21:06 GMT, Randy Martin <> randy@qnx.com> > wrote:
Randy look at the online help of Proc32. it does mention
0xf5 has being a vector invoke during the shutdown procedure,
before Proc32 does its thing.not sure what you mean here.
kernel traps are at 0xf2 for all the kernel calls.
0xfb is the monitor code. look at sysdbg.tgz in /usr/free for examples …
this may be what you are looking for.0xf3 is the reset vector. none others are documented as being available.
but you can use nmi.i think you may be thinking of the 0xfb … sysdbg.tgz
John Parsons <> parsonsj@esi.com> > wrote:
Hi All,In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.Thank
John
\Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
–
Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
On 4 May 2001 19:03:18 GMT, Randy Martin <randy@qnx.com> wrote:
sorry. i’m losing my memory in my old age.
Don’t use this as an excuse with John, LOL!
yes, you can take this over. the samples in /usr/free specifically the apm
and the nmi code show how to take over this type of software interrupt.qnx_hint_attach( 0x200|0xf5, …)
you need Proc32 425
Mario Charest <> mcharest@nozinformatic.com> > wrote:
On 3 May 2001 22:21:06 GMT, Randy Martin <> randy@qnx.com> > wrote:Randy look at the online help of Proc32. it does mention
0xf5 has being a vector invoke during the shutdown procedure,
before Proc32 does its thing.not sure what you mean here.
kernel traps are at 0xf2 for all the kernel calls.
0xfb is the monitor code. look at sysdbg.tgz in /usr/free for examples …
this may be what you are looking for.0xf3 is the reset vector. none others are documented as being available.
but you can use nmi.i think you may be thinking of the 0xfb … sysdbg.tgz
John Parsons <> parsonsj@esi.com> > wrote:
Hi All,In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.Thank
John
\Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
\Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
GEEEEEEEEEEEEEE, thanks a whole lot Mario. 
)
Mario Charest wrote:
On 4 May 2001 19:03:18 GMT, Randy Martin <> randy@qnx.com> > wrote:
sorry. i’m losing my memory in my old age.
Don’t use this as an excuse with John, LOL!yes, you can take this over. the samples in /usr/free specifically the apm
and the nmi code show how to take over this type of software interrupt.qnx_hint_attach( 0x200|0xf5, …)
you need Proc32 425
Mario Charest <> mcharest@nozinformatic.com> > wrote:
On 3 May 2001 22:21:06 GMT, Randy Martin <> randy@qnx.com> > wrote:Randy look at the online help of Proc32. it does mention
0xf5 has being a vector invoke during the shutdown procedure,
before Proc32 does its thing.not sure what you mean here.
kernel traps are at 0xf2 for all the kernel calls.
0xfb is the monitor code. look at sysdbg.tgz in /usr/free for examples …
this may be what you are looking for.0xf3 is the reset vector. none others are documented as being available.
but you can use nmi.i think you may be thinking of the 0xfb … sysdbg.tgz
John Parsons <> parsonsj@esi.com> > wrote:
Hi All,In the documentation for the Proc32 command there is mention of a
interrupt vector 0xf5 that is issued prior to any of the other option of
the Proc32 command. I have tried to attach to this vector with no
avail. Does anyone have an idea how to uses and attach to this vector
location.Thank
John
\Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
\Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579