CS49400 datasheet(73/100 Pages) CIRRUS

73 / 100 page

DSPC.

The

supported

messages

are

described in Table 16. This message tells

DSPC where to get the DSPAB image from.

Currently the C_MASTER_BOOT_FLASH

message is supported and allows booting from

external byte-wide flash or eprom.

3) If the initialization was successful DSPC sends

out the C_BOOT_START message and the

host must proceed to step 4. If initialization

fails the host must re-try steps 1 through 3 and

if failure is met again, the communication

timing and protocol should be inspected.

4) After

receiving

the

C_BOOT_START

message, the host must release control of the

communication interface and wait for INTREQ

to go low.

Note:

DSPC will autoboot DSPAB. After this

DSPC will release control of the communication

interface, but only when in SPI Master Boot

Mode.

5) The end of the .ULD file contains a three byte

checksum. If the checksum is good after the

download,

DSPC

will

send

C_BOOT_SUCCESS message to the host. If

the checksum was bad, DSPC responds with

the C_BOOT_ERROR_CHECKSUM message

message and waits for a hard reset.

6) After reading out the C_BOOT_SUCCESS

message, the host must send a second

C_MASTER_SOURCE_MODE boot message

to DSPC. This messages tells DSPC where the

to get image for DSPC.

7) If the initialization was successful DSPC sends

out the C_BOOT_START message and the

host must proceed to step 8. If initialization

fails the host must re-try step 6. If failure is met

again, the communication timing and protocol

should be inspected.

8) After

receiving

the

C_BOOT_START

message, the host must release control of the

communication interface and wait for INTREQ

to go low.

Note:

DSPC will autoboot DSPC. After this

DSPC will release control of the communication

interface, but only when in SPI Master Boot

Mode.

9) The end of the .ULD file contains a four byte

checksum. If the checksum is good after the

download,

DSPC

will

send

C_BOOT_SUCCESS message to the host. If

the checksum was bad, DSPC responds with

the C_BOOT_ERROR_CHECKSUM message

and waits for a hard reset.

10) After reading out the C_BOOT_SUCCESS

message,

the

host

must

send

the

C_SOFT_RESET message which will cause

the application code to reset and allow the

downloaded application to run.

11) If the soft reset was successful, DSPC sends out

a C_APP_START message the host can

proceed to step 12. If DSPC does not send an

the application start message, the host must re-

try the whole procedure again.

12) Next the host can send hardware and software

configuration messages for DSPC.

13) At this point the application code on DSPC is

running and the host needs to configure

DSPAB.

14) The host must read the AB_APP_START

message from DSPAB. If DSPAB does not

send an the application start message the host

must re-try the whole procedure again, starting

with step 1.

15) The host must send hardware and software

configuration messages for DSPAB, ending

with the kickstart message.

16) At this point the application code on DSPAB is

running.

Note:

Hardware configuration messages are

used to define the behavior of the DSP’s audio

ports. A more detailed description of the

different hardware configurations can be found

CS49400 датащи(PDF) 73 Page - Cirrus Logic

CS49400 датащи(HTML) 73 Page - Cirrus Logic

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100

датащи скачать

ссылки URL