BU94601KV_12 Datasheet, PDF (26/70 Pages) Rohm – AAC/WMA/MP3 +SD Memory Card + iPod

BU94601KV BU94603KV BU94604BKV
Datasheet
20.2 Playable file (BU94601KV doesn’t support AAC/WMA files)
The playable file extensions are *.M4A, *.3GP and *.MP4 for AAC files, *.WMA and *.ASF for WMA files, *.MP3,
*.MP2 and *.MP1 for MP3 files. (Upper case letters and lower case letters are not distinguished.) Note that
the file operation differs in the following cases:
(1) SEL_MP3: See SEL_MP3 for details.
(2) Attribute: AAC/WMA/MP3 file whose attribute is masked can be played. A file with system attributes
cannot be played.
(3) Data destroyed file: When the data section of AAC/WMA/MP3 file is destroyed, the music data of the file
can be played as much as possible rather than disabling to play the entire file. The section which cannot
be played is muted. However, AMUTE terminal remains the H output level. When the header section of
WMA and AAC file is destroyed, it plays next.
(4) File name: A file name and its size do not depend on playing.
(5) Extension: When file data is configured in the non-AAC format and its file extension is *.M4A, *.3GP and
*.MP4 the state is play next. When file data is configured in the non-WMA format and its file extension is
*.WMA, or *.ASF, the state is play next. When file data is configured in the non-MP3 format and its file
extension is *.MP3, *.MP2 or *.MP1, the state is silent playing basically. If playable data can be read, only a
part of the file can be played. The information on time required to output serial status also becomes
uncertain. Then, partial output is done but the correct time information is not output.
(6) File size: When file size is “0”, the file do not recognize at AAC/WMA/MP3 files.
(7) This LSI corresponds to the AAC file encoded by iTunes. The versions of iTunes checked operation are 4.*,
5.*, 6.*, and 7.0 to 7.5. The AAC file encoded with other software may cause fault, such as being in the
middle of reproduction and skipping to next.
(8) When the extension of WMA file is *.ASF, this LSI corresponds to the ASF file of only an audio stream.
20.3 Playing sequence
The playing sequence of supported files is determined based on the following rules. See Figure24.
(1) Folders are sorted in the order written in FAT (in the order of FAT), and files 1 to 100 are sorted in the order
of UNICODE. (*See Chapter 20.4.) Files over 100 are sorted in the order of FAT. Folders over 100 are
sorted in the same manner.
Files are sorted following SEL_MP3. Folders are sorted including null folders and those in which
supported files are not written. Within each folder, supported files over 100 and folders over 100 are
played in the order written to the FAT directory entry.
Since how to write to the directory entry depends on the OS (Operating System) processing to write to the
memory, you cannot understand the file playing sequence.
(2) When supported files exist in the root folder (the highest layer), the files are played first.
(3) When all the files in the root folder have been played, those in the folder under the root folder, if any, are
played.
(4) When a folder is layered under that, files in the folder are played. When not, the master searches any
other folders at the same layer and plays the one, if any.
(5) After playing all the files, the master returns to the root folder as described in (2) and start playing with the
first sorted file.
20.4 Folder/file sort
Folders and files are sorted in the following sequence using this LSI.
(1) Obtain up to 100 files and 100 folders in the order written to FAT.
(2) Compare the obtained folder/file names up to 14 characters (including filename extensions) and sort them
in the ascending order.*
(3) When the same strings are generated, follow the order written to FAT.
(4) For 101 or more folders and files, follow the order written to FAT.
* The processing of the file name and the folder name is shown in the following.
1)When the LFN(long file name) entry exists, folder/filename is processed as one character in two bytes.
2)When the LFN entry doesn't exist, the SFN(short file name) entry is processed as follows.
2-a) When character-code that appears first is ≧0x80 ,It’s treated as the first byte of two byte character.
Byte data afterwards is treated as the second byte of two byte character-code, and treated by two
bytes as one character.
2-b) When the case that doesn't apply to 2-a) ,that is, the character-code appears first is installed within the
range of 0x00-0x7F(US-ASCII) One byte is treated as one character. '0x00' is added and enhanced to
Unicode.
Please confirm the specification of the FAT filesystem about details of LFN and SFN.
www.rohm.com
© 2012 ROHM Co., Ltd. All rights reserved.
TSZ22111・15・001
26/66
TSZ02201-0V2V0E600010-1-2
2012.07.12 Rev.001