Peripheral Simulation

For NXP (founded by Philips) 83/87C554 — I²C Interface

Simulation support for this peripheral or feature is comprised of:

• Dialog boxes which display and allow you to change peripheral configuration.
• VTREGs (Virtual Target Registers) which support I/O with the peripheral.

These simulation capabilities are described below.

I²C Interface Communication Dialog

The Controller Area Network (CAN) Controller Communication tab displays the CAN communication activity on the CAN bus. The Message number, States, Message Identifier, Message Direction, Channel, Data Length and Data content are displayed for each message. To clear the message display, double-click anywhere in the message display area.

I²C Interface Hardware Dialog

The I²C Hardware Interface dialog displays all configuration options for the on-chip I²C controller. You may interactively alter and view these options using the dialog controls.

I2C_CLK VTREG
Data Type: unsigned long

The I2C_CLK VTREG specifies the clock frequency (in Hz) to use in SLAVE mode. 100000 specifies 100KHz.

I2C_IN VTREG
Data Type: unsigned int

The I2C_IN VTREG contains data sent from an I2C peripherals to the simulated MCU.

• 0x0000-0x00FF: An address or data byte transfer.
• 0x0100: START byte. This initiates a SLAVE transmit or receive. The next byte sent is the address.
• 0xFF00: ACK.
• 0xFF01: NACK.
• 0xFFFF: IDLE or STOP condition.

I2C_OUT VTREG
Data Type: unsigned int

The I2C_OUT VTREG contains data sent from the simulated MCU to the I2C peripherals.

• 0x0000-0x00FF: An address or data byte transfer.
• 0x0100: START byte. This initiates a MASTER transmit or receive. The next byte sent is the address.
• 0xFF00: ACK.
• 0xFF01: NACK.
• 0xFFFF: IDLE or STOP condition.