AD-SM2400AP02A-PWRLN. Application Note. SM2400 Bootloader User Guide. Overview
|
|
- Christina Day
- 6 years ago
- Views:
Transcription
1 AD-SM2400AP02A-PWRLN Application Note Communication Technology by: Semitech Semiconductor Revision 1.0 August 2016 Overview This application note describes the SM2400 Bootloader modes, interface, and protocols, and includes programming examples.
2 Table of Contents 1. Introduction Boot Mode Host Interface Application Overview Programming an SPI flash from UART Downloading code images to internal memory from UART Boot Sector and Firmware Image Boot Sector Format Firmware image format In-system programming Bootloader host interface protocol and response format Host s Code examples BIT CRC example (implemented in C) Bootloader command transmit example (implemented in C) Glossary Contact Information Revision Information
3 1. Introduction The SM2400 bootloader is executed when the SM2400 modem comes out of reset. Based on the SM2400 modem mode pins (described in Section 2.), the bootloader can perform the following functions: Direct execution toward a flash memory device or external SRAM Read and write data to the external flash Read and write data to internal and external memory Enter debugger mode 3
4 2. Boot Mode The boot mode is determined by the state of the SM2400 mode pins (MODE0, MODE1 and MODE2) immediately after reset. The values are latched when reset is de-activated, and the pins can be used as general-purpose IOs after the boot sequence. The mode combinations are shown in Table 2-1. Table 2-1. Boot Modes Boot Mode MODE[2:0] Pins Boot from SPI 000 Host Interface on SPI 001 Host Interface on UART 010 Boot from external memory 011 Reserved 100 Reserved 101 DLL and PHY debug mode 110 DLL debug mode 111 In the Boot from SPI mode, the bootloader will look for a valid firmware image in the external flash. The format of the firmware image is detailed in Section 4.2. If the boot mode is not valid or booting from an image fails, the device will time out after 10 seconds and reset. This is to prevent the case where the boot image fails due to a spurious error on the read values, so a reset and new read should allow the system to recover. In the host interface modes, an external host can send commands to the device to access internal and external memory, including writing to an external flash memory. The framing formats are described in Section 6.1, and the available commands in Section 6.2. The debug modes are not described in this document. 4
5 3. Host Interface Application Overview This section contains overviews of example applications of the host interface. 3.1 Programming an SPI flash from UART When programming an SPI flash device from the UART, the SPI interface to the flash device is configured as a passthrough from the UART. These steps should be followed: 1. Perform a reset with the SM2400 mode pins set to Set UART bit rate to 2400 bps. 3. Send UART configuration command to configure the SM2400 UART to higher bit rate (using the Configure UART0 command described in Section 6.2.4). 4. Change the local UART bit rate to the higher rate. 5. Configure the SPI interface (using the Configure SPI1 Pass Through command described in Section 6.2.7). 6. Send commands to SPI flash (using the SPI1 command described in Section 6.1.2). 7. Perform a reset with the SM2400 mode pins set to 000 (to boot from flash). 3.2 Downloading code images to internal memory from UART When downloading firmware images to the internal memory, the bootloader accepts blocks of data and stores them in memory. Once all the memory is populated, an Execute command is issued to start the execution. These steps should be followed: 1. Perform a reset with the SM2400 mode pins set to Set UART bit rate to 2400 bps. 3. Send UART configuration command to configure the SM2400 UART to higher bit rate (using the Configure UART0 command described in Section 6.2.4). 4. Change the local UART bit rate to the higher rate. 5. Parse the *.bundle file (see Section 4.): a. Locate the boot sector at the beginning of the file, which includes the location of the firmware image. b. Parse the image header to get the execution start addresses and the CRC. c. Parse the address table. d. Locate the memory blocks within the *.bundle file. 6. Write the memory blocks into SM2400 internal memory (using the Write command described in Section 6.2.5). 7. Calculate the 32-bit CRC using the first 24 bytes of the image header and the memory blocks (not the address table). It should match the 1-s complement of the CRC in the image header. 8. Send the DLL and PHY start addresses to the SM2400 modem and start the execution (using the Execute command described in Section ). 5
6 4. Boot Sector and Firmware Image The boot sector and the firmware image contain all the information and the data necessary for the bootloader or a host to download the firmware image to be executed. Those components should either reside on an external SPI flash to be read by the bootloader or provided to the host to boot the SM2400 from the host interface. The boot sector and a respective image are packaged in a *.bundle file that can be read by the host or programmed onto an SPI flash. The following sections describe in detail the format of the different components of a *.bundle file." 4.1 Boot Sector Format The purpose of the Boot Sector is to either specify a location of the firmware to be loaded into the PHY and DLL, or to specify details of a host interface for the receipt of subsequent commands Boot Sector characteristics The Boot Sector is 32 bytes long, with the following fields in the order shown below: Magic number: 4 bytes, 0xb00753c7 (big-endian) Identifies this sector as a boot sector CRC-8 of Boot Sector, excluding Magic number, 1 byte Location of Next Boot Sector: The upper 3 bits determine where the next candidate boot sector is. The offset between the two candidate boot sectors is given by 4 KB multiplied by 2 to the power of this value. The lower 5 bits indicate the Boot device. These should be set to 4 for SPI1 SS0. Device configuration: 6 bytes (see below). Image Sequence number,1 byte: this is set to 0 for the first boot sector, to 1 for the second Reserved field of 7 bytes. Device Tag: 8 bytes, general information to be written to the top of DRAM on the DLL. Location of firmware image: 4 bytes, an absolute address into the boot device above Device configuration bytes Below are details of device configuration bytes (big-endian) for the SPI flash (SPI1 register): Bits 31-29: Number of dummy bytes after command Bits 28-24: Max page size for read. Page size is two to the power of this value. If 0, only single byte reads. Bits 23-16: Read command Bit 15: Clock polarity (CPOL) Bit 14: Clock phase (CPHA) Bits 13-12: Address width minus 2. So 0 means 2 byte address;1 means 3-byte address. Only 2- and 3-byte addresses are valid. Bit 11: Set to 1. Bits 10-0: The SPI frequency clock rate divisor (divisor = 6 x 107/ SPI CLK). MAX SPI CLK = 7.5MHz. 6
7 4.2 Firmware image format The firmware image, which in many cases would follow the boot sector, is composed of the Image Header and the binary code. These are needed when booting from SPI or external memory Image Header The Image Header consists of the following: Firmware ID: 4 bytes; this is for product differentiation, since the bootloader will only load firmware for a specific ID. By default the Firmware ID is set to 0xb , big-endian. The 0xb024 is for SM2400; the last two bytes may be used for differentiation. ROM major rev: 1 byte - value 0x05 ROM minor rev: 1 byte - value 0x00 User ID: 2 bytes; this is for customized user purposes. For example, this field can be used if an application boots a specific firmware from a list of bootable images residing in the SPI flash. DLL Execution start address: 4 bytes, big-endian PHY Execution start address: 4 bytes, big-endian DLL VECBASE address: 4 bytes, big-endian PHY VECBASE address: 4 bytes, big-endian CRC-32 of the Image Header and the loaded firmware sections (calculated in order as specified in the ROM store table): 4 bytes; MSB is highest coefficient. The generating polynomial is 0x104C11DB7; the least significant bit is shifted in first. The binary code, starting with the ROM store table. Note: The DLL and PHY execution start addresses must be aligned to 4-byte boundaries. Note: The DLL and PHY VECBASE addresses must be aligned to 1024-byte boundaries Address Table The image header is followed by an address table with the following three 4-byte big-endian addresses: Target base address in SM2400 memory Target top address in SM2400 memory Location in firmware image relative to the Location of Firmware Image address (see Section 4.1.1). The last entry in the address table is followed by 12 bytes of zeroes Code segments The code segments are located above the address table without any specific framing. Although each code segment starts at a 4-byte boundary, some code segments may have a length that is not a multiple of 4 bytes. 7
8 5. In-system programming The bootloader supports in-system programming of external code memories (SPI EEPROM, SPI flash, external flash, or external RAM) by using the host interface. This feature can be used at board assembly time to program the latest firmware and boot sector during final test. 8
9 6. Bootloader host interface protocol 6.1 and response format UART s and responses through the Host Interface UART0 are formatted as described below. The default bit rate of the UART is 2400 bps. It can be changed using the Configure UART0 command described in Section from Host: Start of Frame /Length (MS bits) Length (LS bits) (optional) CRC-16 2 bytes 1 byte 1 byte Variable bytes 2 bytes Response from SM2400: /Length (MS bits) Length (LS bits) (optional) CRC-16 1 byte 1 byte Variable bytes 2 bytes Key definitions and comments: SPI Start of Frame is a fixed two-byte code of 0x9B 0xFE. is the command code. Length is the number of bytes in the field. The maximum length is 72 bytes. Return status is a one-byte code that indicates the result of the command: 0xFE - CRC Error, contains expected CRC Others - Detailed under each command bytes contain the value of parameters (for a command), or return values (for a response); this section is optional depending on the command. CRC-16 is a two-byte CRC calculated for all the information in the command except for the Start of Frame bytes. The CRC coefficients are x 16 + x 12 + x 5 + 1; MSB is the highest coefficient. 0x9B (ASCII ESC) is used as an escape character to precede control characters. Thus the literal 0x9B itself, if it occurs in data, needs to be represented by an escape sequence, which is 0x9B 0x64 (0x64 being the inverse of 0x9B). Note: Escape processing is done after the application of CRC-16. That is, CRC-16 is applied to the raw unescaped data, and then the final binary string is escape stuffed where required, including the two-byte CRC-16 itself. SPI is similar to UART, but the command and response are contained in a single transaction with wait states inserted in between. The wait state is indicated by returning bytes of 0xFF (which would be an invalid return status and length combination). Framing and escape stuffing in SPI is the same as for UART. 9
10 MOSI: Start of Frame Length (optional) CRC-16 Wait States Dummy bytes 2 bytes 1 byte 1 byte Variable bytes 2 bytes Variable bytes Variable MISO: ( and Wait States) Length (optional) CRC-16 (as above) 1 byte 1 byte Variable bytes 2 bytes 6.2 Host s In order to use the SPI master and/or the external memory, they must be configured first using respective command(s). Until configured properly, they will remain disabled. Because of this, external memory must be enabled before it can be accessed at any stage (read, write, boot image commands) x00 - Firmware ID As defined under Boot Sector Format (Section 4.1). 0x00 4 bytes (Currently, 0xb SM2400) x01 - Obsolete ROM rev Return the ROM version for which any earlier firmware versions are obsolete and will not be loaded. 0x01 0x00 - success Obsolete ROM Major number (1 byte) Obsolete ROM Minor number (1 byte) x02 - ROM rev Return the ROM revision number as defined under Boot Sector Format (Section 4.1). 0x02 Major number (1 byte) Minor number (1 byte) 10
11 x03 - Configure UART0 Configure the UART0 Host interface. 0x03 2 bytes (big-endian) Bit 15: Hardware handshaking OFF (0) or ON (1) Bits 14-0: Baud rate divisor to generate the baud clock (16X baud rate) divisor [divisor = 6 x (Baud x 8) / Baud x16] 0x01 - Invalid configuration x04 - Write Write to 32-bit aligned address specified. 0x04 Address (4 bytes, 32-bit-aligned, big-endian) to be written (variable length, multiple of 4 bytes, up to max command length) 0x01 - Error x05 - Read Read from 32-bit aligned address specified. 0x05 Address (4 bytes, 32-bit aligned big-endian) Number of bytes to read, number being a multiple of 4 (1 byte) x01 - Error Read (variable length) x06 - SPI1 pass through Configure SPI1 pass through. 0x06 Set Slave number (1 byte) Clock Mode (1 byte) Bit 7: Clock Polarity (CPOL) Bit 6: Clock Phase (CPHA) Clock divisor (2 bytes) Bit 15-0: Clock rate divisor [divisor = 6 x 10 7 / SPI CLK] MAX SPI CLK = 7.5MHz 11
12 x07 - SPI1 command Execute a command through SPI1. (bytes) 0x07 Length of Read phase (2 bytes, big-endian) bytes (variable length) from Read phase (variable length) x08 - Configure Ext Mem Configure the external memory CS0 interface. (bytes) 0x08 Mem Type (1 byte) Bit 6: SRAM (0) or Flash (1) Static Timing Register Value register as defined in synopsis designware static memory controller databook, byte-swapped (4 bytes) FLASH Timing register as defined in synopsis designware static memory controller databook, byteswapped (2 bytes) 0x01 - Invalid configuration x09 - Execute Pass execution to the firmware at given address - that, is jump to address. Note: The dynamic vectors are not changed before jumping to the addresses given. They will be set to ROM addresses (because this is what the bootloader uses). It is assumed that the vectors are set by the user program. (bytes) (bytes) 0x09 DLL Address to jump to (4 bytes, big-endian) PHY Address to jump to (4 bytes, big-endian) 0x01 - Error 12
13 x0A - CRC32 Return the CRC-32 of a given block of data. (bytes) 0x0A Initial CRC (4 bytes) Start Address of block (4 bytes, big-endian) Block size (4 bytes, big-endian) 0x01 - Error CRC-32 (4 bytes) x0B - BOOT_IMAGE: Boot from image specified. Note: The dynamic vectors are changed based on the values in the firmware image header before jumping to execution. (bytes) 0x0B Boot device number as defined in the Boot Sector (1 byte) Device Config as defined in the Boot Sector (6 bytes, big-endian) Location of image to boot from in the device i.e the Image Address (4 bytes, big-endian) 0x01 - Error x0C - RESET Reset the DLL processor. Note: This will not return and will cause both the DLL and PHY to reset. 0x0C (bytes) none 0x01 - Error 13
14 7. Code examples This section contains code examples that may be useful in communicating with the bootloader BIT CRC example (implemented in C) // polynomial: 0x104C11DB7 static uint32_t crc32_table[] = 0x , 0x1db71064, 0x3b6e20c8, 0x26d930ac, 0x76dc4190, 0x6b6b51f4, 0x4db26158, 0x c, 0xedb88320, 0xf00f9344, 0xd6d6a3e8, 0xcb61b38c, 0x9b64c2b0, 0x86d3d2d4, 0xa00ae278, 0xbdbdf21c ; // CRC calculation uint32_t crc32_calc(uint32_t crc, uint8_t *data, uint32_t ix, uint32_t len) uint32_t k, m, d; for (k = 0; k < len; k++) d = (uint32_t)data[ix + k] ^ crc; m = crc32_table[d & 0x0f]; d >>= 4; d ^= m; crc >>= 8; crc ^= m >> 4; crc ^= crc32_table[d & 0x0f]; return crc; 7.2 Bootloader command transmit example (implemented in C) uint32_t ccitt_crc16_table[] = 0x0000, 0x1021, 0x2042, 0x3063, 0x4084, 0x50a5, 0x60c6, 0x70e7, 0x8108, 0x9129, 0xa14a, 0xb16b, 0xc18c, 0xd1ad, 0xe1ce, 0xf1ef, 0x1231, 0x0210, 0x3273, 0x2252, 0x52b5, 0x4294, 0x72f7, 0x62d6, 0x9339, 0x8318, 0xb37b, 0xa35a, 0xd3bd, 0xc39c, 0xf3ff, 0xe3de, 0x2462, 0x3443, 0x0420, 0x1401, 0x64e6, 0x74c7, 0x44a4, 0x5485, 0xa56a, 0xb54b, 0x8528, 0x9509, 0xe5ee, 0xf5cf, 0xc5ac, 0xd58d, 0x3653, 0x2672, 0x1611, 0x0630, 0x76d7, 0x66f6, 0x5695, 0x46b4, 0xb75b, 0xa77a, 0x9719, 0x8738, 0xf7df, 0xe7fe, 0xd79d, 0xc7bc, 0x48c4, 0x58e5, 0x6886, 0x78a7, 0x0840, 0x1861, 0x2802, 0x3823, 0xc9cc, 0xd9ed, 0xe98e, 0xf9af, 0x8948, 0x9969, 0xa90a, 0xb92b, 0x5af5, 0x4ad4, 0x7ab7, 0x6a96, 0x1a71, 0x0a50, 0x3a33, 0x2a12, 0xdbfd, 0xcbdc, 0xfbbf, 0xeb9e, 0x9b79, 0x8b58, 0xbb3b, 0xab1a, 0x6ca6, 0x7c87, 0x4ce4, 0x5cc5, 0x2c22, 0x3c03, 0x0c60, 0x1c41, 0xedae, 0xfd8f, 0xcdec, 0xddcd, 0xad2a, 0xbd0b, 0x8d68, 0x9d49, 14
15 0x7e97, 0x6eb6, 0x5ed5, 0x4ef4, 0x3e13, 0x2e32, 0x1e51, 0x0e70, 0xff9f, 0xefbe, 0xdfdd, 0xcffc, 0xbf1b, 0xaf3a, 0x9f59, 0x8f78, 0x9188, 0x81a9, 0xb1ca, 0xa1eb, 0xd10c, 0xc12d, 0xf14e, 0xe16f, 0x1080, 0x00a1, 0x30c2, 0x20e3, 0x5004, 0x4025, 0x7046, 0x6067, 0x83b9, 0x9398, 0xa3fb, 0xb3da, 0xc33d, 0xd31c, 0xe37f, 0xf35e, 0x02b1, 0x1290, 0x22f3, 0x32d2, 0x4235, 0x5214, 0x6277, 0x7256, 0xb5ea, 0xa5cb, 0x95a8, 0x8589, 0xf56e, 0xe54f, 0xd52c, 0xc50d, 0x34e2, 0x24c3, 0x14a0, 0x0481, 0x7466, 0x6447, 0x5424, 0x4405, 0xa7db, 0xb7fa, 0x8799, 0x97b8, 0xe75f, 0xf77e, 0xc71d, 0xd73c, 0x26d3, 0x36f2, 0x0691, 0x16b0, 0x6657, 0x7676, 0x4615, 0x5634, 0xd94c, 0xc96d, 0xf90e, 0xe92f, 0x99c8, 0x89e9, 0xb98a, 0xa9ab, 0x5844, 0x4865, 0x7806, 0x6827, 0x18c0, 0x08e1, 0x3882, 0x28a3, 0xcb7d, 0xdb5c, 0xeb3f, 0xfb1e, 0x8bf9, 0x9bd8, 0xabbb, 0xbb9a, 0x4a75, 0x5a54, 0x6a37, 0x7a16, 0x0af1, 0x1ad0, 0x2ab3, 0x3a92, 0xfd2e, 0xed0f, 0xdd6c, 0xcd4d, 0xbdaa, 0xad8b, 0x9de8, 0x8dc9, 0x7c26, 0x6c07, 0x5c64, 0x4c45, 0x3ca2, 0x2c83, 0x1ce0, 0x0cc1, 0xef1f, 0xff3e, 0xcf5d, 0xdf7c, 0xaf9b, 0xbfba, 0x8fd9, 0x9ff8, 0x6e17, 0x7e36, 0x4e55, 0x5e74, 0x2e93, 0x3eb2, 0x0ed1, 0x1ef0 ; int32_t add_byte(uint8_t *buf, int32_t *k, int32_t *crc, uint8_t byt) int32_t nb = 1; buf[(*k)++] = byt; if (byt == BL_ESC) buf[(*k)++] = BL_IESC; nb = 2; *crc = ccitt_crc16_table[((*crc) >> 8 ^ (uint32_t)byt) & 0xff] ^ ((*crc) << 8); return nb; // Encode bootloader packet int32_t bl_encode(uint8_t *buf, uint8_t *inp, int32_t len, uint8_t cmd) int32_t i, k, crc, dcrc; crc = 0; k = 0; buf[k++] = BL_ESC; buf[k++] = BL_ESC2; add_byte(buf, &k, &crc, cmd); add_byte(buf, &k, &crc, len); for (i = 0; i < len; i++) add_byte(buf, &k, &crc, inp[i]); dcrc = 0; add_byte(buf, &k, &dcrc, (uint8_t)(crc >> 8)); add_byte(buf, &k, &dcrc, (uint8_t)(crc >> 0)); return k; // Decode response from SPI - removing escape sequences and checking CRC 15
16 // Return values: // >= 0: length of response // -1: Incomplete sequence // -2: Invalid length // -3: Nonzero status // -4: Invalid escape sequence // int32_t bl_decode(uint8_t *dbuf, uint8_t *buf, int32_t len) uint16_t crc, tcrc; int32_t err; uint8_t stat; int32_t plen, k, n; if (len < 2) return -1; stat = buf[0]; plen = buf[1]; if (stat!= 0x00) return -3; if (plen > 64) return -2; if (plen > len) return -1; // too short, need more data crc = 0; crc = ccitt_crc16_table[(crc >> 8 ^ (uint32_t)buf[0]) & 0xff] ^ (crc << 8); crc = ccitt_crc16_table[(crc >> 8 ^ (uint32_t)buf[1]) & 0xff] ^ (crc << 8); err = 0; for (k = 0, n = 2; (k < plen + 2) && (n < len); k++, n++) dbuf[k] = buf[n]; if (buf[n] == BL_ESC) n++; if (n >= len) return -1; if (buf[n]!= BL_IESC) return -4; if (k < plen) crc = ccitt_crc16_table[(crc >> 8 ^ (uint32_t)dbuf[k]) & 0xff] ^ (crc << 8); if ((n < len) (k < plen + 2)) return -1; // too short tcrc = ((uint32_t)dbuf[k - 2] << 8) (uint32_t)dbuf[k - 1]; if (tcrc!= crc) err = 1; if (err!= 0) return -2; return plen; 16
17 // Read bootloader UART int32_t bl_read(void *serialhandle, uint8_t *decbuf, int32_t maxlen) int32_t k, res; k = uart_read(serialhandle, rxbuf + rbp, BLRXBUF_SIZE - rbp); if (k == 0) return -1; rbp += k; res = bl_decode(decbuf, rxbuf, rbp); if ((res == -1) (res == -4)) // too short, will come back here return -1; rbp = 0; if ((res == -2) (res == -3)) // outright error return -2; return res; // Send a command to SPI int32_t sendhost(void *serialhandle, uint8_t *response, int32_t maxrlen, uint8_t *request, int32_t len, uint8_t command) int32_t elen, rlen; int32_t timeout; uint8_t pkt[160]; elen = bl_encode(pkt, request, len, command); uart_write(serialhandle, pkt, elen); timeout = 100; while (timeout-- > 0) rlen = bl_read(serialhandle, response, maxrlen); if (rlen >= 0) return rlen; sleep(10); return -1; // timeout 17
18 8. Glossary Table 8-1. Glossary of terms Term Boot Loader DLL DRAM ( RAM) DROM ( ROM) External Code External Memory External RAM (EXTRAM) External Flash (EXTFLASH) Firmware Host Hostless Internal Code IRAM (Instruction RAM) IROM (Instruction ROM) Local Memory OCD PHY SROM (System ROM) Target Device Definition Application that resides in on-die non-volatile instruction memory. Sets up system peripherals and loads a firmware image. -link layer CPU Processor Local Memory (read/write) Processor Local Memory (read only) ROM contents Refers to code that does not reside in on-die ROM and is loaded from external source such as SPI Memory or the host interface. Lower performance memory that is off-die. Accessed via a memory controller that is interfaced to the system bus. External asynchronous RAM, interfaced via the external memory controller. Can be populated on EXTMEM_CEN0b or EXTMEM_CEN1b External parallel flash or OTP memory. Can be populated on EXTMEM_CEN0b or EXTMEM_CEN1b See External Code in this table. The external processor or system that implements the OSI application layer and interfaces to the SM2400 device to utilize the communications capabilities. An SM2400-based system that does not include a host processor. In this case the OSI application is executed in the DLL processor. Refers to code that does reside in on-die ROM. Includes the bootloader and library code. Volatile local instruction memory. Local non-volatile instruction memory. IRAM, IROM, DRAM or DROM of relevant processor. On-Chip Debug Physical layer CPU ROM interfaced to the system bus. Can contain executable code or read-only data. A type of system memory The device that is to be programmed during in-system programming. This could be an attached serial memory or parallel memory. 18
19 9. Contact Information For more information regarding the SM2400EVK1 including application notes, product samples, demonstration modules, pricing and ordering please contact: Adesto Technologies Communication technology by: Semitech Semiconductor 10. Revision Information Table Revision history Version Description Date 1.0 First publication 8/2/
20 Corporate Office California USA Adesto Headquarters 3600 Peterson Way Santa Clara, CA Phone: (+1) Adesto Technologies. All rights reserved. / Rev.: PB2480A PWRLN 5/2016 Disclaimer: Adesto Technologies Corporation makes no warranty for the use of its products, other than those expressly contained in the Company's standard warranty which is detailed in Adesto's Terms and Conditions located on the Company's web site. The Company assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without notice, and does not make any commitment to update the information contained herein. No licenses to patents or other intellectual property of Adesto are granted by the Company in connection with the sale of Adesto products, expressly or by implication. Adesto's products are not authorized for use as critical components in life support devices or systems.
PLC Lite Host Message Protocol Specification
PLC Lite Host Message Protocol Specification Version 0.6 Oct. 20, 2014 Copyright Texas Instruments Incorporated, 2009-2014 The information and/or drawings set forth in this document and all rights in and
More informationSXH Protocol by Spinel Version 3.0 Date:
SXH Protocol by Spinel Version 3.0 Date:.8 Revision History Vision Date Description V.0 V.0 V3.0 September, 6 December, 6 April, 8 Initial release Added LED control, OSD, Cmd 0x30 Added all ratio image
More informationUsing the USB and Serial Interfaces
Using the USB and Serial Interfaces PulsON 300 and 400 Series TIME DOMAIN Cummings Research Park 4955 Corporate Drive Suite 101 Huntsville, AL 35805 USA http://www.timedomain.com Tel: +1 256.922.9229 +1
More informationFlexi Soft T E L E G R A M M L I S T I N G
T E L E G R A M M L I S T I N G This document is protected by the law of copyright, whereby all rights established therein remain with the company SICK AG. Reproduction of this document or parts of this
More informationInterface Control Document
Interface Control Document CR8200 Engine-based products D026166 CR8200 Interface Control Document ICD.docx Page 1 of 14 TABLE OF CONTENTS 1 Scope... 3 2 Communication Medium... 3 3 Reader to Host Communication...
More informationBC3G-US-SMA API. Rev 2.0
BC3G-US-SMA API Rev 2.0 28/10/2015 Table of Contents Table of Contents... 2 1. Product revision history... 4 2. How to use this document... 4 3. Serial Protocol Definition... 5 3.1. Configuration... 5
More informationRFID B1 Module User Manual
RFID B1 Module User Manual V1.202 Table of Contents 1 Introduction... 6 1.1 Device Overview... 6 1.2 Pinout... 7 1.3 Application... 8 2 Electrical Characteristics... 9 2.1 Test Conditions... 9 2.2 Absolute
More informationRFID B1 Module User Manual V2.2 16/01/2018
RFID B1 Module User Manual V2.2 16/01/2018 Table of Contents 1 Introduction... 6 1.1 Device Overview... 6 1.2 Pinout... 7 1.3 Application... 8 2 Electrical Characteristics... 9 2.1 Test Conditions... 9
More informationInstallation, operation and maintenance manual
Read this manual before installing, operating or maintaining this actuator. Failure to follow safety precautions and instructions could cause actuator failure and result in serious injury, death or property
More informationThe Cuttle Cart 3. The Intellivision Customizable Menu Cartridge. from. Chad Schell of Schell s Electronics. Copyright 2007 Schell s Electronics
The Cuttle Cart 3 The Intellivision Customizable Menu Cartridge from Chad Schell of Schell s Electronics Copyright 2007 Schell s Electronics Setting up the MicroSD Card To use the Cuttle Cart 3 (CC3) to
More informationWTS family of Tactile Sensor Modules - Command Set Reference Manual - Firmware Version March 2013
WTS family of Tactile Sensor Modules - Command Set Reference Manual - Firmware Version 1.2.0 March 2013 Contents 1 Introduction... 4 1.1 Data Acquisition... 4 1.2 Sensor Cell Numbers... 5 1.3 Connecting
More informationRS232C Serial Interface for Pirani Diaphragm and Pirani Standard Gauges. Caution. binary 8 data bits 1 stop bit no parity bit no handshake
General Information The Serial Interface allows the communication of the digital Agilent Pirani Capacitance Diaphragm Gauges (PCG-750, PCG-752) and the digital Agilent Pirani Standard Gauges (PVG-550,
More informationWSG Command Set Reference Manual. Firmware Version July 2011
WSG Command Set Reference Manual Firmware Version 2.1.0 July 2011 Contents 1 Introduction... 4 1.1 General Communication Protocol... 4 1.2 Command Acknowledge from the WSG... 6 1.3 Asynchronous Commands...
More informationDiagnostic Port Serial Interface for Capacitance Diaphragm Gauges
Communication Protocol Diagnostic Port Serial Interface for Capacitance Diaphragm Gauges CDG025D-X3 4-20 ma Current Loop Stripe CDG045Dhs Stripe CDG100Dhs tira84e1 (2017-05) 1 General Information The Diagnostic
More informationRS232C / RS485C Serial Interface for Cold Cathode and Cold Cathode Pirani Gauges
Communication Protocol RS232C / RS485C Serial Interface for Cold Cathode and Cold Cathode Pirani Gauges MAG500, MAG504 MPG500, MPG504 tira83e1-a (2017-06) 1 General Information The Serial Interface allows
More informationRS232C / RS485C Serial Interface for Pirani Capacitance Diaphragm and Pirani Standard Gauges
Communication Protocol RS232C / RS485C Serial Interface for Pirani Capacitance Diaphragm and Pirani Standard Gauges PCG550, PCG552, PCG554 PSG550, PSG552, PSG554 RS485C RS232C tira59e1-a (2017-04) 1 General
More informationHeat meter PolluStat M-bus communication protocol description
Heat meter PolluStat M-bus communication protocol description 1 1. General structure of protocol 1.1. General features of protocol Meter uses a M-bus protocol. Default baud rate: 2400 bps, Even, 1 Stop.
More informationCTT MODBUS-RTU COMMUNICATION PROTOCOL TEMPERATURE MONITOR DEVICE
INSTRUCTION MANUAL IM149-U v0.92 CTT MODBUS-RTU COMMUNICATION PROTOCOL TEMPERATURE MONITOR DEVICE Firmware version: v3.0 or higher MODBUS PROTOCOL Modbus is a master-slave communication protocol able to
More informationHDLC BCC 15.1 Data Link Protocol Description
Data Link Protocol Description by Daniel L. Henry Revision 1.1 October 9, 2011 Copyright 2000-2011 by Daniel L. Henry Revision History Rev. Date Changed By Reason for Change 1.0 5/9/03 Dan L. Henry Made
More informationTBS Unify Pro / SmartAudio
TBS Unify Pro / SmartAudio 02.12..2017 Revision 08 SmartAudio uses single wire half duplex communication based on UART. In Idle mode both host and VTX define the SmartAudio pin as input. If the host want
More informationKeywords: CRC, CRC-7, cyclic redundancy check, industrial output, PLC, programmable logic controller, C code, CRC generation, microprocessor, switch
Keywords: CRC, CRC-7, cyclic redundancy check, industrial output, PLC, programmable logic controller, C code, CRC generation, microprocessor, switch APPLICATION NOTE 6002 CRC PROGRAMMING FOR THE MAX14900E
More informationHighlights. FP51 (FPGA based 1T 8051 core)
Copyright 2017 PulseRain Technology, LLC. FP51 (FPGA based 1T 8051 core) 10555 Scripps Trl, San Diego, CA 92131 858-877-3485 858-408-9550 http://www.pulserain.com Highlights 1T 8051 Core Intel MCS-51 Compatible
More informationGNetPlus Communication Protocol
Basic Package (BINARY VERSION) Master Query Package (HOST) Field Header Address Query Function Data length DATA BYTES Error Check Desc SOH 0~255 0~255 0~255 CRC16_Low CRC16_Hi Size 1 BYTE 1 BYTE 1 BYTE
More informationUM2330 User manual. ST8500 boot. Introduction
UM30 User manual ST8500 boot Introduction This user manual describes ST8500 bootloader functionalities and operations to be done for a correct device boot and the firmware images download. The following
More informationMCW Application Notes 24 th February 2017
MCW Application Notes 24 th February 2017 www.motorcontrolwarehouse.co.uk Document number MCW-HEDY-001 Revision 0.1 Author Gareth Lloyd Product HEDY HD700 Title Summary HEDY HD700 Modbus Serial Communications
More informationimetos LoRa Data payload structure
imetos LoRa Data payload structure Pessl Instruments, GmbH Version 1.0, 06-2018 Content 1. SCOPE OF THIS DOCUMENT... 2 2. PARSING THE DATA FROM THE PAYLOAD VERSUS API DATA ACCESS... 3 3. IMETOS LORA FIRMWARE
More informationMTR-4. C8 Command to MODBUS Bridge User Manual F-1, No. 631, Chung Der Road, Sec 1, Taichung Taiwan.
MTR-4 C8 Command to MODBUS Bridge User Manual 404 19F-1, No. 631, Chung Der Road, Sec 1, Taichung Taiwan. TEL:886-4-2238-0698 FAX:886-4-2238-0891 Web Site:http://www.monicon.com.tw E-mail: sales@monicon.com.tw
More informationApplication Note: JN-AN-1003 JN51xx Boot Loader Operation
Application Note: JN-AN-1003 JN51xx Boot Loader Operation This Application Note describes the functionality of the boot loaders for the NXP, JN514x and wireless microcontrollers, covering the following
More informationInput Channels: 4 differential or four single-ended. Address / Baud rate / range configurable by the user
DAM-Series User Manual Amazing Electronic (HK) Limited User s Manual Overview: DAM module is a new generation data acquisition and control system based on modular embedded systems. Adopting standard DIN35
More informationTechnical Specification. Third Party Control Protocol. AV Revolution
Technical Specification Third Party Control Protocol AV Revolution Document AM-TS-120308 Version 1.0 Page 1 of 31 DOCUMENT DETAILS Document Title: Technical Specification, Third Party Control Protocol,
More informationDMTME Multimeters. Communication protocol. Technical specification V1.2 ABB
DMTME Multimeters Communication protocol ABB 1 Setting up DMTME serial communication.3 1.1 Serial network ID programming...3 1.2 RS-485 communication interface...3 1.3 Serial line connection...3 2 Communication
More informationvariable 1. Start of Packet - is used to provide synchronization when parsing packets. Always 0xFC
DreamScreen V2 WiFi UDP Protocol Rev 2 The DreamScreen-WiFi platform uses UDP unicasting and broadcasting over the WLAN to provide communication. Port 8888 is used for both sending and receiving. The DreamScreen
More informationvariable 1. Start of Packet - is used to provide synchronization when parsing packets. Always 0xFC
DreamScreen V2 WiFi UDP Protocol The DreamScreen-WiFi platform uses UDP unicasting and broadcasting over the WLAN to provide communication. Port 8888 is used for both sending and receiving. The DreamScreen
More informationID: Sample Name: Q3dY56x3hp Cookbook: defaultlinuxfilecookbook.jbs Time: 04:08:56 Date: 21/08/2018 Version:
ID: 73304 Sample : Q3dY56x3hp Cookbook: defaultlinuxfilecookbook.jbs Time: 04:08:56 Date: 21/08/2018 Version: 23.0.0 Table of Contents Table of Contents Analysis Report Overview General Information Detection
More informationModbus Protocol Guide for ZP2 Series Control Panels
Modbus Protocol Guide for ZP2 Series Control Panels P/N 00-3243-505-2603-01 ISS 14DEC15 Copyright Trademarks and patents Manufacturer Version REV 01 Certification 2015 UTC Fire & Security. All rights reserved.
More informationRS-232 Control of the Advantage EQ281/8, EQ282/8 and Advantage SMS200
RS-232 Control of the Advantage EQ281/8, EQ282/8 and Advantage SMS200 Biamp Systems, 14130 N.W. Science Park, Portland, Oregon 97229 U.S.A. (503) 641-7287 an affiliate of Rauland-Borg Corp. Introduction
More informationSPARC INTERNATIONAL. Version1 SPARC Keyboard Specification
SPARC INTERNATIONAL Version1 SPARC Keyboard Specification SPARC International, Inc. 3333 Bowers Ave., Suite 280, Santa Clara, CA 95054-3913, 408-748-9111. FAX 408-748-9777 1999, SPARC International Inc.
More informationAPPENDIX- A REFERENCE IMPLEMENTATION OF BSF-128 ===============================================================
APPENDICES A p p e n d i c e s P a g e 144 A p p e n d i c e s P a g e 145 APPENDIX- A REFERENCE IMPLEMENTATION OF BSF-128 =============================================================== REFERENCE IMPLEMENTATION
More information1 SETTING UP GENERAL FUNCTION TYPE PROTOCOL MESSAGES COMMAND RETURN CODES... 6 TRANSACTION EXAMPLES...
1 SETTING UP... 3 1.1 RS232 CONTROL CABLES...3 1.2 RS232 SETTINGS...3 2 GENERAL... 4 3 FUNCTION TYPE... 4 4 PROTOCOL MESSAGES... 4 4.1 MESSAGE FORMATS...4 4.1.1 Message Head...4 4.1.2 Message Body...5
More informationArduCAM-M-2MP Camera Shield
33275-MP ArduCAM-M-2MP Camera Shield 2MP SPI Camera Hardware Application Note Rev 1.0, Mar 2015 33275-MP ArduCAM-M-2MP Hardware Application Note Table of Contents 1 Introduction... 2 2 Typical Wiring...
More informationM2M/DMTME Instruments Communication protocol. Technical specification V.2.1 2CSG445011D0201
M2M/DMTME Instruments Communication protocol 2CSG445011D0201 1 Setting up M2M/DMTME serial communication... 3 1.1 Serial network ID programming... 3 1.2 RS-485 communication interface... 3 1.3 Serial line
More informationWireless M-Bus Host Controller Interface
Wireless M-Bus Host Controller Interface Document ID: 4100/6404/0050 IMST GmbH Carl-Friedrich-Gauß-Str. 2-4 47475 KAMP-LINTFORT GERMANY General Information Document Information File name WMBus_HCI_Spec.docx
More informationRS-232 Control of the Advantage DRI
RS-232 Control of the Advantage DRI Biamp Systems, 14130 N.W. Science Park, Portland, Oregon 97229 U.S.A. (503) 641-7287 an affiliate of Rauland-Borg Corp. Introduction This document contains technical
More informationSM2400-EVK1. Evaluation Kit for SM2400 Multi-Standard Narrowband Power Line Communication Modem. Product Overview. Features
SM2400-EVK1 Evaluation Kit for SM2400 Multi-Standard Narrowband Power Line Communication Modem Communication technology by: Semitech Semiconductor Product Overview The SM2400-EVK1 is a complete evaluation
More informationMahesh V. Tripunitara and Samuel S. Wagsta, Jr. COAST Laboratory. Purdue University. COAST TR-98/01.
The Compression Functions of SHA, MD, MD4 and MD5 are not Ane Mahesh V. Tripunitara and Samuel S. Wagsta, Jr. COAST Laboratory Purdue University West Lafayette, IN 47907-198 ftripunit,sswg@cs.purdue.edu
More informationDual core architecture with custom N-PLC optimized DSP and Data Link Layer 32bit controller
SM2400 N-PLC Transceiver MultiStandard Narrowband Power Line Communication Modem Communication technology by: Semitech Semiconductor Product Overview The SM2400 is the ultimate Narrowband Power Line Communication
More informationComputer Control of the Advantage DRC 4+4
Computer Control of the Advantage DRC 4+4 Biamp Systems, 14130 N.W. Science Park, Portland, Oregon 97229 U.S.A. (503) 641-7287 an affiliate of Rauland-Borg Corp. Introduction This document contains technical
More informationDULCOMETER Multi-parameter Controller dialog DACa
Software manual DULCOMETER Multi-parameter Controller dialog DACa Modbus RTU EN Valid only in combination with the operating instructions for the Multi-parameter Controller dialog DACa. A2100 Please carefully
More informationAquaCER with TTL OUTPUT
INSTRUCTION MANUAL AquaCER with TTL OUTPUT DESCRIPTION: The AquaCER TTL is a hydrostatic pressure transmitter, with a capacitive ceramic sensor, and can withstand very high burst pressures. The applied
More informationSerial Boot Loader For CC2538 SoC
Serial Boot Loader For CC2538 SoC Document Number: SWRA431 Version 1.1 TABLE OF CONTENTS 1. PURPOSE... 3 2. FUNCTIONAL OVERVIEW... 3 3. ASSUMPTIONS... 3 4. DEFINITIONS, ABBREVIATIONS, ACRONYMS... 3 5.
More informationSigned/Unsigned Integer Arithmetic in C. Vineel Kovvuri
Signed/Unsigned Integer Arithmetic in C Vineel Kovvuri http://vineelkovvuri.com Contents 1 Introduction 2 2 How signed-ness is represented in the hardware? 2 3 How signed-ness is interpreted in assembly?
More informationAN4872 Application note
Application note BlueNRG-1 and BlueNRG-2 UART bootloader protocol Introduction The BlueNRG-1 and BlueNRG-2 are very low power Bluetooth low energy (BLE) single-mode systemson-chip, compliant with Bluetooth
More informationSIMCom_3G_CSD_Application Note_V1.00
SIMCom_3G_CSD_Application Note_V1.00 Document Title: SIMCom_3G_CSD_Application Note Version: 1.00 Date: Status: Document Control ID: Release SIMCom_3G_CSD_Application Note_V1.00 General Notes SIMCom offers
More informationThe Roboteq Modbus Implementation User Manual
The Roboteq Modbus Implementation User Manual V1.1, December 21, 2017 Visit www.roboteq.com to download the latest revision of this manual Copyright 2017 Roboteq, Inc Copyright Roboteq Inc. 2018. All Rights
More informationBoot Loader. Bootloader
October 2013 Boot Loader A program that is executed upon initial power-up that typically involves a power-on self-test, locating and initializing peripheral devices, and then loading and starting an operating
More informationOEM API Specification
OEM API Specification For Wasatch Photonics OEM Spectrometers WasatchDevices.com Revised 2016-08-26 Page 1 Revision Log Revision Date By Reason 1.0 2016-08-29 J. Traud Initial Release Contents General
More informationJMY504M User's Manual
JMY504M User's Manual (Revision 3.42) Jinmuyu Electronics Co. LTD 2011/6/28 Please read this manual carefully before using. If any problem, please mail to: Jinmuyu@vip.sina.com Contents 1 Product introduction...
More informationMemory Map for the MCU320 board:
Memory Map for the MCU320 board: The Intel 8051 MCUs and all derivatives are based on the Harvard architecture. This is to say that they have separate memory space for program (CODE) and external data
More informationESP8266 Application Note Firmware Download Protocol
ESP8266 Application Note Firmware Download Protocol Version 1.0 Copyright 2016 About This Guide This document introduces ESP8266 firmware download protocol with a structure as follows. Chapter Title Subject
More informationon a 35 mm top-hat rail (in accordance with DIN EN TH35) Ambient temperature Operation: C Storage: C
Data sheet PCD1.B1020-A20 E-Line RIO 16DI, 4Rel Starting with FW 1.08.xx The L-Serie E-Line RIO modules are controlled via the RS-485 serial communication protocols S-Bus and Modbus for decentralised automation
More informationTPMC816. Two Independent Channels Extended CAN Bus PMC Module. Version 2.2. User Manual. Issue August 2014
The Embedded I/O Company TPMC816 Two Independent Channels Extended CAN Bus PMC Module Version 2.2 User Manual Issue 2.2.1 August 2014 TEWS TECHNOLOGIES GmbH Am Bahnhof 7 25469 Halstenbek, Germany Phone:
More informationUSER GUIDE EDBG. Description
USER GUIDE EDBG Description The Atmel Embedded Debugger (EDBG) is an onboard debugger for integration into development kits with Atmel MCUs. In addition to programming and debugging support through Atmel
More information1 Introduction Revision History... 4
Contents 1 Introduction 4 1.1 Revision History............................................. 4 2 Connectors 4 2.1 J1011 - PMBus Addressing........................................ 5 2.1.1 Parallel Operation........................................
More informationQBridge. I2C, SPI, CAN Control Software User s Manual. Date: Rev 1.3
QBridge I2C, SPI, CAN Control Software User s Manual Date: 9-10-2005 Rev 1.3 1. Introduction...1 1.1. What QBridge can do?... 1 1.2. Disclaimer... 1 1.3. Operational Format... 1 1.4. QBridge-V2... 1 2.
More informationGSA GAT PROTOCOL V Game Authentication Terminal
GSA GAT PROTOCOL V3.50.0 Game Authentication Terminal Gaming Standards Association GAT Technical Committee Released: 2010/12/13 Document ID: gsa-p0093.001.00 GAMINGSTANDARDS.COM GSA GAT Protocol, Document
More informationEthernet to Digital I/O and Analog Input. (Model: IP-IO)
Ethernet to Digital I/O and Analog Input (Model: IP-IO) Feature: Operation voltage : DC 7V ~ 36V. Analog Interface: Interface : 3.3V levels compatibility. Resolution : 16-bits Σ-Δ A/D converters. Accuracy
More informationAN EZ-USB FX3 I 2 C Boot Option. Application Note Abstract. Introduction. FX3 Boot Options
EZ-USB FX3 I 2 C Boot Option Application Note Abstract AN68914 Author: Shruti Maheshwari Associated Project: No Associated Part Family: EZ-USB FX3 Software Version: None Associated Application Notes: None
More informationSuperCard Pro Software Developer's Kit Manual v1.7 Release Date: December 23, 2013 Last Revision: December 7, 2015
www.cbmstuff.com SuperCard Pro Software Developer's Kit Manual v1.7 Release Date: December 23, 2013 Last Revision: December 7, 2015 All material including, but not limited to photographs, text, and concepts
More informationDATA SHEET. article numbers P125-1b & P125-1g
LC 16.2 TREND DATA SHEET article numbers P125-1b & P125-1g Pottery House, Pottery Road, Dun Laoghaire, Co. Dublin, Ireland. Tel: +353-1-2350279 Fax: +353-1-2350361 Am Gneisenauflöz 6, 66538 Neunkirchen,
More informationAN5123 Application note
Application note STSPIN32F0A - bootloader and USART protocol Introduction Cristiana Scaramel The STSPIN32F0A is a system-in-package providing an integrated solution suitable for driving three-phase BLDC
More informationJMY607H User's Manual
JMY607H User's Manual (Revision 3.42) Jinmuyu Electronics Co. LTD 2011/6/27 Please read this manual carefully before using. If any problem, please mail to: Jinmuyu@vip.sina.com Contents 1 Product introduction...
More informationCommunication Technology by: Semitech Semiconductor. SM2400 Serial-2-PLC Adapter User s Guide
Communication Technology by: Semitech Semiconductor Serial-2-PLC Adapter User s Guide This publication contains proprietary information which is subject to change without notice and is supplied as is,
More informationKinetis Bootloader to Update Multiple Devices in a Field Bus Network
Freescale Semiconductor, Inc. Document Number: AN5204 Application Note Rev. 0, 01/2016 Kinetis Bootloader to Update Multiple Devices in a Field Bus Network 1. Introduction This application note describes
More information//
----------------------------------------------------------------------------------- Filename: FixedMath.h ----------------------------------------------------------------------------------- -----------------------------------------------------------------------------------
More informationVerve IPAC Plug-in Wireless AC Module. Software Setup 3. DolphinView Software 3. Preparations 4 Transmit LINK Signals 4.
Verve IPAC Plug-in Wireless AC Module Wireless Linking & Configuration Guide Table of Contents IPAC Configuration Settings 2 Configuration Settings Reference Table 2 Software Setup 3 DolphinView Software
More informationChapter 2: Secret Key
Chapter 2: Secret Key Basics Block or Stream? Secret Key Methods Salting AES Key Entropy Prof Bill Buchanan OBE http://asecuritysite.com/crypto02 http://asecuritysite.com/encryption Conclusion Encryption
More information// and verify that there is a sine wave with frequency <FREQUENCY> and
F330DC_IDA0_SineWave.c Copyright 2006 Silicon Laboratories, Inc. http:www.silabs.com Program Description: This program outputs a sine wave using IDA0. IDA0's output is scheduled to update at a rate determined
More informationPCD1.A2000-A20. E-Line S-Serie RIO 6Rel 16A. Features. General technical data. Dimensions and installation
Data sheet www.sbc-support.com PCD1.A2000-A20 E-Line S-Serie RI 6Rel 16A The S-Serie E-Line RI modules are controlled via the RS-485 serial communication protocols S-Bus and Modbus for decentralised automation
More informationEDBG. Description. Programmers and Debuggers USER GUIDE
Programmers and Debuggers EDBG USER GUIDE Description The Atmel Embedded Debugger (EDBG) is an onboard debugger for integration into development kits with Atmel MCUs. In addition to programming and debugging
More informationMotors I Automation I Energy I Transmission & Distribution I Coatings. Modbus RTU CFW701. User s Manual
Motors I Automation I Energy I Transmission & Distribution I Coatings Modbus RTU CFW701 User s Manual Modbus RTU User s Manual Series: CFW701 Language: English Document Number: 10001538593 / 00 Publication
More informationModbus communication protocol
TIP Thüringer Industrie Produkte GmbH Bahnhofstraße 26 99842 Ruhla GERMANY Tel. : +49 (0)36929/64029-0 Fax : +49 (0)36929/64029-99 info@stromzaehler.de www.stromzaehler.de Modbus communication protocol
More informationAN4 QCA7000 SPI / UART Protocol
AN4 QCA7000 SPI / UART Protocol I2SE GmbH: Christian Aurich, Stefan Wahren June 14, 2018 1/11 CONTENTS CONTENTS Contents 1 Revisions 3 2 Introduction 3 3 SPI Physical Layer 3 4 UART Physical Layer 3 5
More informationModbus RTU CFW100. User s Manual. Phone: Fax: Web: -
Modbus RTU CFW100 User s Manual Modbus RTU User s Manual Series: CFW100 Language: English Document Number: 10002909455 / 00 Publication Date: 06/2014 CONTENTS CONTENTS... 3 ABOUT THIS MANUAL... 5 ABBREVIATIONS
More informationRequest for Comments: XXXX November Registration of a Georgian Character Set draft-giasher-geostd8-00.txt
Internet draft Gia Shervashidze Network Working Group Georgian Internet Avenue Request for Comments: XXXX November 2001 Registration of a Georgian Character Set draft-giasher-geostd8-00.txt Status of this
More informationPCD1.W5200-A20. E-Line S-Serie RIO 8AO. Features. General technical data. Dimensions and installation
Data sheet www.sbc-support.com PCD1.W5200-A20 E-Line S-Serie RI 8A The S-Serie E-Line RI modules are controlled via the RS-485 serial communication protocols S-Bus and Modbus for decentralised automation
More informationPCI-4IPM Revision C. Second Generation Intelligent IP Carrier for PCI Systems Up to Four IndustryPack Modules Dual Ported SRAM, Bus Master DMA
PCI-4IPM Revision C Second Generation Intelligent IP Carrier for PCI Systems Up to Four IndustryPack Modules Dual Ported SRAM, Bus Master DMA REFERENCE MANUAL 781-21-000-4000 Version 2.1 April 2003 ALPHI
More informationSPI Lasers UK Limited. Serial Command Reference for the PRISM Laser Platform
SPI Lasers UK Limited Serial Command Reference for the PRISM Laser Platform 1 of 89 Table of Contents Introduction... Connecting to the OEM Fibre Laser... Data Link Layer... Frame Structure... Data Element...
More informationAN4491 Application note
Application note BlueNRG, BlueNRG-MS updater Introduction Note: This document describes the updater functionality of BlueNRG and BlueNRG-MS devices. The document content is valid for both BlueNRG and BlueNRG-MS
More informationGetting Started with the MCU Flashloader
NXP Semiconductors Document Number: MBOOTFLASHGS User's Guide Rev 3, 05/2018 Getting Started with the MCU Flashloader Contents Contents Chapter 1 Introduction...3 Chapter 2 Overview...4 2.1 MCU flashloader...4
More informationControl Flow Integrity with ptrace()
Control Flow Integrity with ptrace() Sebastian Krahmer krahmer@suse.de May 18, 2006 Abstract Control Flow Integrity (CFI) is a new technology to ensure a certain execution flow of a program. One of its
More informationModbus Map: Conext XW/XW+ Device
Map: Conext XW/XW+ Device 503-0246-01-01 Revision A.3 UNINTENDED OPERATION WARNING The use of this product with communications requires expertise in the design, operation, and programming of the device.
More informationJMY501H User's Manual
JMY501H User's Manual (Revision 3.42) Jinmuyu Electronics Co. LTD 2011/6/27 Please read this manual carefully before using. If any problem, please mail to: Jinmuyu@vip.sina.com Contents 1 Product introduction...
More information1-Mbit (128K 8) Serial (SPI) F-RAM
1-Mbit (128K 8) Serial (SPI) F-RAM 1-Mbit (128K 8) Serial (SPI) F-RAM Features 1-Mbit ferroelectric random access memory (F-RAM) logically organized as 128K 8 High-endurance 100 trillion (10 14 ) read/writes
More informationTPMC Channel Isolated Serial Interface RS232. Version 1.0. User Manual. Issue August 2017
The Embedded I/O Company TPMC860 4 Channel Isolated Serial Interface RS232 Version 1.0 User Manual Issue 1.0.4 August 2017 TEWS TECHNOLOGIES GmbH Am Bahnhof 7 25469 Halstenbek, Germany Phone: +49 (0) 4101
More informationKinetis Bootloader QuadSPI User's Guide
Freescale Semiconductor Document Number: KBLQSPIUG User's Guide Rev. 1, 04/2016 Kinetis Bootloader QuadSPI User's Guide 1 Introduction The QuadSPI controller available on selected Kinetis devices supports
More informationClock Synchronous Control Module for Serial Flash Memory Access Firmware Integration Technology
APPLICATION NOTE RX Family R01AN2662EJ0234 Rev.2.34 Introduction This application note explains how to control and use serial flash memory with microcontrollers manufactured by Renesas Electronics. Refer
More informationRevision History. Rev Date Author Description A 27 Aug 99 Emil Farkas Initial release. Approvals: Author. VP. Engineering
Carina Manual Carina Manual Revision History Style Sheet is: X:\Company\SmartMasters\Orion Filenames are: X:\Company\Manuals\ReferenceManual\Components\Carina\RevA\CarinaManual.lwp X:\Company\Manuals\ReferenceManual\Components\Carina\RevA\CarinaManualTitlePage
More informationCyberAtom X-202 USER MANUAL. Copyrights Softexor 2015 All Rights Reserved.
CyberAtom X-202 USER MANUAL Copyrights Softexor 2015 All Rights Reserved. X-202 Contents ii Contents About...5 Block Diagram... 5 Axes Conventions...5 System Startup... 6 Hardware Reset...6 LED indicator...
More informationJDICON 400/500 JDICON 401/501. B Interface Description. Universal process controller
JDICON 400/500 Universal process controller JDICON 401/501 Universal profile controller Universal profile generator B 70.3570.2 Interface Description 10.99/00371593 Contents 1 Introduction 5 1.1 Preface...
More informationCyberAtom X-200 USER MANUAL. Copyrights Softexor 2015 All Rights Reserved.
CyberAtom X-200 USER MANUAL Copyrights Softexor 2015 All Rights Reserved. X-200 Contents ii Contents About...6 Block Diagram... 6 Axes Conventions...6 System Startup... 7 Selecting Power Source...7 Hardware
More information