Hi,
SV#8 is the check
Anyway, good news you found it.
Giovanni
chSysHalt("SV#8") at Vector78
Moderators: RoccoMarco, barthess
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Re: chSysHalt("SV#8") at Vector78
Not exactly...
Two calls of CH_IRQ_PROLOGUE() / CH_IRQ_EPILOGUE() inside EXT IRQ handler,
but SW#8 will be called in different IRQ handler, so there is no call trace or hit that can be used to find the problem.
Two calls of CH_IRQ_PROLOGUE() / CH_IRQ_EPILOGUE() inside EXT IRQ handler,
but SW#8 will be called in different IRQ handler, so there is no call trace or hit that can be used to find the problem.
Vitaly
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Re: chSysHalt("SV#8") at Vector78
The callback is called by the IRQ handler, the callback then calls CH_IRQ_PROLOGUE(), I think it is two in a row even if do not happen in the same function.
Unless I understood it wrong.
Giovanni
Unless I understood it wrong.
Giovanni
Re: chSysHalt("SV#8") at Vector78
Yes,
first CH_IRQ_PROLOGUE in EXT IRQ handler, the second CH_IRQ_PROLOGUE in EXT callback and chSysHalt(SV#8) will be call from different IRQ handler,
in my case it were: ST and SPI, so there was no hint to look at CycloneTCP OS port which was call CH_IRQ_PROLOGUE from EXT callback.
first CH_IRQ_PROLOGUE in EXT IRQ handler, the second CH_IRQ_PROLOGUE in EXT callback and chSysHalt(SV#8) will be call from different IRQ handler,
in my case it were: ST and SPI, so there was no hint to look at CycloneTCP OS port which was call CH_IRQ_PROLOGUE from EXT callback.
Vitaly
Who is online
Users browsing this forum: No registered users and 41 guests