Topic: difference between mailbox and normal command mode  (Read 3138 times)

Jaffry November 11, 2013, 03:34 AM

  • Member
  • *
  • Posts: 126
hello every one,


I cannot actually understand what is the difference between the mailbox and normal command mode.
both of them look similar in their functionality. I think there is some priority difference, i.e. may be mailbox has more priority than normal cmd mode, but I am not sure. Of course they are somewhat difference but what best utilize them?


Can any one explain this with a little example?


Thanks
jaffry

ebarhorst November 11, 2013, 07:05 AM (#1)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 1222
Hi Jaffry


the mailbox feature is mainly intended for Firmware to Host software messages.  a command packet with the command field set to "mailbox" translates in an interrupt generated towards the host. The driver places this packet in the mailbox queue and the software application can read this queue. A typical way to use this is for waking up a software thread in case of an event that has happened in the firmware.


best regards,
Erik

Jaffry November 11, 2013, 09:03 AM (#2)

  • Member
  • *
  • Posts: 126
oh...ok


That is quite fascinating...I was wondering how to catch the pulse from completion of my task. I wish I would have ask this earlier ;D


For example the scanning complete and then software gets the notice, Now I am using the register read, with each pulse, the value is set in a register and I constantly monitor that register using c++ using a loop and when the value is set HIGH I manually set that register value low so that it may be used for next scan cycle. and continue on.


So now it means I can replace that thing with the mailbox function.

arnaudNL April 01, 2014, 07:58 AM (#3)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.