vector.com|Contact
Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

apple*
Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Search:
Advanced search

How to Execute HW-Specific Requests of a vMem Using the vMemAccM

Last updated: 2019-01-30
Question:
How do I execute HW-Specific requests of a vMem using the vMemAccM
Answer:
It is not allowed the call the vMem API directly, therefore the HW-specific vMem requests have to be set up through the vMemAccM to be prioritized against and synchronized with other vMem requests. To set up such a request, vMemAccM provides the public API vMemAccM_HwSpecificReq with following parameters:
  • AddressAreaId referencing the wanted vMem
  • HwId provided by the enum vMemAccM_HwIdType within vMemAccM_vMemCfg.h. The parameter references the vMem instance.
  • vMemHwSpecificFuncIndex pointing to the wanted hardware-specific request in vMem’s function pointer table. Each vMem provides the available indexes within the vMem_HWSpecificFuncId enumeration within the file vMem_Extended_Func.h.
  • DataPtr storing the input and output parameters needed by the desired vMem request. vMemAccM does not use the data, it will be forwarded to vMem.
  • Length of the DataPtr.
Note:
vMemAccM does not split the hardware-specific requests into several steps, it will be forwarded to the vMem as one request.
Example:

The vMem_30_Tc3xxInf01 provides the hardware-specific function, vMem_30_Tc3xxInf01_GetActiveAddressRegion, which gets the currently active address region. To receive this information the API vMemAccM_HwSpecificReq has to be called with the parameters:

  • AddressAreaId referencing vMem_30_Tc3xxInf01
  • HwId corresponding to instance of vMem_30_Tc3xxInf01
  • vMemHwSpecificFuncIndex is given by the symbol VMEM_30_TC3XXINF01_ACTIVE_ADDRESS_REGION
  • DataPtr must point to a variable of type vMem_30_Tc3xxInf01_AddressRegionType. When the job is completed, it contains the information which address region is currently active.
  • Length is not used in this case and could be e.g. 1.
 
Article Options
2019-01-30
Views: 98