Basic Information

Hashrate:
3.5T (+-5%)
Power consumption:
990W (measure on 12V port of the device)
1100W (on the wall, with assumption of 90% power conversion ratio)
Power per hash:
270J/THash (device only)
295J/THash (on the wall, with assumption of 90% power conversion
ratio)
Overclocking:
Support automatically optimize frequency, no need to overclock manually.
PSU output pin:
4x6PIN PCIe power connector. *All must be connected.*
PSU requirements:
Minimum 1100W output, recommend to use high-quality PSU for server
with more than 1200W output and high quality power cable.
Input voltage no lower than 11.7V and no higher than 12.2V (numbers
take from the controller)
Lower voltage leads to lower hashrate and higher voltage leads to
possible device burning down.
NOTICE: Poor quality cable may result in low voltage.
Fan:
Specs: 12038
Current: between 1.6A and 2.8A.
Minimum RPM: 3800.
*NOTICE* If the fan is broken or the fan's RPM cannot be measure,
the device will not start.
Controller:
Raspberry Pi (version B or B+)
Raspberry Pi 2 will be supported at the middle of December 2015
Each Rpi can control approximately ~12 devices.
AUC:
Each AUC can connect up to 6 devices.
Dimensions:
354x136x150mm
Net weight:
~4.8kg
Protection Degree:
IP20

Time,in milliseconds, that the device will wait after receipt of the DFU_DETACH request. if this time elapses without a USB reaset, then the device will terminate the Reconfiguration phase and revert back to normal operation . This repreents the maximum time that the device can wait(depending on its timers, etc.).The host may specify a shorter timeout in the DFU_DETACH request.

5

wTransferSize

2

Number

Maximum number of bytes that the device can accept per control-write transaction.

7

bcdDFUVersion

2

BCD

Numeric expression identifying the version of the DFU Specification release.

DFU Mode Interface Descriptor

Offset

Field

Size

Value

Descripton

0

bLength

1

09h

Size of this descriptor,in bytes.

1

bDescriptorType

1

04h

INTERFACE descriptor type.

2

bInterfaceNumber

1

Number

Number of this interface.

3

bAlternateSetting

1

00h

Alternate setting. Must be zero.

4

bNumEndpoints

1

00h

Only the control pipe is used.

5

bInterfaceClass

1

FEh

Application Specific Class Code.

6

bInterfaceSubClass

1

01h

Device Firmware Upgrade Code.

7

bInterfaceProtocol

1

02h

DFU mode protocol.

8

iInterface

1

index

Index of string descriptor for this interface.

USB-DFU Product's USB Descriptor

DFU Updata Process Diagram

How To Judge The Bootloader Program Is Updating Or Jump To Application Program

I used a updata flag which is a four bytes word and is writed at fixd flash address (0x8000 - 4)

The flag's value is 0xAABBCCDD

When the bootloader program run, first it judge the updata flag, if the updata falg is not equal 0xAABBCCDD, it will jump to application program.
Otherwise it will run to updata program.

How To Jump To Application Program

When we don't want to updata application program, the bootloader program should run to application program.

In order to achieve this goal, we can add under code in your bootloader program.