Code: |
AS + 112 |
Symbolic: |
bccFlashInit |
This command will request to create, define and initialize flashes for the connected device. Request parameters are the following:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U32 |
FLAGS |
Operating flags: 0x00000001 Query only effective configuration |
4 |
U8 |
NFLA |
Number of required flashes (min 1). |
5 |
... |
FLA0 |
Flash 0 request |
... |
... |
FLA1 |
Flash 1 request |
... |
... |
... |
|
Where FLAx contains the following parameters:
Offset |
Type |
Label |
Description |
|---|---|---|---|
+0 |
U8[4] |
NAME |
Flash name (3 + 0 terminator) |
+4 |
U32 |
SIZE |
Required size [kbyte] |
Notes:
•for standard flashes the name is /Fx, where x is @ for system flash, and from A to Z for users defined flashes
•for compact flashes use the bccFlashDisk command.
On success, a bccAck is received with the following data:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U8 |
NFL |
Number of effective flashes |
1 |
... |
FLA0 |
Flash 0 effective data |
... |
... |
FLA0 |
Flash 1 effective data |
... |
... |
... |
|
Where FLAx contains the following parameters:
Offset |
Type |
Label |
Description |
|---|---|---|---|
+0 |
U8x4 |
NAME |
Flash name (3 + 0 terminator) |
+4 |
U32 |
SIZE |
Effective size [kbyte] |
On failure, a bccNack is received. Specific errors:
NACK code |
Description |
Extra data |
|---|---|---|
nackIllegalArgs |
Illegal parameters |
U16 What illegal: 1=Flags 2=No. of flashes 3=Flashes 100+x=Flash x name 200+x=Flash x size |
nackReadOnly |
The flash (or the device itself) is read-only and cannot be initialized. |
|
After the bccAck is received, the initialization operation will begin as soon as possible: when operation normally end you will receive a bccCompleted message (with no data). If operation is aborted from the device, you will receive a bccAborted.
Notes:
•Operation cannot be aborted by command, but only from remote.
•Both bccCompleted and bccAborted will have PID as request command PID.
During the operation you can optionally request the operation status by sending a bccCheck message (with no parameters): as DCH value you must use the SCH value from first bccAck message. The bccAck answer for a bccCheck, will contain following data:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U8 |
PERC |
Operation progress (%) |
1 |
STRZ |
MSG |
Optional status message |
