1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<html> 3<head> 4<META http-equiv="Content-Type" content="text/html; charset=windows-1252"> 5<META name="GENERATOR" content="IBM WebSphere Studio Homepage Builder Version 8.0.2.0 for Windows"> 6<META http-equiv="Content-Style-Type" content="text/css"> 7<title>WVR_StartUpAsync</title> 8<LINK rel="stylesheet" href="../../css/nitro.css" type="text/css"> 9</head> 10<body> 11<h1 align="left">WVR_StartUpAsync <img src="../../image/NTR.gif"></h1> 12<h2>Syntax</h2> 13<dl> 14 <dd><PRE><CODE>#include <nitro/wvr.h> 15<A href="WVRResult.html">WVRResult</A> WVR_StartUpAsync( 16 GXVRamARM7 vram , 17 <A href="WVRCallbackFunc.html">WVRCallbackFunc</A> callback , 18 void* arg 19); 20</CODE></PRE></dd> 21</dl> 22<h2>Arguments</h2> 23<table border="1" width="100%"> 24 <tbody> 25 <TR> 26 <TD width="200"><CODE>vram</CODE></TD> 27 <TD width="800">Designates the VRAM bank to allocate to ARM7. The ARM7-side wireless driver will begin to operate on this VRAM. 28 <BR> Below are the possible configuration values. 29 <CODE><UL> 30 <LI>GX_VRAM_ARM7_128_C 31 <LI>GX_VRAM_ARM7_128_D 32 <LI>GX_VRAM_ARM7_256_CD 33 </UL></CODE> 34 </TD> 35 </TR> 36 <TR> 37 <TD width="200"><CODE>callback</CODE></TD> 38 <TD width="800">Designates the callback function to call when the asynchronous process completes. This callback is called from within the interrupt handler.</TD> 39 </TR> 40 <TR> 41 <TD width="200"><CODE>arg</CODE></TD> 42 <TD width="800">Designates optional arguments to be passed to the callback function called when the asynchronous process is complete.</TD> 43 </TR> 44 </tbody> 45</table> 46<h2>Return Values</h2> 47<p>Returns the results of the <A href="WVRResult.html"><CODE>WVRResult</CODE></A> enumerated type process.</p> 48<H2>Description</H2> 49<P> 50Allocates a VRAM bank to the ARM7-side wireless driver, then starts the operations for that driver. If the return value was <code>WVR_RESULT_OPERATING</code>, the callback function is called from inside the PXI receive interrupt handler when the asynchronous process is complete. This function is relevant only when the <CODE>ichneumon</CODE> component, which contains features for operating the wireless driver in VRAM, is being used. For all other components, <code>WVR_RESULT_DISABLE</code> is returned and this function will fail. If the <CODE>ichneumon</CODE> component is being used, the wireless communication features cannot be used as long as the wireless driver is not put into operation via this function. Before the wireless driver starts up, the <A href="../../wm/wm/WM_Init.html"><code>WM_Init</code></A> function will return <code>WM_ERRCODE_DISABLE</code> and will fail. The wireless driver can only be allocated to the VRAM banks VRAM-C and VRAM-D, but if these VRAM banks are already allocated for another application by the GX library, this function will fail. In that case, try to call this function after putting the VRAM bank to be used into a "Not allocated for any application" state with a function such as GX_DisableBankFor*. Conversely, if the VRAM bank is allocated to the wireless driver via this function, the designated VRAM bank will be unable to be allocated for any other application until the wireless driver is stopped by the <A href="WVR_TerminateAsync.html"><code>WVR_TerminateAsync</code></A> function. There are no differences for the wireless driver due to the VRAM that is allocated. The allocation of either VRAM-C or VRAM-D has the same effect on the operations of the wireless driver. Select the VRAM to allocate according to how VRAM-C and VRAM-D will be used.<br><br> <FONT color="#800000">Before calling this function, you must call the <A href="../../os/spinLock/OS_InitLock.html"><code>OS_InitLock</code></A> or <A href="../../os/init/OS_Init.html"><code>OS_Init</code></A> function must be called.</FONT> 51</P> 52<h2>See Also</h2> 53<p><A href="WVR_TerminateAsync.html"><CODE>WVR_TerminateAsync</CODE></A><br> <A href="../../wm/wm/WM_Init.html"><CODE>WM_Init</CODE></A></p> 54<H2>Revision History</H2> 55<P> 562005/06/27 Added statement about callback being called from the interrupt handler.<br> 2005/03/14 Corrected mistake with link destination.<br> 2005/03/08 Standardized the use of the term "interrupt" in Japanese.<br> 2005/03/01 Added to <B>Description</B>.<BR> 2005/02/16 Initial version. 57</P> 58<hr><p>CONFIDENTIAL</p></body> 59</html>