Wav File Playback System

7/31/2019 Wav File Playback System

1/68

.wav FILE PLAYBACK SYSTEM

1.1 Digital audio player

A digital audio player, or DAP, is a consumer electronic device that has the primary

function of storing, organizing and playing audio files. Some DAPs are also referred to as

portable media players as they have image-viewing and/or video-playing support.

1.2 History

The immediate predecessor in the market place of the digital audio player was the

portable CD player, or "portable audio device."

Kane Kramer designed one of the earliest digital audio players, which he called the IXI.

His 1979 prototype was capable of approximately 3.5 minutes of audio playback but it did not

enter commercial production. Apple Inc. hired Kramer as a consultant and presented his workas an example of prior art in the field of digital audio players during their litigation with

Burst.com almost two decades later.

The world's first company to announce a portable MP3 player and the attendant system

for uploading MP3 audio content to a personal computer and then downloading it onto a

personal MP3 player was Audio Highway.

One of the chips making it possible to create portable MP3 players before the market

for mass produced devices took off was the Micronas MAS3507D ASIC MP3 Decoder chip.

Several electronics DIY projects used this circuit. As software based approach would have

limited battery time severely. This chip allowed the microcontroller to read data from a flash

memory and feed the decoder chip, creating a low power solution.

In 1998, Compaq developed the first hard drive based DAP using a 2.5" laptop drive. It

was licensed to HanGo Electronics (now known as Remote Solution), which first sold the PJB-

100 (Personal Jukebox) in 1999. The player had an initial capacity of 4.8 GB, with an

advertised capacity of 1200 songs.

In 2000, Creative released the 6GB hard drive based Creative NOMAD Jukebox. The

name borrowed the jukebox metaphor popularized by Remote Solution and also used by

Archos. Later players in the Creative NOMAD range used micro drives rather than laptop

drives.

In October 2001, Apple Computer (now known as Apple Inc.) unveiled the firstgeneration iPod, a 5 GB hard drive based DAP with a 1.8" Toshiba hard drive. In July 2002,

DEPT E&C,SBMJCE 1


2/68


Apple introduced the second generation update to the iPod. It was compatible with Windows

computers through Musicmatch Jukebox. The iPod series, which grew to include flash

memory-based players, has become the market leader in DAPs.

In 2002, Archos released the first "portable media player" (PMP), the Archos Jukebox

Multimedia. Manufacturers have since implemented abilities to view images and play videos

into their devices.

1.3 Operation

Digital sampling is used to convert an audio wave to a sequence of binary numbers that

can be stored in a digital format, such as MP3. Common features of all MP3 players are a

memory storage device, such as flash memory or a miniature hard disk drive, an embedded

processor, and an audio codec microchip to convert the compressed file into an analogue sound

signal.

Most DAPs are powered by rechargeable batteries, some of which are not user-

replaceable. They have a 3.5 mm stereo jack; music can be listened to with earbuds or

headphones, or played via an external amplifier. Some devices also contain internal speakers,

through which music can be listened to, although these built-in speakers are typically of very

low quality.

Nearly all DAPs consists of some kind of display screen, although there are exceptions,

such as the iPod Shuffle, and a set of controls with which the user can browse through the

library of music contained in the device, select a track, and play it back. The display, if the unit

even has one, can be anything from a simple one or two line monochrome LCD display, similar

to what are found on typical calculators, to large full-colour displays capable of displaying

photographs or viewing video content on. The controls can range anywhere from the simple

buttons as are found on most typical CD players, such as for skipping through tracks orstopping/starting playback to full touch-screen controls, such as that found on the iPod Touch

or the Zune HD. One of the more common methods of control is some type of the scroll wheel

with associated buttons. This method of control was first introduced with the Apple iPod and

many other manufacturers have created variants of this control scheme for their respective

devices.

Content is placed on DAPs typically through a process called "syncing", by connecting

the device to a personal computer, typically via USB, and running any special software that is

often provided with the DAP on an enclosed CD-ROM, or downloaded from the manufacturer's

DEPT E&C,SBMJCE 2


3/68


website. Some devices simply appear as an additional disk drive on the host computer, to which

music files are simply copied like any other type of file. Other devices, most notably the Apple

iPod or Microsoft Zune, require the use of special management software, such as iTunes or

Zune Software. The music, or other content such as TV episodes or movies, is added to the

software to create a "library". The library is then "synced" to the DAP via the software. Thesoftware typically provides options for managing situations when the library is too large to fit

on the device being synced to. Such options include allowing manual syncing, in that the user

most manually "drag-n-drop" the desired tracks to the device, or allow for the creation of play

lists. Some of the more advanced units are now starting to allow syncing through a wireless

connection, such as via WiFi or Bluetooth.

1.4 Types

Digital audio players are generally categorized by storage media:

1. Flash-based Players: These are non-mechanical solid state devices that hold digital

audio files on internal flash memory or removable flash media called memory cards. Due to

technological advancements in flash memory, these originally low-storage devices are now

available commercially ranging up to 64 GB. Because they are solid state and do not have

moving parts they require less battery power and may be more resilient to hazards such as

dropping or fragmentation than hard disk-based players. Basic MP3 player functions are

commonly integrated into USB flash drives.

2. Hard drive-based Players or Digital Jukeboxes: Devices that read digital audio files

from a hard disk drive (HDD). These players have higher capacities currently ranging up to 250

GB. At typical encoding rates, this means that tens of thousands of songs can be stored on one

player.

3. MP3 CD Players: Portable CD players that can decode and play MP3 audio filesstored on CDs.

4. Networked audio players: Players that connect via (WiFi) network to receive and

play audio.

DEPT E&C,SBMJCE 3


4/68


2.1 ARM CORES

Following are the different types of ARM CORE PROCESSORS that are used for various

applications.

ARM Cortex Application Processors

Cortex-A Series - High performance processors for open Operating Systems.

ARM Cortex Embedded Processors

Cortex-R Series - Exceptional performance for real-time applications.

Cortex-M Series - Cost-sensitive solutions for deterministic microcontroller

applications.

Classic ARM Processors

ARM11 Series- Performance processors based on the ARMv6 architecture.

ARM9 Series- Popular processors based on the ARMv5 architecture.

ARM7 Series- Classic processors for general purpose applications.

ARM Specialist Processors

SecurCore - Processors for high security applications

FPGA Cores - Processors for FPGA

We chose Cortex-M series because these processors have been developed primarily for

the microcontroller domain where the need for fast, highly deterministic, interrupt management

is coupled with the desire for extremely low gate count and lowest possible power

consumption. The STM32F103VET6 board uses the ARM CORTEX-M3 as the core processor.

[1], [2]

2.2 AUDIO FORMATS

These are the audio formats that are used in various popular media players.

MP3- MPEG Layer-3 format is the most popular format for downloading and storing

music. By eliminating portions of the audio file that are essentially inaudible, mp3 files

DEPT E&C,SBMJCE 4


5/68


are compressed to roughly one-tenth the size of an equivalent PCM file while

maintaining good audio quality.

WAV- Commonly used for storing uncompressed (PCM), CD-quality sound files

MP4- MPEG-4 audio most often AAC but sometimes MP2/MP3, MPEG-4 SLS, CELP,HVXC and other audio object types defined in MPEG-4 Audio

FLAC- A lossless compression codec.

WMA- The popular Windows Media Audio format owned by Microsoft. Designed with

Digital Rights Management (DRM) abilities for copy protection.

We chose WAV format because WAV format has more to do with its familiarity, its

simplicity and simple structure, which is heavily based on the RIFF file format. [7], [8]

2.3 METHODOLOGICAL APPROACH

We made a study of various methods to present our report and we chose this method which

suits best to our idea. [14]

Requirement Analysis

Requirements

o System Requirements

Hardware Requirements

Software Requirements

Design

o High Level Design (HLD)

o Low Level Design (LLD)

Coding

Testing

o Module Testing

o Integration Testing

DEPT E&C,SBMJCE 5


6/68


o System Testing

2.4 PLATFORMS

Many semiconductor companies manufacture ARM CORTEX-M3 based evaluation and

application development platforms. Here are a few examples:

Hardware

TIs STELLARIS

AURDINOs XDUINO

STMs STM32 PRIMER2

We chose STMs PRIMER2 as it was economical, portable and compact compared to other

hardware.

Software

We made a study of various operating systems to understand their goals and their

scheduler algorithms which helps us in making our application portable and generic.

Operating system

-Free RTOS -Windows CE

-VXworks -PHARLAP

-EMBos -Circle OS

IDE (Integrated Development Environment)

-IAR -STELLARIS WARE

-RIDE 7 -XDUINO

We chose Circle OS as our RTOS and RIDE 7 as our IDE, both of these come as

freeware with the PRIMER2 .Also the small footprint of CircleOS allows you to keep up to 104

KB for the applications. The list of the available applications is stored in a table at the top of

the memory used by CircleOS. Each application is run by CircleOS when selected, has the full

DEPT E&C,SBMJCE 6


7/68


availability of the CPU and can use the entire RAM which is not used by CircleOS. It will be

scheduled by the CircleOS with full privileges on the device, until it explicitly quits. [4], [15]

.2.5 OTHER STATISTICS AND GRAPHS

The following comparison, statistics and graphs helps in defending our choices made in all thefields. [4], [9]

ARM Processor family

Fig2.1.ARM Processor family

Features of ARM7TDMI-S vs. CORTEX-M3

Table 2.1.Features of ARM7TDMI-S vs. CORTEX-M3

Performance of ARM7TDMI-S vs. CORTEX-M3

DEPT E&C,SBMJCE 7


8/68


Fig2.2.Relative Performance of ARM7TDMI-S vs. CORTEX-M3

Fig2.3.Relative Code size of ARM7TDMI-S vs. CORTEX-M3

Performance compared to other family of processors

DEPT E&C,SBMJCE 8


9/68


Fig2.4. Performance compared to other family of processors

3.1 REQUIREMENT ANALYSIS

DEPT E&C,SBMJCE 9


10/68


USE CASE is a description of a systems behavior as it responds to a request that

originates from outside of that system. In other words, a use case describes "who" can do

"what" with the system in question. The use case technique is used to capture a system's

behavioral requirements by detailing scenario-driven threads through the functional

requirements.

.WAV FILE

SELECTION VOLUME CONTROL PLAY CONTROL OUTPUT DISPLAY

DISPLAY OF FILES POWEROFF

SPEAKERUP DOWN MUTE PLAY STOP QUIT

Fig3.1. Use-Case analysis of Requirements

3.2 System requirements specification (SRS)

SRS is a structured collection of information that embodies the requirements of a system.

A .wav player with the following specifications:

.wav files are stored on a micro sd card.

The application should select from a list of files on the card and play the

valid .wav files.

Upon selection and while playing the .wav files the screen should display

options to play, stop, quit and power off.

These options on screen should act as input elements i.e. they should be enabled

through touch.

The application should display options to increase or decrease volume.

DEPT E&C,SBMJCE 10
http://en.wikipedia.org/wiki/Functional_requirementhttp://en.wikipedia.org/wiki/Functional_requirementhttp://en.wikipedia.org/wiki/Functional_requirementhttp://en.wikipedia.org/wiki/Functional_requirement


11/68


The application should display the name of the file being played.

1. On switching the device on the following screen shall appear. (Fig 3.2)

2. Upon pressing the centre button of the joystick the device shall display a menu containing all

the applications on the device. (Fig 3.3)

The .wav player application shall appear as wmp on the menu.

3. On selecting the wmp application through touch or joystick, a menu shall appear

displaying sd card and quit. If the sd card is not inserted it shall display a message as sd

card not inserted. (Fig 3.4)

4. Upon selection ofsd card option through or joystick, a screen shall appear displaying the

list of files on the sd card. The screen shall display a list of 5 files at a time. The touch screen or

the centre button of joystick can be used to select a file. If the quit option is selected the

control shall go back to the previous menu. (Fig 3.5)

5. Upon selecting a valid .wav file from the list through or joystick, the screen shall display the

format as shown in figure 1.5.If the selected file is invalid then an error message shall appear as

invalid file. (Fig 3.6)

Fig3.2. Start Up Screen.

DEPT E&C,SBMJCE 11


12/68


Fig3.3. Menu Screen.

Fig3.4. SD Check Screen.

Fig3.5. Explorer Screen.

Fig3.6. Run Screen.

3.2 User Controls

Sub ID Screen element Input/output Action on single touch

Com.1 Mute icon Input Shall mute the volume.

Com.2 Volume increase

icon

Input Shall increase the volume by a certain fixed db

.Upon multiple touches can go to a maximum

DEPT E&C,SBMJCE 12


13/68


predetermined value.

Com.3 Volume decrease

icon

Input Shall decrease the volume by a certain fixed

db .Upon multiple touches can mute the

volume.

Com.4 Configuration

icon

Input Opens the configuration menu.

Com.5 Play icon Input Shall issue a RUN command and it plays the

selected file and the name of the file being

played shall be displayed.

Com.6 Stop icon Input Shall issue a STOP command which stops the

playback of the current running file and goesto idle mode with the same screen status.

Com.7 Quit icon Input Shall issue an EXIT command which brings

the control out of the application and device

goes back to exploring state.

Com.8 Shut Down icon Input Shall stop playing the file and shall display the

initial Start Up Idle screen.

Com.9 Running

text/Still text

Output

Table3.1. User controls.

4.1 BLOCK DIAGRAM

DEPT E&C,SBMJCE 13


14/68


The figure above shows the architecture of the STM32-Primer2,equipped with an

STM32F103VET6, one of the new ST, Cortex-based, 32-bit microcontrollers. The main

characteristics of this system are:

ARM 32-bit Cortex-M3 CPU, 72 MHz, 90 DMips with 1.25 DMips/MHz,

512KB of Flash program memory, 64KB SRAM.

Fig4.1. Block Diagram of the System

Embedded communication peripherals: SPI, I2C, I2S.

A touch-screen LCD color display (24-bits color, 128x160 pixels),

DEPT E&C,SBMJCE 14


15/68


2 USB connectors:

o One marked "Debug" to connect to a PC running Ride for application

development,

o One marked "STM32" that allows the embedded application to communicate

with external host.

One 4-directions joystick with push button,

4 menu buttons,

An on-board microphone and a loudspeaker providing sound recording and playback

capabilities,

A headphone connector,

One accelerometer (MEMS) that captures the 3D-position information related to the

STM32-Primer2, and which is used to navigate through the menus, and to move thePointer.

One extra connector is linked to some unused I/O pins of the STM32 in order to add

Extra peripherals.

4.2 Power supply

The STM32-Primer2 features a 400mAh Li-Ion rechargeable battery, equipped with a

voltage regulator along with a battery charger. When one of the USB connectors is linked to a

PC host, voltage supplied by the PC is used to recharge the battery. When no USB host is

connected, the battery is used to supply the power for the STM32-Primer2. When the battery is

fully charged, the STM32-Primer2 can be used for about 6 hours. The duration of the batteries

depends on the Primer2 activity. For instance, it can be extended -or reduced- by

changing the setting of the backlight intensity (see the menu Settings) and the CPU

frequency.

4.3 3D MEMS accelerometer

The STM32-Primer2 is equipped with a MEMS inertial sensor (LIS3LV02DL from

STMicroelectronics). This device is used by the STM32-Primer2 as a human interface device

to select commands, in coordination with a graphic pointer. When you start the STM32-

Primer2 for the first time, you will see a small ball moving according to the orientation of the

STM32-Primer2 circuit. The information about the 3D position is provided by the MEMS.

4.4 ARM CORE: ARM Architecture M profile

DEPT E&C,SBMJCE 15


16/68


The ARM architecture has evolved through several major revisions to a point where it

supports implementations across a wide spectrum of performance points, with over a billion

parts per annum being produced.

The latest version (ARMv7) has seen the diversity formally recognized in a set of

architecture profiles, the profiles used to tailor the architecture to different marketrequirements. A key factor is that the application level is consistent across all profiles, and the

bulk of the variation is at the system level.

The introduction of Thumb-2 technology provided a balance to the ARM and Thumb

instruction sets, and the opportunity for the ARM architecture to be extended into new markets,

in particular the microcontroller marketplace.

To take maximum advantage of this opportunity a Thumb-only profile with a new

programmers model (a system level consideration) has been introduced as a unique profile,

complementing ARMs strengths in the high performance and real-time embedded markets.

Key criteria for ARMv7-M implementations are as follows:

Enable implementations with industry leading power, performance and area constraints

o Opportunities for simple pipeline designs offering leading edge system

performance levels in a broad range of markets and applications

Highly deterministic operation

o Single/low cycle execution

o Minimal interrupt latency (short pipelines)

o Cache less operation

Excellent C/C++ target aligns with ARMs programming standards in this area

o Exception handlers are standard C/C++ functions, entered using standard calling

conventions

Designed for deeply embedded systems

o Low pin count devices

o Enable new entry level opportunities for the ARM architecture

Debug and software profiling support for event driven systems.

4.5 SYSTEM ARCHITECTURE

In low-, medium- and high-density devices, the main system consists of:

Four masters:

DEPT E&C,SBMJCE 16


17/68


Cortex-M3 core DCode bus (D-bus) and System bus (S-bus)

GP-DMA1 & 2 (general-purpose DMA)

Four slaves:

Internal SRAM

Internal Flash memory FSMC

AHB to APBx (APB1 or APB2), which connect all the APB peripherals

These are interconnected using a multilayer AHB bus architecture as shown in below

architecture.

Fig4.2.System architecture

ICode bus

This bus connects the Instruction bus of the Cortex-M3 core to the Flash memory instruction

interface. Prefetching is performed on this bus.

DEPT E&C,SBMJCE 17


18/68


DCode bus

This bus connects the DCode bus (literal load and debug access) of the Cortex-M3 core to

the Flash memory Data interface.

System busThis bus connects the system bus of the Cortex-M3 core (peripherals bus) to a BusMatrix

which manages the arbitration between the core and the DMA.

DMA bus

This bus connects the AHB master interface of the DMA to the BusMatrix which manages the

access of CPU DCode and DMA to SRAM, Flash memory and peripherals.

BusMatrix

The BusMatrix manages the access arbitration between the core system bus and the

DMA master bus. The arbitration uses a Round Robin algorithm. In connectivity line devices,

the Bus Matrix is composed of five masters -CPU DCode, System bus, Ethernet DMA, DMA1

and DMA2 bus, and three slaves -FLITF, SRAM and AHB2APB bridges. In other devices, the

Bus Matrix is composed of four masters -CPU DCode, System bus, DMA1 bus and DMA2

bus, and four slaves -FLITF, SRAM, FSMC and AHB2APB bridges. AHB peripherals are

connected on system bus through a BusMatrix to allow DMA access.

AHB/APB bridges (APB)

The two AHB/APB bridges provide full synchronous connections between the AHB

and the

2 APB buses. APB1 is limited to 36 MHz, APB2 operates at full speed (up to 72 MHz

depending on the device). After each device reset, all peripheral clocks are disabled (except for

the SRAM and FLITF). Before using a peripheral you have to enable its clock in the

RCC_AHBENR, RCC_APB2ENR or RCC_APB1ENR register.

4.6 Memory organization:

Program memory, data memory, registers and I/O ports are organized within the same

linear 4-Gbyte address space.

DEPT E&C,SBMJCE 18


19/68


The bytes are coded in memory in Little Endian format. The lowest numbered byte in a

word is considered the words least significant byte and the highest numbered byte the

most significant.

For the detailed mapping of peripheral registers, please refer to the related chapters.

The addressable memory space is divided into 8 main blocks, each of 512 MB.All the memory areas that are not allocated to on-chip memories and peripherals are

considered Reserved). Refer to the Memory map figure in the corresponding product

datasheet.

4.7 POWER SUPPLY OVERVIEW

The device requires a 2.0-to-3.6 V operating voltage supply (VDD). An embedded

regulator is used to supply the internal 1.8 V digital power.

The real-time clock (RTC) and backup registers can be powered from the VBAT

voltage when the main VDD supply is powered off.

Fig4.3. POWER SUPPLY BLOCK

4.8 SPI BLOCK DIAGRAM

DEPT E&C,SBMJCE 19


20/68


Fig4.4. SPI Interface Block Diagram

Usually, the SPI is connected to external devices through 4 pins:

MISO: Master In / Slave Out data. This pin can be used to transmit data in slave

mode and receive data in master mode.

MOSI: Master Out / Slave In data. This pin can be used to transmit data in master

mode and receive data in slave mode.

SCK: Serial Clock output for SPI masters and input for SPI slaves.

NSS: Slave select. This is an optional pin to select a slave device. This pin acts as a

chip select to let the SPI master communicate with slaves individually and to avoid

contention on the data lines. Slave NSS inputs can be driven by standard I/O ports on the

master device. The NSS pin may also be used as an output if enabled (SSOE bit) and driven

low if the SPI is in master configuration. In this manner, all NSS pins from devices connected

to the Master NSS pin see a low level and become slaves when they are configured in NSS

hardware mode. When configured in master mode with NSS configured as an input (MSTR=1

and SSOE=0) and if NSS is pulled low, the SPI enters the master mode fault state: the MSTR

bit is automatically cleared and the device is configured in slave mode.

4.8.1 SINGLE MASTER/SINGLE SLAVE APPLICATION

DEPT E&C,SBMJCE 20


21/68


Fig4.5. Single Master/Slave Application Block Diagram

The MOSI pins are connected together and the MISO pins are connected together. In

this way data is transferred serially between master and slave (most significant bit first). The

communication is always initiated by the master. When the master device transmits data to a

slave device via the MOSI pin, the slave device responds via the MISO pin. This implies full-

duplex communication with both data out and data in synchronized with the same clock signal

(which is provided by the master device via the SCK pin).

4.8.2 Slave select (NSS) pin management

There are two NSS modes:

Software NSS mode: this mode is enabled by setting the SSM bit in the SPI_CR1

register. In this mode, the external NSS pin is free for other application uses and the internal

NSS signal level is driven by writing to the SSI bit in

the SPI_CR1 register.

Hardware NSS mode: there are two cases:

o NSS output is enabled: when the STM32F10xxx is operating as a Master and

the NSS output is enabled through the SSOE bit in the SPI_CR2 register, the

NSS pin is driven low and all the NSS pins of devices connected to the Master

NSS pin see a low level and become slaves when they are configured in NSS

hardware mode When an SPI wants to broadcast a message, it has to pull NSS

low to inform all others that there is now a master for the bus. If it fails to pull

NSS low, this means that there is another master communicating, and a Hard

Fault error occurs.

o NSS output is disabled: the multimaster capability is allowed.

DEPT E&C,SBMJCE 21


22/68


4.8.3 Configuring the SPI in master mode

In the master configuration, the serial clock is generated on the SCK pin.

Procedure

Select the BR[2:0] bits to define the serial clock baud rate.

Select the CPOL and CPHA bits to define one of the four relationships between

the data transfer and the serial clock.

Set the DFF bit to define 8- or 16-bit data frame format

Configure the LSBFIRST bit in the SPI_CR1 register to define the frame format

If the NSS pin is required in input mode, in hardware mode, connect the NSS

pin to a high- level signal during the complete byte transmit sequence. In NSS

software mode, set the

SSM and SSI bits in the SPI_CR1 register. If the NSS pin is required in output

mode, the SSOE bit only should be set.

The MSTR and SPE bits must be set (they remain set only if the NSS pin is

connected to a high-level signal).

In this configuration the MOSI pin is a data output and the MISO pin is a data

input.

Transmit sequence

The transmit sequence begins when a byte is written in the Tx Buffer. The data byte is

parallel-loaded into the shift register (from the internal bus) during the first bit transmission and

then shifted out serially to the MOSI pin MSB first or LSB first depending on the LSBFIRST

bit in the SPI_CR1 register. The TXE flag is set on the transfer of data from the Tx Buffer to

the shift register and an interrupt is generated if the TXEIE bit in the SPI_CR2 register is set.

Receive sequence

For the receiver, when data transfer is complete:

The data in the shift register is transferred to the RX Buffer and the RXNE flag is set

An interrupt is generated if the RXNEIE bit is set in the SPI_CR2 register

At the last sampling clock edge the RXNE bit is set, a copy of the data byte received in the shift

register is moved to the Rx buffer. When the SPI_DR register is read, the SPI peripheral returns

this buffered value. Clearing the RXNE bit is performed by reading the SPI_DR register. A

continuous transmit stream can be maintained if the next data to be transmitted is put in the Tx

DEPT E&C,SBMJCE 22


23/68


buffer once the transmission is started. Note that TXE flag should be 1 before any attempt to

write the Tx buffer is made.

4.9 I2S BLOCK DIAGRAM

Fig4.6. I2S Block Diagram

The SPI could function as an audio I2S interface when the I2S capability is enabled (by

setting the I2SMOD bit in the SPI_I2SCFGR register). This interface uses almost the same

pins, flags and interrupts as the SPI. The I2S shares three common pins with the SPI:

SD: Serial Data (mapped on the MOSI pin) to transmit or receive the two time multiplexed

DEPT E&C,SBMJCE 23


24/68


data channels (in simplex mode only).

WS: Word Select (mapped on the NSS pin) is the data control signal output in master

mode and input in slave mode.

CK: Serial Clock (mapped on the SCK pin) is the serial clock output in master mode

and serial clock input in slave mode.

An additional pin could be used when a master clock output is needed for some external audio

devices:

MCK: Master Clock (mapped separately) is used, when the I2S is configured in master

mode (and when the MCKOE bit in the SPI_I2SPR register is set), to output this

additional clock generated at a preconfigured frequency rate equal to 256 FS,

where FS is the audio sampling frequency. The I2S uses its own clock generator to

produce the communication clock when it is set in master mode. This clock

generator is also the source of the master clock output. Two additional registers are

available in I2S mode. One is linked to the clock generator configuration

SPI_I2SPR and the other one is a generic I2S configuration register SPI_I2SCFGR

(audio standard, slave/master mode, data format, packet frame, clock polarity, etc.).

The SPI_CR1 register and all CRC registers are not used in the I2S mode. Likewise, the

SSOE bit in the SPI_CR2 register and the MODF and CRCERR bits in the SPI_SR are not

used. The I2S uses the same SPI register for data transfer (SPI_DR) in 16-bit wide mode.

4.9.1 Supported audio protocols

The three-line bus has to handle only audio data generally time-multiplexed on two

Channels: the right channel and the left channel. However there is only one 16-bit register for

the transmission or the reception. So, it is up to the software to write into the data register

the adequate value corresponding to the considered channel side, or to read the data from

the data register and to identify the corresponding channel by checking the CHSIDE bit in

the SPI_SR register. Channel Left is always sent first followed by the channel right (CHSIDE

has no meaning for the PCM protocol).

Four data and packet frames are available. Data may be sent with a format of:

16-bit data packed in 16-bit frame




DEPT E&C,SBMJCE 24


25/68


26/68


external master starts the communication. The I2S data register has to be loaded before the

master initiates the communication.

For the I2S, MSB justified and LSB justified modes, the first data item to be written

into the data register corresponds to the data for the left channel. When the communication

starts, the data are transferred from the Tx buffer to the shift register. The TXE flag is then setin order to request the rightchannel data to be written into the I2S data register.

The CHSIDE flag indicates which channel is to be transmitted. Compared to the master

transmission mode, in slave mode, CHSIDE is sensitive to the WS signal coming from the

external master. This means that the slave needs to be ready to transmit the first data before the

clock is generated by the master. WS assertion corresponds to left channel transmitted first.

The data half-word is parallel-loaded into the 16-bit shift register (from the internal bus)

during the first bit transmission, and then shifted out serially to the MOSI/SD pin MSB first.

The TXE flag is set after each transfer from the Tx buffer to the shift register and an interrupt is

generated if the TXEIE bit in the SPI_CR2 register is set.

To secure a continuous audio data transmission, it is mandatory to write the SPI_DR

register with the next data to transmit before the end of the current transmission. An underrun

flag is set and an interrupt may be generated if the data are not written into the SPI_DR register

before the first clock edge of the next data communication. This indicates to the software that

the transferred data are wrong. If the ERRIE bit is set into the SPI_CR2 register, an interrupt is

generated when the UDR flag in the SPI_SR register goes high. In this case, it is mandatory to

switch off the I2S and to restart a data transfer starting from the left channel. To switch off the

I2S, by clearing the I2SE bit, it is mandatory to wait for TXE = 1 and BSY=0.

Reception sequence

The operating mode is the same as for the transmission mode except for the point 1

where the configuration should set the master reception mode using the I2SCFG[1:0] bits in

the SPI_I2SCFGR register. Whatever the data length or the channel length, the audio data are

received by 16-bit packets. This means that each time the RX buffer is full, the RXNE flag in

the SPI_SRregister is set and an interrupt is generated if the RXNEIE bit is set in the SPI_CR2

register.

Depending on the data length and channel length configuration, the audio value

received for a right or left channel may result from one or two receptions into the RX buffer.

The CHSIDE flag is updated each time data are received to be read from SPI_DR. It is

sensitive to the external WS line managed by the external master component. Clearing the

RXNE bit is performed by reading the SPI_DR register.

DEPT E&C,SBMJCE 26


27/68


If data are received while the precedent received data have not yet been read, an

overrun is generated and the OVR flag is set.

If the bit ERRIE is set in the SPI_CR2 register, an interrupt is generated to indicate the

error. To switch off the I2S in reception mode, I2SE has to be cleared immediately after

receiving the last RXNE = 1.

5.1 OPERATING SYSTEM

CircleOS is the multi-application operating system used in the different STM32

Primers. This 'Open source' project was initiated by Raisonance with the objective of providing

an API to access both the hardware peripherals and the user interface. CircleOS also manages

DEPT E&C,SBMJCE 27


28/68


the MEMS accelerometer, the melody generator, the LCD display, the menu utility and the

application launcher.

The CircleOS firmware requires 64 KB of FLASH and 4 KB of RAM, including the

stack usage for the applications. The remaining 448 KB are available for applications, which

can be added or removed at will using a programming tool.

MEMORY MAP OF CIRCLE OS

Fig5.1. Memory Map of Circle OS

5.2 IDE

Ride7 software toolset that allows you to:

modify and compile applications

program the STM32F103xE on the Primer2

DEPT E&C,SBMJCE 28


29/68


and debug the application while it runs on the microcontroller

The Ride7 toolset forSTM32 Primer2 includes:

Ride7: Raisonance Integrated development environment capable of debugging and

programming the target microcontroller. Ride7 provides fully integrated code editing,compiling, device programming and application debugging features from a single easy-

to-use graphical interface.

GNU C compiler for STM32 provides fully optimizing, unlimited compilation

capability. Compiler control is seamlessly integrated in Ride7

Fig5.2. Ride7

6.1 HIGH LEVEL DESIGN

A High-Level Design provides an overview of a solution, platform, system, product,

service, or process.

DEPT E&C,SBMJCE 29


30/68


Such an overview is important in a multi-project development to make sure that each

supporting component design will be compatible with its neighbouring designs and with

the big picture.

The highest level solution design should briefly describe all platforms, systems,

products, services and processes that it depends upon and include any important

changes that need to be made to them.

A high-level design document will usually include a high-level architecture diagram

depicting the components, interfaces and networks that need to be further specified or

developed.

The document may also depict or otherwise refer to work flows and/or data flows

between component systems.

In addition, there should be brief consideration of all significant commercial, legal,

environmental, security, safety and technical risks, issues and assumptions.

The idea is to mention every work area briefly, clearly delegating the ownership of

more detailed design activity whilst also encouraging effective collaboration between

the various project teams.

Today, most high-level designs require contributions from a number of experts,

representing many distinct professional disciplines.

Finally, every type of end-user should be identified in the high-level design and eachcontributing design should give due consideration to customer experience.

High level software design, also called software architecture is the first step to analyze

and consider all requirements for a software and attempt to define a structure which is able to

fullfill them.

For this also the non-functional requirements have to be considered, such as scalability,

portability and maintainability. This first design step has to be more or less independent of a

programming language.

This is not always 100% possible, but a good high level design can be further refined

into a low level design, which then describes the implementation in any desired programming

language.

DEPT E&C,SBMJCE 30


31/68


MIDDLEWARE

STATE MACHINE MENU HANDLER

WAVE FILE

DECODER

FILE BUFFER

MANAGEMENTDECODER

DISPLAY KEYPAD TOUCHSCREEN

AUDIODRIVER SD CARD MEMS

APPLICATION

LAYER

MIDDLEWARE

DRIVERS

Fig6.1. HLD

6.1.2 Application layer

Menu handler

When the device is switched on, the Circle OS call this function,

enum MENU_code Application_Ini ( void ):This function initialises all drivers .

After initialisation the following function is called,

FS_Explorer_Ini ( ): This function initialises the Circle OS explorer which enables us to view

the applications on the device and navigate through them.

Menu:

DEPT E&C,SBMJCE 31


32/68


enum MENU_code Application_Handler ( void ) :This function puts the applications on the

menu and displays as a list for selection.

FS_Explorer ( ): This function helps in navigation

MENU_CONTINUE: This function will keep the explorer open.

MENU_Quit: This function will quit the menu and returns to idle state.

DRAW_Puts : Displays all the error messages .

FS_GetVolumeInfo(0, StartMBR, &volume_info): Shall display the files on SD card.

State Machine:

FS_Explorer ( ) : Shall be used to explore SD card.

FS_OpenFile(&volume_info, CurrentPath,FS_READ, &file_info) :Shall open the file to read.

DRAW_Puts : Shall be used to display the name of file and its information.

void PlayAudioFile(void) : Shall play the file selected.

FS_ReadFile(&file_info, (u8 *)AudioFileHeader, &i, HEADER_SIZE) : Shall check if it is a

valid wave file.

Get_Touch() : Shall take in inputs.

AUDIO_Playback_Stop() : Shall stop playback of a file.

FS_Explorer_Ini ( ) : Shall be used to go back to file selection mode in case quit is selected.

DRAW_Clear() :Shall clear the screen.

FS_Close (&file_info): Shall close the current file.

6.1.3 MIDDLE LAYER

Wave File Decoder:

The functions mentioned below checks the format of the .WAV file and gets information

about the audio format. This is done by reading the value of a number of parameters stored in

the file header and comparing these to the values expected authenticates the format of a

standard .WAV file (44 bytes will be read). If it is a valid .WAV file format, it continues

reading the header to determine the audio format such as the sample rate and the sampled data

DEPT E&C,SBMJCE 32


33/68


size .If the audio format is supported by this application, it retrieves the audio format in

WAVE_Format structure and returns a zero value. Otherwise the function fails and the return

value is nonzero. In this case, the return value specifies the cause of the function fails. The

error codes that can be returned by this function are declared in the header file.

u32 ReadUnit(u8 NbrOfBytes, Endianness BytesFormat) : Checks the header format.

File buffer management:

void FillBuffer(u32 start) : Shall fill the buffer with Music from the SD card.

TIM_ITConfig( TIM5, TIM_IT_Update, DISABLE ) : Shall stop reading music to buffer.

Decoder:

AUDIO_Play(AudioBuffer,sizeof(AudioBuffer) / ((WAVE_Format.BitsPerSample==16) ?

2:1) : Shall play the audio from buffer.

6.2 LOW LEVEL DESIGN

Low Level Design (LLD) is like detailing the HLD. It defines the actual logic for each

and every component of the system. Class diagrams with all the methods and relation between

classes comes under LLD. Programs specs are covered under LLD.

LLD describes each and every module in an elaborate manner so that the programmer

can directly code the program based on this.There will be at least 1 document for each module

and there may be more for a module.The LLD will contain: - deailed functional logic of the

module in pseudo code - database tables with all elements including their type and size - all

interface details with complete API references(both requests and responses) - all dependency

issues -error message listings - complete input and outputs for a module.

The LLD for the following drivers are given in the APPENDIX:

1. Draw inputs 5. File System

2. LCD 6. Touch Screen

3. Joystick /Keypad 7. Audio

4 .MEMS 8. SD Card

DEPT E&C,SBMJCE 33


34/68


The following flowcharts outline the operation of the source code.

Flowcharts have been written for these units of the code:

1. Audio Buffer/output buffer. 2. Touch Input.

2. Menu handler. 4. Wave Parsing.

7.1 FLOWCHART FOR BUFFER

Check for startposition

Overwrite buffer

Retain buffer

Trigger to refill buffer

Check for word

alignment of 1st byte

Check for EOF

Stop playback

Decode data to lowerpart of buffer

Decode data to higherpart of buffer

Check for errors

Zero pad to avoid falsesync after last frame

Check for EOF

Continue Playing

YES

YES

YES

YES

NO

NO

NO

NO

Fig7.1.Buffer

DEPT E&C,SBMJCE 34


35/68


7.2 FLOWCHART FOR TOUCH INPUT

Get Input from

touchscreen

Case:stop

Case:play

Case:eject

Case:off

Stop

playback

Exploring

state(open new

fi le and play)

Shut down

application

Start

Playback

from

beginning

Yes

Yes

Yes

Yes

No

No

No

No

Fig7.2.Touch input

DEPT E&C,SBMJCE 35


36/68


7.3 FLOWCHART MENU HANDLER

IfExploringState=?

CASE1

CASE2

CASE3

If

PlayingState=?

IfIdle State

QUIT menu

Show IDLE screen

YET to SELECTRemain in same

STATE

Display Text

Clear Text

IDLEScreen

Start Playback

YES

YES

YES

YES

YES

NO

NO

NO

NO

YES

NO

Fig7.3.Menu Handler

DEPT E&C,SBMJCE 36


37/68


7.4 WAVE FILE PARSING

Read chunkID

If temp !=RIFF

Read filelength

ErrorReport

If != WAVEformat

Invalidformat

Readformat ID

If !=format IDInvalid

format ID

Read lengthof FMT

Initialiseheader index

41

NO

YES

YES

YES

NO

NO

Fig7.4.Wave Parsing (contd..)

DEPT E&C,SBMJCE 37


38/68


If!=0x10

Read audioformat

Extra formatbytes=1

If!=format tag

Readnumber ofchannels

Read

sample rate

Unsupportedformat tag

Set the sample

rate

If!=Sample rate

Unsupportdsample rate

Read byterate

Read blockAlligenment

2 4

41

YES

YES

YES

NO

NO

NO


DEPT E&C,SBMJCE 38


39/68


!=8||16Bits/sample

Read nuber ofbits/sample

Unsupportedbits/sample

Read extraformatbytes

If extra formatbytes==1

If !=0x00Unsupportedextra format

bytes

Read factchunk

If !=Fact IDReturn invalid fact

chunk ID

Read factchunk data

size

3A

2

4

4

YES

YES

YES

NO

NO

NO

YES

NO


DEPT E&C,SBMJCE 39


40/68


Set index to read

after header en d

Read datachunk

If != Data IDInvalid Da ta chunk

ID

Read no. ofsampleData

Set Data po inter to

beginning of Aud ioData

Return ValidWAVE file

3A

Error

4

NO

YES

Fig7.4.Wave Parsing

DEPT E&C,SBMJCE 40


41/68


7.5 STATE MACHINE

The state machine described below gives the behavior of the system for different inputs.

Fig7.5. State Machine

On entering the application through the menu, the device enters SD card exploring state

where desired audio files are selected for playing. After the file has been selected for playing,

the device enters run state. The device after entering the run state can go back to exploring state

if the eject icon is pressed and can go to idle state if the stop icon is pressed and can go to main

startup screen if the shutdown icon is pressed.

DEPT E&C,SBMJCE 41


42/68


8.1 TEST RESULTS

The following test results explain how each requirement was being met.

Test results have been given for each requirement which was specified earlier.

1. This is the picture of the startup screen which appears when the device is powered ON.

Fig21. Startup Screen.

1. This is the picture displaying the menu.

Fig22. Menu Screen.

2. This is the picture displaying the screen which appears when the SD card is not

inserted.

Fig23. SD check Screen.

DEPT E&C,SBMJCE 42


43/68


3. This is the picture displaying the idle screen in the application. This screen appears

when user stops the playback.

Fig24. Idle Screen.

4. This is the picture displaying the screen which appears when a file is being played.

Fig25. Run Screen.

DEPT E&C,SBMJCE 43


44/68


FUTURESCOPE

A media playback system can be designed from the newest of the processors in the

market, such as ARM A-8, INTEL ATOM or any other MIPS processors, making it further

more sophisticated and fast.

The device can be upgraded to provide various features like:

Support multiple media formats such as mp3 and mp4 with the use of various codecs.

Digital meta-data on digital audio collection, such as album arts, genre, ratings, year

etc.

Windows like User Interface.

Ability to view photos and play music on same device.

Support for multi-language menus.

Ability to produce HD audio.

And many more.

CONCLUSION

When designing a media playback system that is compact and portable, power

efficiency of the system is the buzz word. This system employs a processor which consumes

the lowest possible power among the leading processors available.

There are various other factors which shall play a vital role in making a media playback system

laudable. Cost, size, user-interface and reliability being such factors. The system is designed

considering the facts that it shall not exceed the size of a palm, does not exceed 4Gs, has a user

friendly application and has been tested to be free from bugs. There is no wear and tear on the

media files like on a physical disc. The device produces a noiseless playback and has no

moving parts making it more reliable.

DEPT E&C,SBMJCE 44


45/68


BIBLIOGRAPHY

[1] Embedded System Design: A Unified Hardware/Software Introduction. John Wiley andSons, ISBN: 0471386782, October 2001.

[2] Microsoft Corporation (June 1998). "WAVE and AVI Codec Registries - RFC 2361".

IETF. http://tools.ietf.org/html/rfc2361. Retrieved 2009-12-06.

[3] Arm cortex-M3 Complete reference manual.

[4] http://arm.com/DDI0405C_arm_architecture_v7m_application_level

_reference_manual.pdf

[5] www.arm.com/products/processors/cortex-m/cortex-m3.php

[6] infocenter.arm.com/...arm.doc.../DDI0337E_cortex_m3_r1p1_trm.pdf

[7] http://www.stm32circle.com/schematics_stm32_primer2_1_2.PDF

[8] http://en.wikipedia.org/wiki/Wav

[9] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0337e/index.html

[10] www.st.com/mcu/familiesdocs-110.html

[11] http://en.wikipedia.org/wiki/Digital_audio_player

[12] http://www.stm32circle.com/resources/stm32primer2.php

[13] www.educypedia.be/electronics/I2C.htm

[14] http://www.industryconvergence.com/evolution of media players

[15] http://en.wikipedia.org/wiki/businessreports

[16] http://en.wikipedia.org/wiki/rtos

DEPT E&C,SBMJCE 45
http://arm.com/DDI0405C_arm_architecture_v7m_application_levelhttp://arm.com/DDI0405C_arm_architecture_v7m_application_level


46/68


1. LLD_DRAW INPUTS

LLD_vbattoa static void vbattoa( u8* ptr, u16

X )

This function convert an

u16 in ascii radix 10

LLD_DRAW_DisplayStringW

ithMode

static void

DRAW_DisplayStringWithMode(u8 x, u8 y, const u8* ptr, u8 len,

s32 mode )

This function is used to

display a character string(17 char max)at given X,

Y coordinates on the

LCD display.This

function is the user

interface to use the LCD

driver.

LLD_DRAW_Init void DRAW_Init( void ) Initialize GUI drawing.

Called at CircleOS

startup.

LLD_DRAW_Handler void DRAW_Handler( void ) Called by CircleOS to

manage DRAW tasks

such as screen

orientation.

LLD_DRAW_Batt void DRAW_Batt( void ) Draw the battery at xBat

and yBat set in

DRAW_Ini

LLD_DRAW_Line_Circle void DRAW_Line_Circle (s16 x1,

s16 y1, s16 x2, s16 y2, u16 color )

Draw a line on the LCD

screen. Optimized for

horizontal/vertical

lines,and use the

Bresenham algorithm

for other cases.

LDD_DRAW_Cross_Absolute void DRAW_Cross_Absolute(s16

x1, s16 y1, u16 color, u16

CrossSize)

Draw a cross on the

screen.

LDD_DRAW_SetCharMagni

Coeff

void

DRAW_SetCharMagniCoeff( u16

Coeff )

Set the magnifying value

for the characters

(should be 1 or 2)

LDD_DRAW_GetCharMagni

Coeff

u16 DRAW_GetCharMagniCoeff(

void )

Return the current

magnifying value for the

characters

LLD_DRAW_GetTextColor u16 DRAW_GetTextColor( void ) Return current text

color.

LLD_DRAW_SetTextColor void DRAW_SetTextColor( u16 Set current text color.

DEPT E&C,SBMJCE 46


47/68


Color )

LLD_DRAW_GetBGndColor u16 DRAW_GetBGndColor( void

)

Return current

background color.

LLD_DRAW_SetBGndColor void DRAW_SetBGndColor(u16

Color)

Set current background

color

LLD_ DRAW_Clear void DRAW_Clear( void ) Clear the LCD display.

Draw Batterie and

butterfly if main display.

LLD_DRAW_SetLogoBW void DRAW_SetLogoBW( void ) Draw the butterfly logo

LLD_ DRAW_SetImage void DRAW_SetImage( const

u16* imageptr, u8 x, u8 y, u8

width, u8 height )

The provided bitmap is

made width * height 2

byte words. Each 2 byte

word contains the RGBcolor of a pixel.

LLD_ DRAW_SetImageSel void DRAW_SetImageSel( const


width, u8 height, u16

oldBgndColor, u16

newBgndColor )


made width * height 2

byte words. Each 2 byte

word contains the RGB

color of a pixel. All

pixels with the

oldBgndColor are

replaced with thenewBgndColor

LLD_ DRAW_SetImageBW void DRAW_SetImageBW( const


width, u8 height )


made of width * height

bits where a set bit

means a pixel drawn in

the current text color,

whereas an unset bit

means a pixel drawn in

the current backgroundcolor.

LLD_ DRAW_DisplayVbat void DRAW_DisplayVbat( u8 x,

u8 y )


display vbat in ascii

LLD_ DRAW_DisplayTime void DRAW_DisplayTime( u8 x,

u8 y )


display time in ascii on

LCD

LLD_ DRAW_DisplayString void DRAW_DisplayString( u8 x,

u8 y, const u8* ptr, u8 len )


display a character string

(17 u8 max)* at given

DEPT E&C,SBMJCE 47


48/68


X, Y coordinates on the

LCD display.

LLD_

DRAW_DisplayStringInverted

void

DRAW_DisplayStringInverted( u

8 x, u8 y, const u8* ptr, u8 len )



(17 char max) at given

X, Y coordinates on theLCD display, with

inverted colors.

LLD_

DRAW_SetDefaultColor

void DRAW_SetDefaultColor

(void)

Reset text and

background colors to

their default values.

LLD_ DRAW_DisplayTemp void DRAW_DisplayTemp( u8 x,

u8 y )


display the current

temperature in ascii.Thechoice between Celcius

and Fahrenheit is fixed

by

UTIL_SetModeTemp()

LLD_ DRAW_Line void DRAW_Line (s16 x1, s16

y1, s16 x2, s16 y2, u16 color )

Draw a line on the LCD

screen. Optimized for

horizontal/vertical

lines,and use the

Bresenham algorithmfor other cases.

LLD_ DRAW_Putc void DRAW_Putc( u8 Ascii ) Display at current

coordinates the provided

ASCII character with the

current text and

background colors and

with the current magnify

coefficient.

LLD_ DRAW_Puts void DRAW_Puts( const u8* ptr ) This function is used to


at current coordinates on

the LCD display. This

function is the user

interface to use the LCD

driver.

LLD_ DRAW_SetCursorPos void DRAW_SetCursorPos( s32

x, s32 y )


set the current positionof the cursor.This

position is used by the

DEPT E&C,SBMJCE 48


49/68


DRAW_putc and

DRAW_Puts functions.

LLD_ DRAW_GetCursorPos s32 DRAW_GetCursorPos() This function is used to

get the current position

of the cursor.

LLD_

DRAW_SetCursorMargin

void

DRAW_SetCursorMargin( s32 lx,

s32 rx, s32 hy, s32 ly )


set the current margins

for the cursor.This

position is used by the

DRAW_putc and


LLD_

DRAW_GetCursorMargin

void

DRAW_GetCursorMargin( s32*

lx, s32* rx, s32* hy, s32* ly )


get the current margins

for the cursor.Thisposition is used by the

DRAW_putc and


2.LLD_LCD

LLD_LCD_DataLinesConfig static void

LCD_DataLinesConfig( DataConfig

Mode_TypeDef Mode )

Configure data lines

D0~D7 in Input

Floating mode for

read from LCD or in

Output Push-Pull

mode for write on

LCD

LLD_LCD_DataLinesWrite static void

LCD_DataLinesWrite( GPIO_TypeD

ef* GPIOx, u32 PortVal )

Write a value on

D0~D7

LLD_LCD_CtrlLinesConfig static voidLCD_CtrlLinesConfig( void )

Configure controllines in Output Push-

Pull mode.

LLD_LCD_CtrlLinesWrite static void

LCD_CtrlLinesWrite( GPIO_TypeDe

f* GPIOx, u32 CtrlPins, BitAction

BitVal )

Set or reset control

lines.

LLD_LCD_CheckLCDStatus static void

LCD_CheckLCDStatus( void )

Check whether LCD

is busy or not.

LLD_LCD_DrawCharSetFilter void LCD_DrawCharSetFilter( s32 Define a restriction

DEPT E&C,SBMJCE 49


50/68


xmin, s32 xmax, s32 ymin, s32 ymax

)

area for

LCD_DrawChar

(used for the

first/last line when

scrolling lists).

LLD_LCD_DrawChar static void LCD_DrawChar( u8 x, u8y, u8 width, const u8* bmp, u16

textColor, u16 bGndColor, u16

charMagniCoeff )

Draw a character onthe LCD screen.

LLD_LCD_DisplayRotate static void

LCD_DisplayRotate( Rotate_H12_V

_Match_TypeDef H12 )

Configure the LCD

controller for a given

orientation.

LLD_LCD_7637_Controller static void

LCD_7637_Controller( void )

Initialization of the

controller registers.

LLD_LCD_ST7732S_Controll

er_init

void LCD_ST7732S_Controller_init(

void )

Initialization of the

controller registers.

LLD_LCD_BackLightConfig void LCD_BackLightConfig( void ) Setting of the PWM

that drives the

backlight intensity.

LLD_LCD_BackLightChange static void

LCD_BackLightChange( void )

Modify the PWM

rate.

LLD_LCD_Init void LCD_Init( void ) Initialize LCD.

Called at CircleOS

startup.

LLD_ LCD_Handler void LCD_Handler( void ) Called by the

CircleOS scheduler

to manage LCD

tasks.

LLD_LCD_FillRect_Circle void LCD_FillRect_Circle( u16 x,

u16 y, u16 width, u16 height, u16

color )

Fill a rectangle with

a provided

color.This function

does not check

parameters validity

LLD_LCD_SendLCDCmd void _LCD_SendLCDCmd(void) Call

LCD_SendLCDCmd

function, with the

ST7637_RAMWR

orST7732_RAMWR

DEPT E&C,SBMJCE 50


51/68


parameter

LLD_ LCD_Batt void LCD_Batt(u16 xBat, u16 yBat,

s32 fDisplayTime, u16 BatState,

u16* OldBatState, s32 divider_coord,

u16* widthBat, u16* heightBat)

Draw the battery

LLD_LCD_Clear void LCD_Clear (u16 xBat,u16

yBat)

Draw the batterie

and the toolbar

LLD_LCD_Scroll void LCD_Scroll (u8 Ascii, s32

PosCurX,s32 *PosCurY,s32

RightMarginX,s32 LeftMarginX,s32

HighMarginY,s32 LowMarginY,u16

BGndColor, u16 TextColor,u16

CharMagniCoeff )

Scroll the screen

each line to the top

LLD_LCD_SendLCDCmd void LCD_SendLCDCmd( u8 Cmd ) Send on command

byte to the LCD.

LLD_LCD_SendLCDData void LCD_SendLCDData( u8 Data ) Send one data byte

to the LCD.

LLD_ LCD_ReadLCDData u32 LCD_ReadLCDData( void ) Read one data byte

from the LCD.

LLD_LCD_FillRect void LCD_FillRect( u16 x, u16 y,

u16 width, u16 height, u16 color )

Fill a rectangle with

a provided color.

LLD_LCD_DrawRect void LCD_DrawRect( u16 x, u16 y,

u16 width, u16 height, u16 color )

Draw a rectangle

with a provided

color.

LLD_LCD_DrawPixel void LCD_DrawPixel( u8 XPos, u8

YPos, u16 Color )

Draw a pixel on the

LCD with the

provided color.

LLD_LCD_RectRead void LCD_RectRead( u16 x, u16 y,

u16 width, u16 height, u8* bmp )

Save the pixels of a

rectangle part of theLCD into a RAM

variable

LLD_ LCD_GetPixel u16 LCD_GetPixel( u8 x, u8 y ) Read the RGB color

of the pixel the

coordinate are

provided in

parameter.

LLD_ LCD_DisplayChar void LCD_DisplayChar( u8 x, u8 y,u8 Ascii, u16 TextColor, u16

BGndColor, u16 CharMagniCoeff)

Display at providedcoordinates the

provided ASCII

DEPT E&C,SBMJCE 51


52/68


character with the

provided text and

background colors

and with the

provided magnify

coefficient.

LLD_ LCD_SetRect_For_Cmd void LCD_SetRect_For_Cmd( s16 x,

s16 y, s16 width, s16 height )

Define the rectangle

for the next

command to be

applied.

LLD_ LCD_SetBackLight void LCD_SetBackLight( u32

newBacklightStart )

Modify the PWM

rate. Any value

below

BACKLIGHTMIN

reset the value to the

default value

LLD_ LCD_SetBackLightOff void LCD_SetBackLightOff( void ) Switch the LCD

back light off.

LLD_ LCD_SetBackLightOn void LCD_SetBackLightOn( void ) Switch the LCD

back light on.

LLD_ LCD_GetBackLight u32 LCD_GetBackLight( void ) Returns le LCD

PWM rate.

LLD_ LCD_SetRotateScreen void LCD_SetRotateScreen( u8

RotateScreen)

Enable or disable the

ability of the screen

display to rotate

according to the

MEMs information.

LLD_ LCD_GetRotateScreen u8 LCD_GetRotateScreen( void ) Return the screen

rotation mode.

LLD_LCD_SetScreenOrientation

voidLCD_SetScreenOrientation( Rotate_

H12_V_Match_TypeDef

ScreenOrientation )

Set the screenorientation.

LLD_

LCD_GetScreenOrientation

Rotate_H12_V_Match_TypeDef

LCD_GetScreenOrientation( void )

Return current

screen orientation.

LLD_ LCD_SetFont void LCD_SetFont(u8* NewFont) Change the current

font, with the

specified new one.

DEPT E&C,SBMJCE 52


53/68


LLD_ LCD_SetDefaultFont void LCD_SetDefaultFont(void) Restore the default

system font.

3. LLD_JOYSTICK

LLD_JOYSTICK_Handler void JOYSTICK_Handler( void ) Called by the

CircleOS

scheduler to

manage Joystick

tasks

LLD_JOYSTICK_CircularPermuta

tion

enum JOYSTICK_state

JOYSTICK_CircularPermutation

(enum JOYSTICK_state

abs_direction, s32 iter)

1. Current

direction.

2. Number of

permutations.

3. The new

direction value.

LLD_BUTTON_SetMode void BUTTON_SetMode( enum

BUTTON_mode mode )

Sets new button

mode

LLD_BUTTON_GetMode enum BUTTON_mode

BUTTON_GetMode( void )

Returns current

button mode.

LLD_BUTTON_GetState enum BUTTON_state

BUTTON_GetState( void )

Returns current

button state.

LLD_BUTTON_WaitForRelease void

BUTTON_WaitForRelease( void )

Disable

temporarily any

new button

event.

LLD_JOYSTICK_GetState enum JOYSTICK_state

JOYSTICK_GetState(void)

Decodes the

Joystick

direction.

LLD_JOYSTICK_WaitForRelease void

JOYSTICK_WaitForRelease( void )

Disable

temporarily any

new button

event.

4.LLD_MEMS

LLD_MEMS_WakeUp static void MEMS_WakeUp( void ) Wake Up Mems.

DEPT E&C,SBMJCE 53


54/68


LLD_MEMS_ReadOut

XY

static u32 MEMS_ReadOutXY( void ) Reads X and Y

Out.return An

unsigned 32 bit

word with the

highest 16 bitscontaining the Y

and the lowest 16

bits the X.

LLD_MEMS_ChipSel

ect

static void MEMS_ChipSelect( u8 State) Selects or deselects

the MEMS device.

LLD_MEMS_SendByt

e

static u8 MEMS_SendByte( u8 byte ) Sends a byte

through the SPI

interface and returnthe byte received

from the SPI bus.

LLD_MEMS_Init void MEMS_Init(void) Initializes the

peripherals used by

the SPI MEMS

driver.

LLD_MEMS_Handler void MEMS_Handler( void ) Called by the

CircleOS scheduler

to manage the

MEMS. The Circle

beeps if the MEMS

is shocked.

LLD_MEMS_ReadID u8 MEMS_ReadID( void ) Reads SPI chip

identification.

LLD_

MEMS_GetPosition

void MEMS_GetPosition( s16* pX, s16*pY ) Returns the current

(relative) position of

the Primer.Only X-Y axis are

considered here.

LLD_MEMS_GetRota

tion

void MEMS_GetRotation

(Rotate_H12_V_Match_TypeDef*pH12)

Returns current

screen orientation.

LLD_MEMS_SetNeutr

al

void MEMS_SetNeutral( void ) Set current position

as "neutral

position".

LLD_MEMS_GetInfo tMEMS_Info* MEMS_GetInfo( void ) Return the current

MEMS information

DEPT E&C,SBMJCE 54


55/68


(state, absolute

position...).

5. LLD_FILESYSTEM

LLD_FS_Explorer_

UpdateList

NODEBUG void

FS_Explorer_UpdateList()

Populate the list with

contents of current

directory.

LLD_FS_Mount u32 FS_Mount(enum STORAGE_device

device)

Initializes and connects

selected device to file

system.

LLD_FS_Unmount u32 FS_Unmount(enum

STORAGE_device device)

Deinitializes and

disconnects selected

device to file system.

LLD_FS_OpenFile u32 FS_OpenFile(PVOLINFO volinfo, u8

*path, u8 mode, PFILEINFO fileinfo)

Call FS_OpenFile with

mode = FS_READ and

supply a path and the

relevant VOLINFO

structure. FS_OpenFile

will populate a

FILEINFO that can be

used to refer to the file.

LLD_FS_ReadFile u32 FS_ReadFile(PFILEINFO fileinfo,

u8 *buffer, u32 *successcount, u32 len)

Reads the file

LLD_FS_WriteFile u32 FS_WriteFile(PFILEINFO fileinfo,

u8 *buffer, u32 *successcount, u32 len)

Call DFS_OpenFile

with mode =

DFS_WRITE and

supply a path and the

relevant VOLINFO

structure.

DFS_OpenFile willpopulate a FILEINFO

that can be used to refer

to the file.

LLD_FS_Close u32 FS_Close(PFILEINFO fileinfo) Close file.

LLD_FS_Seek void FS_Seek(PFILEINFO fileinfo, u32

offset)

Seek file pointer to a

given position.

LLD_FS_Delete u32 FS_Delete(PVOLINFO volinfo, u8

*path)

Delete file or directory.

LLD_FS_GetNextE u32 FS_GetNextEntry(PVOLINFO Search next entry of the

DEPT E&C,SBMJCE 55


56/68


ntry volinfo, PDIRINFO dirinfo, PDIRENT

dirent)

directory.

LLD_FS_OpenDire

ctory

u32 FS_OpenDirectory(PVOLINFO

volinfo,u8 *dirname, PDIRINFO dirinfo)

Open directory.

LLD_FS_GetVolum

eInfo

u32 FS_GetVolumeInfo(u8 unit, u32

startsector, PVOLINFO volinfo)

Gets the volume

informations

LLD_FS_Explorer_

Ini

enum MENU_code FS_Explorer_Ini () Checks the presence of

the SDCARD,

initializes various

structures and lists the

root directory.

LLD_FS_Explorer s32 FS_Explorer () Navigation into the

SDCARD folders,

through a list,and

selection of a file.

LLD_FS_GetSDCar

dCurrentPath

u8* FS_GetSDCardCurrentPath (void) Get the Currentpath of

the SDCard, updated

during navigation with

the explorer.

LLD_FS_GetSDCar

dVolInfo

VOLINFO* FS_GetSDCardVolInfo

( void )

Get the volume

informations of the

SDCard,structurepopulated by the

FS_Explorer_Ini().

This structure is

necessary for file

access,

(FS_OpenFile,

FS_ReadFile,

FS_Seek...).

LLD_FS_GetPathFi

lter

u8* FS_GetPathFilter ( void ) Get the filter applied to

the file type during

exploring the SDCard

LLD_FS_SetPathFil

ter

void FS_SetPathFilter ( u8* filter ) Set the filter applied to

the file type during

exploring the

SDCard.A null pointer

indicates no filter

DEPT E&C,SBMJCE 56


57/68


LLD_NVIC_Config

_SDIO

void NVIC_Config_SDIO(void) Configures SDIO IRQ

channel.

6. LLD_TOUCHSCREEN

LLD_TOUCHSCR_Handler void TOUCHSCR_Handler() Called by the

CircleOS scheduler

to manage the

touchscreen.

LLD_TOUCHSCR_SetMode void

TOUCHSCR_SetMode( TOUCHS

CR_Mode_enum mode )

Change the mode of

the touchscreen.

LLD_TOUCHSCR Drawing void

TOUCHSCREEN_Drawing( void )

This function

provides a mini

"scribble"

functionality.

LLD_TOUCHSCR_Init void TOUCHSCR_Init() Called by the

CircleOS scheduler

to initialize the

touchscreen.

LLD_TOUCHSCR calibration void

TOUCHSCREEN_Calibration()

Takes care of

caliberation of thescreen

LLD_TOUCHSCR_GetPos u16 TOUCHSCR_GetPos( void ) Return the current

position of the point

touched.

LLD_TOUCHSCR_GetAbsPo

s

u16

TOUCHSCR_GetAbsPos( void )

Return the current

absolute position of

the point

touched.This

position is

independant with the

orientation of the

screen.

LLD_TOUCHSCR_IsPressed bool

TOUCHSCR_IsPressed( void )

Return info if the

screen has been

touched or not.

LLD_TOUCHSCR_GetMode TOUCHSCR_Mode_enum

TOUCHSCR_GetMode( void )

Return info if the

touchscreen is in

calibration or not.

DEPT E&C,SBMJCE 57


58/68


LLD_TOUCHSCR_SetSensibi

lity

void

TOUCHSCR_SetSensibility( u16

sens )

Set the sensibility of

the touch detection.

7. LLD_AUDIO

LLD_AUDIO_DeviceSoftwar

eReset

void

AUDIO_DeviceSoftwareReset(voi

d)

Reset the audio codec.

LLD_AUDIO_Init void AUDIO_Init( void ) General initialization of the

STw5094a audio

codec.Only the I2C

interface is activated.

LLD_AUDIO_Handler void AUDIO_Handler( void ) Called by the CircleOS

scheduler to manage audio

tasks.

LLD_AUDIO_CODEC_Init_

I2C

void AUDIO_Init_I2C() Initialization of I2C

communication I2C is used

to configure the STw5094a

audio codec

LLD_AUDIO_Init_audio_mo

de

void

AUDIO_Init_audio_mode(AUDIO_DeviceMode_enum

mode,AUDIO_Length_enum

length, AUDIO_Frequency_enum

frequency, AUDIO_Format_enum

format)

Initialization for Audio

Mode use of the STw5094acodec:- set STw5094a to

Audio Mode via I2C-

enable STM32 I2S

communication to send

audio samples (SPI3/I2S3

port) in DMA mode

LLD_AUDIO_Init_voice_mo

de

void

AUDIO_Init_voice_mode( AUDI

O_DeviceMode_enum mode )

Initialization for Voice

Mode use of the STw5094a

codec:- set STw5094a toVoice Mode via I2C

LLD_AUDIO_Shutdown void AUDIO_Shutdown( void ) Called by the CircleOS

scheduler to shutdown the

audio codec.

LLD_AUDIO_I2C_Read_Re

gister

u8

AUDIO_I2C_Read_Register(u8

register_to_read)

Reads a data byte from one

of STw5094A

configuration registers.

DEPT E&C,SBMJCE 58


59/68


LLD_AUDIO_I2C_WriteReg

ister

void

AUDIO_I2C_WriteRegister(u8

register_to_write, u8

data_to_write)

Send a data byte to one of

STw5094A configuration

registers.

LLD_AUDIO_I2C_WriteMul

tByte

void

AUDIO_I2C_WriteMultByte(u8WriteAddr, u8 NumByteToWrite,

u8* pBuffer)

Sends a data buffer to

STw5094A configurationregisters.

LLD_AUDIO_I2C_ReadMult

Byte

s32

AUDIO_I2C_ReadMultByte(u8

ReadAddr, u8 NumByteToRead,

u8* pBuffer)

Reads "NumByteToRead"

bytes from STw5094A

configuration registers and

stores them in "pBuffer".

LLD_AUDIO_BUZZER_Set

ToneFrequency

void

AUDIO_BUZZER_SetToneFrequency ( u16 freq )

Set the frequency of the

audio tone generator for theaudio buzzer.

LLD_AUDIO_BUZZER_On

Off

void

AUDIO_BUZZER_OnOff(ON_O

FF_enum mode)

Set the RTE switch of the

audio codec ON or OFF, in

order to mute or not the

audio buzzer.If RTE = ON,

the buzzer is active through

Loudspeaker and

Headphones,depending of

the MUT switch position

LLD_AUDIO_Set_Volume void AUDIO_Set_Volume( void ) Sets the volume status

LLD_AUDIO_Cpy_Mono void AUDIO_Cpy_Mono() Copy Mono data to small

buffer, set both Left+Right

Channel to samme value

LLD_AUDIO_SetMode void

AUDIO_SetMode( AUDIO_Devi

ceMode_enum mode,

AUDIO_Length_enumlength,AUDIO_Frequency_enum frequency

AUDIO_Format_enum format)

Set new codec mode. Mode

can be * AUDIO_MODE

* VOICE_MODE

LLD_AUDIO_GetMode AUDIO_DeviceMode_enum

AUDIO_GetMode()

Get the current codec

mode. Mode can be

* AUDIO_MODE

* VOICE_MODE

LLD_AUDIO_Play void AUDIO_Play( sound_type *buffer, s32 size )

Issues audio samples(stored in buffer) to the

DEPT E&C,SBMJCE 59


60/68


audio codec via I2S.

LLD_AUDIO_Playback_Stop void AUDIO_Playback_Stop( ) Stop the playback by

stopping the DMA transfer.

LLD_AUDIO_Playback_Get

Status

AUDIO_Playback_status_enum

AUDIO_Playback_GetStatus()

Gets the status of playback

mode.

LLD_AUDIO_PlaybackBuffe

r_GetStatus

AUDIO_PlaybackBuffer_Status

AUDIO_PlaybackBuffer_GetStatu

s(AUDIO_PlaybackBuffer_Status

value)

Gets the status of Playback

buffer.

LLD_AUDIO_SPEAKER_O

nOff

void

AUDIO_SPEAKER_OnOff(ON_

OFF_enum mode)

Set the PLS switch of the

audio codec ON or OFF, in

order to mute or not the

loudspeaker.If PLS = ON,

the Loudspeaker is active

for audio and buzzer.

LLD_AUDIO_MUTE_OnOff void

AUDIO_MUTE_OnOff(ON_OFF

_enum mode)

Set the MUT switch of the

audio codec ON or OFF.If

MUT = ON, both buzzer,

Loudspeaker and

Headphones are cut off.

LLD_AUDIO_isMute bool AUDIO_IsMute(void) Indicates if the audio is

MUTE or not.If MUT =

ON, both buzzer,

Loudspeaker and

Headphones are cut off.

LLD_AUDIO_Inc_Volume void AUDIO_Inc_Volume(u8 dB) Increment the volume of

the loudspeaker and

headphones.

LLD_AUDIO_Dec_Volume void AUDIO_Dec_Volume(u8

dB)

Decrement the volume of

the loudspeaker and

headphones.

LLD_AUDIO_ReadRegiste-r u8 AUDIO_ReadRegister(u8

register_to_read)

Reads a data byte from one

of STw5094A

configuration registers.

LLD_AUDIO_WriteRegister void AUDIO_WriteRegister(u8

register_to_write, u8data_to_write)

Send a data byte to one of

STw5094A configurationregisters.

DEPT E&C,SBMJCE 60


61/68


LLD_AUDIO_SetLocalBuffe

rSize

void

AUDIO_SetLocalBufferSize(s32

size)

Adjust the size of the local

buffer used in MONO

mode.

8. LLD_SD CARD

LLD_ SD_SendSDStatus SD_Error SD_SendSDStatus(uint32_t

*psdstatus)

Returns the current SD

card's status.

LLD_ SD_ProcessIRQSrc SD_Error SD_ProcessIRQSrc(void) Allows to process all the

interrupts that are high.

LLD_SD_ CmdError static SD_Error CmdError(void) Checks for error

conditions for CMD0.

LLD_SD_CmdResp7Error

static SD_Error CmdResp7Error(void) Checks for errorconditions for R7.

LLD_ CmdResp1Error static SD_Error

CmdResp1Error(uint8_t cmd)

Checks for error

conditions for R1.

LLD_ CmdResp3Error static SD_Error CmdResp3Error(void) Checks for error

conditions for R3 (OCR).

LLD_ CmdResp2Error static SD_Error CmdResp2Error(void) Checks for error

conditions for R2 (CID or

CSD).

LLD_ CmdResp6Error static SD_Error

CmdResp6Error(uint8_t cmd, uint16_t

*prca)

Checks for error

conditions for R6 (RCA).

LLD_ SDEnWideBus static SD_Error

SDEnWideBus(FunctionalState

NewState)

Enables or disables the

SDIO wide bus mode.

LLD_

IsCardProgramming

static SD_Error

IsCardProgramming(uint8_t *pstatus)

Checks if the SD card is in

programming state.

LLD_ FindSCR static SD_Error FindSCR(uint16_t

rca, uint32_t *pscr)

Find the SD card SCR

register val.

LLD_

convert_from_bytes_to_p

ower_of_two

static uint8_t

convert_from_bytes_to_power_of_tw

o(uint16_t NumberOfBytes)

Converts the number of

bytes in power of two and

returns the power.

LLD_GPIO_Configuration

static void GPIO_Configuration(void) Configures the SDIOCorresponding GPIO

DEPT E&C,SBMJCE 61


62/68


Ports

LLD_

DMA_TxConfiguration

static void

DMA_TxConfiguration(uint32_t

*BufferSRC, uint32_t BufferSize)

Configures the DMA2

Channel4 for SDIO Tx

request.

LLD_

DMA_RxConfiguration

static void

DMA_RxConfiguration(uint32_t

*BufferDST, uint32_t BufferSize)

Configures the DMA2

Channel4 for SDIO Rx

request.

SCHEMATICS

DEPT E&C,SBMJCE 62


63/68


USB INTERFACE

DEPT E&C,SBMJCE 63


64/68


POWER SUPPLY SYSTEM

BATTERY UNIT & SUPPLY

DEPT E&C,SBMJCE 64


65/68


CLOCK SOURCE

MEMS

DEPT E&C,SBMJCE 65


66/68


MEMS POWER SUPPLY

JOYSTIC CONNECTOR

DEPT E&C,SBMJCE 66


67/68


SD CARD CONNECTOR

USB

DEPT E&C,SBMJCE 67


68/68


USB INTERFACE

Wav File Playback System

Documents

Transcript of Wav File Playback System