AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560

I am trying to syncronize execution between HWI and SWI threads:

HWI--\
--> Start Function X
SWI--/

Either HWI thread or SWI thread needs to call Function X after the
latest (HWI or SWI) is finished.

Seems like a simple problem. But the CCS Documentation does not allow
the use of semaphores, mailboxes or swi mailboxes inside HWI threads.

Any suggestions ?

Thanks,
Mark




(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Mark-

> I am trying to syncronize execution between HWI and SWI threads:
>
> HWI--\
> --> Start Function X
> SWI--/
>
> Either HWI thread or SWI thread needs to call Function X after the
> latest (HWI or SWI) is finished.
>
> Seems like a simple problem. But the CCS Documentation does not allow
> the use of semaphores, mailboxes or swi mailboxes inside HWI threads.
>
> Any suggestions ?

If X() is re-entrant, what about a static variable there that serves as semaphore?
If a previous thread is already running inside X(), then either return, or wait until
the function completes and continue. Maybe a counter if you expect a rapid interrupt
rate...

If you this then you have to turn interrupts off temporarily when altering the
semaphore/counter.

-Jeff





(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )

Hi,
I am not aware of the solution, but I have a query regarding the
feasibility of the same.

Can a HWI and SWI be synchronized? Isn't it the case that HWIs always have a
higher priority over SWIs. I am not sure of what the case is in DSP/BIOS,
but I suspect it should be so as in many other RTOS kernels.

Won't such a synchronization bring up issues like priority inversion?

Please do correct me if I am wrong.
--
Jagadeesh
"Quaerendo invenietis".

> -----Original Message-----
> From: c6x@c6x@... [mailto:c6x@c6x@...] On
> Behalf Of Mark
> Sent: Saturday, December 17, 2005 2:09 AM
> To: c6x@c6x@...
> Subject: [c6x] HWI & SWI syncronization
>
> I am trying to syncronize execution between HWI and SWI threads:
>
> HWI--\
> --> Start Function X
> SWI--/
>
> Either HWI thread or SWI thread needs to call Function X
> after the latest (HWI or SWI) is finished.
>
> Seems like a simple problem. But the CCS Documentation does
> not allow the use of semaphores, mailboxes or swi mailboxes
> inside HWI threads.
>
> Any suggestions ?
>
> Thanks,
> Mark
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender or administrator@admi...




(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )