29.01.2015 Views

Embedded Software for SoC - Grupo de Mecatrônica EESC/USP

Embedded Software for SoC - Grupo de Mecatrônica EESC/USP

Embedded Software for SoC - Grupo de Mecatrônica EESC/USP

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Evaluation of Applying SpecC to the Integrated Design Method 147<br />

As <strong>de</strong>scribed in [7], the interface on the software si<strong>de</strong> can be converted<br />

mechanically. For the interface on the hardware si<strong>de</strong>, mechanical conversion<br />

is possible by preparing a bus interface circuit <strong>for</strong> bus mo<strong>de</strong>ls. By preparing<br />

a channel library and an interface <strong>de</strong>scription <strong>for</strong> every channel inclu<strong>de</strong>d in<br />

library, the mechanical conversion can be ma<strong>de</strong> more efficient. Since we were<br />

able to show the mechanical conversion methods of SpecC <strong>de</strong>scription to softwares<br />

and interface, we conclu<strong>de</strong> that evaluation point (2) is satisfied.<br />

6. CHANGE OF PARTITION POINT<br />

The optimal partition point between a software and a hardware changes with<br />

the <strong>de</strong>mands and restrictions of a system. The advantage of the conversion<br />

from integrated <strong>de</strong>scription is that the partition point of the <strong>de</strong>vice and the<br />

<strong>de</strong>vice driver can be changed according to the need of the system. To be able<br />

to change the partition point, a single behavior <strong>de</strong>scription should be<br />

converted into both software and hardware.<br />

To evaluate point (3) <strong>de</strong>scribed in section 3, the partition point of the<br />

software and the hardware is changed from a byte channel to a PPP packet<br />

channel previous conversion. The difference between the byte channel conversion<br />

and the PPP packet channel conversion is that the <strong>de</strong>vice that receives<br />

the pointer has to take out the data from the memory using direct memory<br />

access (DMA) because the PPP packet channel only passes the pointer to the<br />

PPP packet.<br />

6.1. Device driver and interface<br />

For the SIO system, the objects of the <strong>de</strong>vice driver conversion are <strong>de</strong>scriptions<br />

of IP packet channels and PPP generation and analysis behaviors. As<br />

<strong>de</strong>scribed in section 5, the conversion can be done mechanically.<br />

The PPP packet channels can be mechanically converted to an interface<br />

using the method done with a byte channel. The functions of the channel <strong>for</strong><br />

PPP packet are equivalent to the functions of the byte channel. The only<br />

difference is that in the conversion of PPP packet channels, the type<br />

data_buffer is used so after the conversion the size of the <strong>de</strong>vice register<br />

used to hold the a data_buffer is different from that of the byte channel.<br />

6.2. Conversion of the <strong>de</strong>vice<br />

This section <strong>de</strong>scribes the conversion of the byte channel and the byte transmit<br />

behavior to the <strong>de</strong>vice. For <strong>de</strong>scription on the layer below the bit transmit/<br />

receive behavior, conversion is the same as <strong>de</strong>scribed in section 5. Since the<br />

PPP packet channel transmits and receives pointers to PPP packet, the byte<br />

transmit/receive behavior inclu<strong>de</strong>s functions to access memory. To convert<br />

memory access with pointers, the memory access is done using DMA. The

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!