Delete file

requesttype=0x0a

This differs from the command 0x0d in the older protocol; instead of separate strings for directory and file name, we have a complete path specification (directory/file), then another copy of the directory name. Each seems to be allowed 48 bytes (0x30).

Command: variable length (here 0x91 bytes)

00000000  51 00 00 00 01 02 00 00 00 00 00 00 00 00 00 00  Q...............
00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000020  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000040  02 00 00 00 0a 00 10 11 51 00 00 00 2c d8 12 00  ........Q...,...
00000050  41 3a 2f 44 43 49 4d 2f 31 30 31 43 41 4e 4f 4e  A:/DCIM/101CANON
00000060  2f 49 4d 47 5f 30 31 30 35 2e 4a 50 47 00 00 00  /IMG_0105.JPG...
00000070  07 00 05 00 00 01 08 00 68 76 8f 00 78 80 8f 00  ........hv..x...
00000080  41 3a 2f 44 43 49 4d 2f 31 30 31 43 41 4e 4f 4e  A:/DCIM/101CANON
00000090  2f                                               /
      

Here we delete a JPEG file. The complete path string is terminated by (at least one) zero byte, followed by garbage. At offset 0x80 of the packet (0x30 of the payload), we have the directory name, with no trailing zero byte.

Response: 0x54 bytes

00000000  14 00 00 00 01 03 00 00 00 00 00 00 00 00 00 00  ................
00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000020  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000000  02 00 00 00 0a 00 10 21 14 00 00 00 2c d8 12 00  .......!....,...
00000010  00 00 00 00                                      ....
      

Status codes:

0x00000000 No errors
0x82200040 ??
0x82220040 Bad parameters? Directory not found?