CW308T-CEC1702 - Revision history

Coflynn: Replaced content with "== Page Moved == See [https://rtfm.newae.com/Targets/UFO%20Targets/CW308T-CEC1702/ NewAE RTFM Page] which is now built from the [https://github.com/newaetech/chipwhispere..."

2020-07-29T19:32:42Z

Replaced content with "== Page Moved == See [https://rtfm.newae.com/Targets/UFO%20Targets/CW308T-CEC1702/ NewAE RTFM Page] which is now built from the [https://github.com/newaetech/chipwhispere..."

Show changes

Adewar: /* ATE and EFUSE */

2019-07-18T15:08:02Z

‎ATE and EFUSE

Adewar: /* Programming the Device */

2019-07-17T20:40:03Z

‎Programming the Device

Fheubach at 18:24, 1 May 2018

2018-05-01T18:24:09Z

Fheubach: Change header levels

2018-05-01T14:04:47Z

Change header levels

Coflynn at 13:18, 5 April 2018

2018-04-05T13:18:43Z

Coflynn: /* ATE and EFUSE */

2018-04-05T12:56:01Z

‎ATE and EFUSE

Coflynn: /* ATE and EFUSE */

2018-04-05T12:54:22Z

‎ATE and EFUSE

Adewar at 20:59, 4 April 2018

2018-04-04T20:59:37Z

Adewar at 20:43, 4 April 2018

2018-04-04T20:43:50Z

@@ Line 282: / Line 282: @@
 * Some additional features of the EFUSE include setting keys for flash decryption and authentication by the bootloader.
-You can see an example program that works with the CW308T-CEC1702 device at [https://github.com/newaetech/chipwhisperer-target-cec1702](https://github.com/newaetech/chipwhisperer-target-cec1702).
+You can see an example program that works with the CW308T-CEC1702 device at [https://github.com/newaetech/chipwhisperer-target-cec1702](https://github.com/newaetech/chipwhisperer-target-cec1702). '''NOTE: This firmware requires that integers are 32bits. Before building this project, go to Project>Edit Project and change Data Type Size to "other (int 4 byte)"'''
 To use E-FUSE with the CW308T, you will need to use a jumper wire. To do this:

@@ Line 190: / Line 190: @@
 === Programming the SPI Flash ===
-The [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B] flash chip on the target board can be programmed by an SPI programmer attached to the SPI pins of the CW308. To program the chip, the nRST chip must be pulled to ground by holding the nRST button down or by connecting a jumper to J8 on the CW308. Additionally, the SDIC pin must be driven high during the programming process the enable communication through a buffer chip.
+The [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B] flash chip on the target board can be programmed by an SPI programmer attached to the SPI pins of the CW308. To program the chip, the nRST chip must be pulled to ground by holding the nRST button down or by connecting a jumper to J8 on the CW308. Additionally, the PDIC pin must be driven high during the programming process to enable communication through a buffer chip.
 The [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B] flash chip uses global block protection that must be disabled before every write operation. This is done by sending the command code '''98''' to the chip before erasing or writing to the device. This can be done by configuring a custom transaction in your flash programming software. Below is a table of useful information for configuring your programming software. The Parameters listed here have been tested with the Total Phase Flash Center software and the Aardvark I<sup>2</sup>C/SPI Host adapter. Additionally, a [https://www.totalphase.com/products/flash-center/ Total Phase Flash Center] script is provided with the firmware for additional reference. See the [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B data sheet] and the manual for your SPI flash program for more details.

← Older revision		Revision as of 18:24, 1 May 2018
Line 301:		Line 301:
	* [http://www.mikroe.com/mikroc/arm mikroC PRO for ARM IDE]		* [http://www.mikroe.com/mikroc/arm mikroC PRO for ARM IDE]
	* [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B Flash Datasheet]		* [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B Flash Datasheet]
		+
		+	== Hardware ==
		+	{{Template:Hardware}}

@@ Line 130: / Line 130: @@
 == Hardware Cryptography ==
-==== Multi-purpose AES Cryptographic Engine ====
+=== Multi-purpose AES Cryptographic Engine ===
 - Hardware support for ECB, CTR, CBC, and OFB AES modes
@@ Line 137: / Line 137: @@
 - DMA interface to SRAM, shared with Hash engine
-==== Cryptographic Hash Engine ====
+=== Cryptographic Hash Engine ===
 - Support for SHA-1, SHA-256, SHA-512
 - DMA interface to SRAM, shared with AES engine
-==== Public Key Cryptographic Engine ====
+=== Public Key Cryptographic Engine ===
 - Hardware support for RSA and Elliptic Curve public key algorithms
@@ Line 151: / Line 151: @@
 - Microcoded support for standard public key algorithms
-==== Other Cryptographic Features ====
+=== Other Cryptographic Features ===
 - True Random Number Generator
@@ Line 161: / Line 161: @@
 The firmware provided with Chipwhisperer (or its own repo) is designed to work with the [http://www.mikroe.com/mikroc/arm MikroC PRO for ARM IDE]. This IDE supports the many peripherals of the CEC1702, including the hardware security features and comes with extensive libraries and example code. The board layout has been designed to be compatible with many of the provided examples, while some others can be easily modified to work with the CW308T-CEC1702. After the binaries have been created, they can either be loaded into SPI Flash or directly into RAM via JTAG.
-==== Creating and Modifying Examples ====
+=== Creating and Modifying Examples ===
 The following notes may prove useful when using mikroC PRO examples or creating your own:
 * Any example which uses UART1 needs to be changed to use UART0 by changing the UART1_* functions to UART0_*.
@@ Line 171: / Line 171: @@
 * There are no GPIO library functions to write or read from pins. Instead, use GPIO_OUTPUT_xxx_xxx.Bn/GPIO_INPUT_xxx_xxx.Bn for bit n of pin range xxx-xxx.
-==== Compilation Settings ====
+=== Compilation Settings ===
 '''Project > Edit Project'''
@@ Line 189: / Line 189: @@
 The CEC1702 supports loading code in two ways: from external flash memory into RAM and directly into RAM over JTAG.
-==== Programming the SPI Flash ====
+=== Programming the SPI Flash ===
 The [http://ww1.microchip.com/downloads/en/DeviceDoc/20005262C.pdf SST26VF016B] flash chip on the target board can be programmed by an SPI programmer attached to the SPI pins of the CW308. To program the chip, the nRST chip must be pulled to ground by holding the nRST button down or by connecting a jumper to J8 on the CW308. Additionally, the SDIC pin must be driven high during the programming process the enable communication through a buffer chip.
@@ Line 259: / Line 259: @@
 |}
-==== Programming over JTAG/SWD ====
+=== Programming over JTAG/SWD ===
 In addition to the SPI flash method, the CEC1702 can be temporarily (until power off) programmed using a JTAG debugger. This has been tested using Ozone V2.56d with a j-Trace Pro from Segger. The mikroC PRO IDE also supports programming and debugging using the Segger.
@@ Line 266: / Line 266: @@
 Load the image binary on to the flash chip and verify that the write was performed. If verification fails, ensure the nRST pin was held low for the entirety of the erase/write/verify cycle. If verification still fails, refer to the data sheet and your programming software manual to make sure the necessary command codes were sent in the appropriate order.
-==== Running the Program ====
+=== Running the Program ===
 If you programmed the device via SPI flash, remove the nRST jumper/release the nRST button and disconnect the 3.3V source from PDIC. If you loaded your code from JTAG, hit go on your debugging software.

@@ Line 288: / Line 288: @@
 * Using a screwdriver, adjust VADJ trimmer to output 1.60V. Note you might need to switch the V-ADJ source voltage.
 * Jumper the VADJ output to the VFUSE header pin.
 == Useful Links ==

@@ Line 273: / Line 273: @@
 == ATE and EFUSE ==
-The CEC1702 may ship in ATE mode from other suppliers, which prevents booting off of SPI flash and seems to mess with the UART baud rate (57600 baud corresponded to 32000 baud). The device can be changed into normal mode by setting Byte 35 Bit[7] of the EFUSE memory. This can be done via an external SPI flash such as the mikroProg, or by loading a program that modifies the bits via JTAG. For additional information, see the CEC1702 datasheet and errata. Before modifying the EFUSE, keep the following in mind:
+The CEC1702 ships in ATE mode suppliers, which prevents booting off of SPI flash and seems to mess with the UART baud rate (57600 baud corresponded to 32000 baud). Note the CW308T-CEC1702 target boards have this disabled as part of the production process / test procedure.
 * EFUSE bits are one time programmable (OTP) to 1. This means there's no way to set the bits back to 0 once they are set to 1.
 * To modify the EFUSE, VREF must be set to between 1.52V and 1.6V.
@@ Line 279: / Line 281: @@
 * Note that both the EFUSE instructions in the CEC1702 datasheet and mikroC PRO's EFUSE program rely on VREF being set to ground while FSOURCE_EN_READ and FSOURCE_EN_PRGM are being switched. Instead, to modify the EFUSE, set both to 0, wait for the registers to be set, then set the appropriate bit.
 * Some additional features of the EFUSE include setting keys for flash decryption and authentication by the bootloader.
 == Useful Links ==

← Older revision		Revision as of 20:59, 4 April 2018
Line 13:		Line 13:

	The CW308T-CEC1702 incorporates the main chip with a 16MB SPI flash chip and a bi-directional SPI Buffer. The target board has standard power monitoring, UART serial, and clock In/Out compatibility with the CW308. JTAG pins and many GPIO pins are also exposed for prototyping and testing use.		The CW308T-CEC1702 incorporates the main chip with a 16MB SPI flash chip and a bi-directional SPI Buffer. The target board has standard power monitoring, UART serial, and clock In/Out compatibility with the CW308. JTAG pins and many GPIO pins are also exposed for prototyping and testing use.
		+
		+	This device is interesting in that it has a lot of hardware crypto and security functionality.

	== I/O Connections ==		== I/O Connections ==

@@ Line 160: / Line 160: @@
 ==== Creating and Modifying Examples ====
-The following notes may prove useful when using mikroC examples or creating your own:
+The following notes may prove useful when using mikroC PRO examples or creating your own:
 * Any example which uses UART1 needs to be changed to use UART0 by changing the UART1_* functions to UART0_*.
 * The plain text and encrypted text buffers need to be 16 byte aligned for the CEC1702's DMA to function properly. If the aes_crypt() call fails or the encryption never completes, this may be the cause. See simpleserial_base.c or mikroC PRO's AES examples for examples of this.
 * All variable declarations need to be done at the beginning of functions, before any variables are modified or functions are called.
-* The mikroC compiler may have strange sizes for integer constants, meaning changing 4 8 bit numbers into a 32 bit number via bitshifts may not work as intended. Instead, using memcpy() may prove easier and more reliable.
+* The mikroC PRO compiler may have strange sizes for integer constants, meaning changing 4 8 bit numbers into a 32 bit number via bitshifts may not work as intended. Instead, using memcpy() may prove easier and more reliable.
-* When using mikroC's "Clean Project Folder", ensure that .mcpar, .c, .h, and .xml files are not selected, as this will cause the source/project/Flash Center
+* When using mikroC PRO's "Clean Project Folder", ensure that .mcpar, .c, .h, and .xml files are not selected, as this will cause the source/project/Flash Center
 * The port base for use with the GPIO library is actually GPIO_PORT_xxx_xxx, not _GPIO_PORT_xxx_xxx. Additionally, this is not a pointer, meaning the address of this variable needs to be passed to the gpio functions
 * There are no GPIO library functions to write or read from pins. Instead, use GPIO_OUTPUT_xxx_xxx.Bn/GPIO_INPUT_xxx_xxx.Bn for bit n of pin range xxx-xxx.
@@ Line 258: / Line 258: @@
 ==== Programming over JTAG/SWD ====
-In addition to the SPI flash method, the CEC1702 can be temporarily (until power off) programmed using a JTAG debugger. This has been tested using Ozone V2.56d with a j-Trace Pro from Segger. The mikroC Pro IDE also supports programming and debugging using the Segger.
+In addition to the SPI flash method, the CEC1702 can be temporarily (until power off) programmed using a JTAG debugger. This has been tested using Ozone V2.56d with a j-Trace Pro from Segger. The mikroC PRO IDE also supports programming and debugging using the Segger.
 Note that the CEC1702 only supports JTAG when the Debug Select bit (Byte 482 Bit[6]) of EFUSE is 0 and SWD when the Debug Select bit is 1. If one does not work, try the other.
@@ Line 275: / Line 275: @@
 * To modify the EFUSE, VREF must be set to between 1.52V and 1.6V.
 * Make sure that FSOURCE_EN_READ and FSOURCE_EN_PRGM are never set to 1 at the same time, as this will short ground and power.
-* Note that both the EFUSE instructions in the CEC1702 datasheet and mikroC's EFUSE program rely on VREF being set to ground while FSOURCE_EN_READ and FSOURCE_EN_PRGM are being switched. Instead, to modify the EFUSE, set both to 0, wait for the registers to be set, then set the appropriate bit.
+* Note that both the EFUSE instructions in the CEC1702 datasheet and mikroC PRO's EFUSE program rely on VREF being set to ground while FSOURCE_EN_READ and FSOURCE_EN_PRGM are being switched. Instead, to modify the EFUSE, set both to 0, wait for the registers to be set, then set the appropriate bit.
 * Some additional features of the EFUSE include setting keys for flash decryption and authentication by the bootloader.