Request AudioReQuest N.Series Instrukcja Obsługi Pobierz pdf (Strona 51)

USB Audio Design Guide 51/61

/* MIDI IO / IAP */

on stdc ore [ AUDIO _ IO_CO R E ]:

{

thre ad_sp e ed ();

# i fde f MIDI

usb _midi ( p_m idi_rx , p_midi_tx , clk_midi , c_midi , 0, null , null , null ,

> n ull ) ;

# else

iAP ( c_iap , null , p_i2c_scl , p_i2c _sda ) ;

# e ndi f

}

# e ndi f

4.4 Adding Custom Code

The ﬂexibility of the USB audio solution means that you can modify the reference

applications to change the feature set or add extra functionality. Any part of the

software can be altered with the exception of the XUD library.

The reference designs have been veriﬁed against a variety of host OS types, across

diﬀerent samples rates. However, modiﬁcations to the code may invalidate the

results of this veriﬁcation and you are strongly encouraged to retest the resulting

software.

The general steps are:

Make a copy of the eclipse project or application directory (

app_usb_aud_l1

app_usb_aud_l2

) you wish to base your code on, to a separate directory with a

diﬀerent name.

Make a copy of any modules you wish to alter (most of the time you probably

do not want to do this). Update the Makeﬁle of your new application to use

these new custom modules.

Make appropriate changes to the code, rebuild and reﬂash the device for testing.

Once you have made a copy, you need to:

Provide a

.xn

ﬁle for your board (updating the TARGET variable in the Makeﬁle

appropriately).

2. Update device_defines.h with the speciﬁc deﬁnes you wish to set.

3. Update main.xc.

4. Add any custom code in other ﬁles you need.

The following sections show some example changes with a high level overview of

how to change the code.

REV 6.1

1 2 ... 46 47 48 49 50 51 52 53 54 55 56 ... 61 62

Brak uwag

Request AudioReQuest N.Series Instrukcja Obsługi Strona 51