SAP5SD-B-G1-R datasheet(25/67 Pages) RENESAS

25 / 67 page

SAP51 / SAP5S Datasheet

January 28, 2016

Logical

EEPROM

Address

Bit

Position

EEPROM Cell Content

Description

S_flag_5

Swap-flag 5

3 to 0

DI_S5 [3:0]

Data Input word 5 from Safety Code Table

S_flag_6

Swap-flag 6

3 to 0

DI_S6 [3:0]

Data Input word 6 from Safety Code Table

S_flag_7

Swap-flag 7

3 to 0

DI_S7 [3:0]

Data Input word 7 from Safety Code Table

Safety_Mode_Enable

If set, Safety Mode is enabled

Safety_Program_Mode_Disable

If set, Safety Area is protected against overwriting

Similar to the Firmware Area programming, Safety Area programming is intended to be used only during

production set-up of a slave component at the manufacturer’s site. Write access to the Safety Area of the

EEPROM is possible in the Safety Program Mode. It can be entered only if the Safety_Program_Mode_Disable

flag is not yet set to ‘1’ and if the slave address has been set to 0HEX. If the slave address equals 0HEX, the

reception of the Enter_Program_Mode_Safety (PRGM) call sets the SAP5 device into the Safety Program Mode.

It should be noted that no response is generated to the Enter_Program_Mode_Safety call (refer to the

AS-Interface Complete Specification).

In the Safety Program Mode, the Write_Parameter (WPAR) and Data_Exchange (DEXG) calls are used to

transfer data words to the EEPROM similar to the Firmware Area write procedure described in section 4.3.

However, the address bits A[4:0] of the master telegrams are used to address one of the memory locations of the

EEPROM (refer to Table 4.4). The information bits I[4:0] (normally used for output data) carry the data to be

stored.

Any WPAR or DEXG call initializes an autonomous write process within the SAP5. The status of the write process

can be monitored by evaluating the status register of the SAP5 as described in section 4.1. Since the SAP5 is still

in Safety Program Mode, the address within the Read_Status master call has the “don’t care” status. In order to

execute as many write procedures as desired, do not leave the Safety Program Mode until finished.

Note: The SAP5 will leave the Safety Program Mode and start its initialization procedure if it receives a

Reset_Slave (RES) master call to any desired slave address.

Any attempt to access one of the unavailable EEPROM address locations (0, 9 to 30) of the Safety Area via a

Write_Parameter (WPAR) or Data_Exchange (DEXG) command will be ignored.

There is no direct read access to the Safety Area data in Safety Program Mode.

After programming the Safety Area, an EEPROM verification procedure should be performed; i.e., by performing

one complete AS-i safety cycle (8 DEXG calls at intervals of at least 250µs) in Safety Mode operation.

SAP5SD-B-G1-R 数据表(PDF) 25 Page - Renesas Technology Corp

SAP5SD-B-G1-R 数据表(HTML) 25 Page - Renesas Technology Corp

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

数据表下载

链接网址

SAP5SD-B-G1-R 数据表(PDF) 25 Page - Renesas Technology Corp

SAP5SD-B-G1-R 数据表(HTML) 25 Page - Renesas Technology Corp

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

数据表 下载

链接网址

数据表下载