Explore chapters and articles related to this topic
Electronic applications and the Arduino
Published in Mike Tooley, Electronic Circuits, 2019
Note that the 0x prefix denotes a value expressed in hexadecimal (base 16) format. Because only eight bits are used byte data is limited in range. The minimum value that can be represented is 0 when all of the bits are 0 (hexadecimal 0x00) and the maximum value is 255 (hexadecimal 0xFF) when all of the bits are set to 1. Despite the restricted range, byte data can be useful in a variety of applications, particularly when dealing with the status of byte-wide (i.e. eight bit) input or output lines. For example: byte inputStatus = 0x00; // initialise input port status byte inputFailure = 0xFF; // all port lines have gone high
Robotic Arm Control
Published in Ferat Sahin, Pushkin Kachroo, Practical and Experimental Robotics, 2017
There are two communication protocols to control the robot using the serial port: instant control protocol and download protocol. In the instant control protocol, a control command (shown in Table 5.3) is sent to the servomotor controller through the serial port. The first byte is 255 (0xFF in hexadecimal form). The second byte is the target servomotor. The third byte is the value for the servomotor, which determines the angle of the motor. It takes values from 0 to 255 representing -45 degrees and 45 degrees, respectively. The value 127 represents the 0 degree angle.
Machine learning techniques to predict sensitive patterns to fault attack in the Java Card application
Published in Journal of Experimental & Theoretical Artificial Intelligence, 2018
Yahiaoui Chahrazed, Lanet Jean-Louis, Mezghiche Mohamed, Tamine Karim
To prevent a fault attack, we need to know what are its effects on smart cards. Blomer, Otto, and Seifert (2003) present a taxonomy of fault models in details. In our case, we choose the precise byte error model as the most realistic attack model. When an attacker physically injects energy in a memory cell to change its state and depending on the underlying technology, the memory physically takes the value 0x00 or 0xFF. If the memory cells are encrypted, the physical value becomes random according to the encryption algorithm. Thus, we assume that an attacker can:Make a fault injection at a precise clock cycle (he can target any operation he wants),Only set or reset a byte to 0x00 or to 0xFF up to the underlying technology, or he can change this byte to a random value beyond his control (random fault type),Target any memory cells (precise memory cell of a variable or register).Moreover, we have to distinguish the nature of the memory. We assume that an attacker targets only the EEPROM memory. Such an assumption is based on the fact that first ROM cell values can only be modified while the content is on the bus, which is a little bit more complicated. The RAM memory is much more difficult to target. The position of a data in the RAM is located in the stack which is a changing data structure.